Foreign Sources
RESTful service to the Horizon Provisioning Foreign Source definitions. Foreign source definitions are used to control the scanning (service detection) of services for SLA monitoring as well as the data collection settings for physical interfaces (resources).
This API supports CRUD operations for managing the provisioner’s foreign source definitions. Foreign source definitions are POSTed and will be deployed when the corresponding requisition gets imported/synchronized by Provisiond.
If a request says that it gets the "active" foreign source, that means it returns the pending foreign source (being edited for deployment) if there is one, otherwise it returns the deployed foreign source.
GETs (Reading Data)
| Resource | Description |
|---|---|
|
Get all active foreign sources. |
|
Get the active default foreign source. |
|
Get the list of all deployed (active) foreign sources. |
|
Get the number of deployed foreign sources. (Returns plaintext, rather than XML or JSON.) |
|
Get the active foreign source named {name} |
|
Get the configured detectors for the foreign source named {name} |
|
Get the specified detector for the foreign source named {name} |
|
Get the configured policies for the foreign source named {name} |
|
Get the specified policy for the foreign source named {name} |
POSTs (Adding Data)
POST requires XML using application/xml as its Content-Type.
| Resource | Description |
|---|---|
|
Add a foreign source. |
|
Add a detector to the named foreign source. |
|
Add a policy to the named foreign source. |
PUTs (Modifying Data)
PUT requires form data using application/x-www-form-urlencoded as a Content-Type.
| Resource | Description |
|---|---|
|
Modify a foreign source with the given name. |
DELETEs (Removing Data)
| Resource | Description |
|---|---|
|
Delete the named foreign source. |
|
Delete the specified detector from the named foreign source. |
|
Delete the specified policy from the named foreign source. |