Actions12
- Host Actions
- Service Actions
- Monitoring Server Actions
Overview
This node integrates with Centreon, a monitoring software, via its Web API. Specifically, the Service - Acknowledge operation allows users to acknowledge a service alert or issue in Centreon. Acknowledging a service means marking it as recognized, often to indicate that someone is aware of the problem and is working on it, which can suppress further notifications or alerts.
Common scenarios for this node include:
- Automatically acknowledging service alerts when certain automated remediation steps are triggered.
- Integrating with incident management workflows to mark issues as acknowledged once they are assigned.
- Reducing noise by programmatically acknowledging known issues during maintenance windows.
Example: When an alert fires for a critical service monitored by Centreon, this node can be used to add an acknowledgment comment, optionally notify contacts, and set flags like sticky or persistent acknowledgment.
Properties
| Name | Meaning |
|---|---|
| API Version | Version of the Centreon API to use (e.g., "latest", "v24.10"). |
| Service Name or ID | The service to acknowledge. Choose from a dropdown list of services or specify an ID via expression. The value encodes both host ID and service ID. |
| Comment | Reason for the acknowledgment. This is a required text field where you explain why the service is being acknowledged. |
| Notify | Boolean flag indicating whether to send a notification to the service's contacts about the acknowledgment. |
| Sticky | Boolean flag indicating whether to keep the acknowledgment active even if the service state changes. |
| Persistent | Boolean flag indicating whether to keep the acknowledgment even if the Centreon engine restarts. |
Output
The node outputs JSON data representing the response from the Centreon API after attempting to acknowledge the service. The output typically includes success status and any relevant messages returned by the API.
The structure generally looks like:
{
"success": true,
"message": "POST /monitoring/hosts/{hostId}/services/{serviceId}/acknowledgements completed successfully",
"timestamp": "2024-06-xxTxx:xx:xxZ"
}
If an error occurs, the output will contain error details unless the node is configured to continue on failure.
No binary data is produced by this operation.
Dependencies
- Requires valid Centreon API credentials (username, password, base URL).
- The node authenticates with Centreon using these credentials to obtain an authentication token.
- The API version must be specified; defaults to "latest".
- Network access to the Centreon server's API endpoint is necessary.
- No additional external dependencies beyond the Centreon API and n8n's HTTP request capabilities.
Troubleshooting
- Authentication errors: If the node cannot authenticate, it throws an error "Cannot authenticate to Centreon" or "Authentication failed". Verify credentials and network connectivity.
- Invalid service selection: The service property expects a JSON string encoding host and service IDs. Selecting from the provided dropdown ensures correct format.
- Missing required fields: The "Comment" property is mandatory. Omitting it will cause an error.
- API errors: Any HTTP or API errors from Centreon are propagated. Check the message for details.
- Date/time validation: Not applicable for this operation but relevant for downtime operations.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error info in the output.
Links and References
- Centreon Web API Documentation
- n8n Expressions Documentation
- Centreon Acknowledgement API Endpoint (for reference)
This summary is based solely on static analysis of the provided source code and input properties definition.