Actions12
- Host Actions
- Service Actions
- Monitoring Server Actions
Overview
This node integrates with Centreon, a monitoring software, via its Web API. Specifically, the "Monitoring Server" resource with the "List" operation allows users to retrieve a list of monitoring servers configured in Centreon.
Typical use cases include:
- Fetching available monitoring servers to display or process further in an automation workflow.
- Integrating Centreon monitoring server data into dashboards or reporting tools.
- Automating configuration management by retrieving current monitoring server details.
For example, a user might want to get the first 50 monitoring servers to verify their status or to trigger configuration updates on them.
Properties
| Name | Meaning |
|---|---|
| API Version | Version of the Centreon API to use (e.g., "latest", "v24.10"). |
| Limit | Maximum number of monitoring server results to return (minimum 1). |
Output
The output is a JSON array where each item represents a monitoring server retrieved from Centreon. The structure corresponds directly to the API response under /configuration/monitoring-servers. Each object typically contains properties such as the server's ID, name, and other metadata as provided by Centreon's API.
No binary data is output by this operation.
Example output snippet (conceptual):
[
{
"id": "123",
"name": "Primary Monitoring Server",
"address": "192.168.1.10",
...
},
{
"id": "124",
"name": "Backup Monitoring Server",
"address": "192.168.1.11",
...
}
]
Dependencies
- Requires valid Centreon API credentials (username, password, base URL).
- The node authenticates using these credentials to obtain an API token before making requests.
- The API version parameter must correspond to a supported Centreon API version.
- Network access to the Centreon API endpoint must be available.
- Optionally respects SSL verification based on credential settings.
Troubleshooting
- Authentication failures: If the node cannot authenticate, it throws an error "Cannot authenticate to Centreon". Verify that the API credentials are correct and that the Centreon API endpoint is reachable.
- Invalid API version: Using an unsupported or incorrect API version string may cause request failures.
- Limit parameter issues: Setting the limit below 1 will be rejected; ensure the limit is at least 1.
- Network errors: Connection timeouts or SSL errors can occur if the base URL is incorrect or SSL verification fails.
- Unexpected response format: If the API response changes or is malformed, the node may throw errors when parsing results.
To resolve these issues:
- Double-check credentials and API endpoint URLs.
- Confirm the API version matches your Centreon installation.
- Adjust SSL verification settings if necessary.
- Review network connectivity and firewall rules.