Actions12
- Host Actions
- Service Actions
- Monitoring Server Actions
Overview
This node integrates with Centreon, a monitoring software, to manage service downtimes via its Web API. Specifically for the "Service" resource and "Downtime" operation, it allows scheduling downtime periods for individual services monitored by Centreon. This is useful when planned maintenance or known issues require temporarily suspending alerts for specific services.
Typical use cases include:
- Scheduling downtime for a service before performing maintenance to avoid false alarms.
- Automating downtime scheduling based on external triggers or workflows.
- Managing service availability windows programmatically within an IT operations automation pipeline.
For example, you can specify a service (host-service pair), provide a reason comment, set start and end times in UTC, and define whether the downtime is fixed or flexible along with its duration.
Properties
| Name | Meaning |
|---|---|
| API Version | Version of the Centreon API to use (e.g., "latest", "v24.10"). |
| Service Name or ID | The target service to put into downtime, selected from a list or specified by expression. |
| Comment | Reason for scheduling the downtime (required). |
| Start Time | UTC start time of the downtime in ISO format (YYYY-MM-DDThh:mm:ssZ) (required). |
| End Time | UTC end time of the downtime in ISO format (YYYY-MM-DDThh:mm:ssZ) (required). |
| Fixed | Boolean indicating if the downtime is fixed (true) or flexible (false). |
| Duration in Seconds | Length of the downtime period in seconds (minimum 1 second). |
Output
The node outputs JSON data representing the result of the downtime scheduling API call. This typically includes success confirmation or error details returned by the Centreon API.
The output JSON structure contains fields such as:
- Confirmation message or API response data.
- Timestamps or metadata related to the downtime scheduling.
- In case of errors, an error message field describing the failure.
No binary data output is produced by this operation.
Dependencies
- Requires an active Centreon API credential with username, password, base URL, and SSL ignore option configured in n8n.
- The node authenticates to the Centreon API using these credentials to obtain an authentication token.
- The API version parameter controls which Centreon API endpoint version is used.
- Network access to the Centreon server's API endpoint must be available.
Troubleshooting
- Authentication failures: If the node cannot authenticate, ensure the API credentials are correct and the Centreon server is reachable.
- Invalid time range: The node validates that the start time is before the end time; otherwise, it throws an error. Check the input times carefully.
- API errors: Errors from the Centreon API (e.g., invalid service ID, permission denied) will be surfaced. Review the error messages for guidance.
- Empty or malformed service selection: Ensure the service parameter is correctly selected or expressed; invalid JSON or missing IDs cause failures.
- SSL issues: If using self-signed certificates, enable the "ignore SSL" option in credentials to avoid TLS errors.