Actions9
- Host Actions
- Service Actions
Overview
This node integrates with the Centreon Web API to manage monitoring services and hosts. Specifically, for the Service - Acknowledge operation, it allows users to acknowledge alerts or issues on a specific service monitored by Centreon. Acknowledging a service typically means marking an alert as recognized, optionally notifying contacts, and controlling how the acknowledgement behaves over time (sticky, persistent).
Common scenarios where this node is beneficial include:
- Automatically acknowledging known issues during maintenance windows.
- Integrating alert acknowledgements into automated workflows or incident management systems.
- Sending notifications to service contacts when an issue is acknowledged.
Example use case: When a monitoring alert triggers for a critical service, an automated workflow can acknowledge the alert with a comment explaining the reason, notify the relevant team, and ensure the acknowledgement persists through state changes or system restarts.
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 list loaded dynamically or specify an ID via expression. |
| Comment | Reason for the acknowledgement (mandatory). |
| Notify | Whether to send a notification to the service's contacts upon acknowledgement (true/false). |
| Sticky | Whether to keep the acknowledgement active on state changes (true/false). |
| Persistent | Whether to keep the acknowledgement even if the monitoring engine restarts (true/false). |
| Options Avancées | Advanced options collection containing: |
| - Ignore SSL Errors | Whether to ignore TLS certificate errors when connecting to the Centreon API (true/false). |
Output
The node outputs JSON data representing the response from the Centreon API after attempting to acknowledge the specified service. This typically includes confirmation details about the acknowledgement action performed.
No binary data output is produced by this operation.
Example output JSON structure (simplified):
{
"comment": "Acknowledgement reason",
"is_notify_contacts": true,
"is_sticky": false,
"is_persistent_comment": false,
"service_id": "123",
"host_id": "456",
"acknowledgement_id": "789"
}
The exact fields depend on the Centreon API response but generally confirm the acknowledgement parameters and identifiers.
Dependencies
- Requires valid credentials for the Centreon API (username, password, base URL).
- Needs network access to the Centreon server.
- Supports specifying API version; defaults to "latest".
- Optional configuration to ignore SSL/TLS certificate errors.
- Uses n8n helper methods for HTTP requests and credential management.
Troubleshooting
- Authentication failures: If the node cannot authenticate, verify that the provided API credentials are correct and that the Centreon server is reachable.
- Invalid service selection: Ensure the service ID or name is valid and exists in Centreon. Use the dynamic dropdown to select available services.
- Missing mandatory comment: The "Comment" property is required; leaving it empty will cause an error.
- SSL errors: If connecting to a Centreon instance with self-signed certificates, enable "Ignore SSL Errors" to bypass TLS verification.
- API version mismatch: Using an unsupported API version may cause unexpected errors. Confirm the version matches your Centreon installation.
- Network issues: Timeouts or connection errors indicate network problems between n8n and Centreon.
Links and References
- Centreon API Documentation
- n8n Expressions Documentation
- Centreon Acknowledgement API Reference (general reference for acknowledgement endpoints)