Actions12
- Host Actions
- Service Actions
- Monitoring Server Actions
Overview
This node integrates with Centreon, a monitoring software, to manage hosts and their states via the Centreon Web API. Specifically, the Host Acknowledge operation allows users to acknowledge a host in the monitoring system. Acknowledging a host typically means marking an issue or alert as recognized, optionally notifying contacts, and controlling how the acknowledgment behaves over time.
Common scenarios for this node include:
- Automatically acknowledging known issues during maintenance windows.
- Marking alerts as acknowledged after manual investigation.
- Suppressing repeated notifications by setting sticky or persistent acknowledgments.
- Acknowledging all services attached to a host when the host itself is acknowledged.
Practical example:
- When a network device (host) triggers an alert, an automated workflow can acknowledge the host with a comment explaining the reason, notify the relevant team, and keep the acknowledgment sticky so it persists through state changes.
Properties
| Name | Meaning |
|---|---|
| API Version | Version of the Centreon API to use (e.g., "latest", "v24.10"). |
| Host Name or ID | The specific host to acknowledge. Choose from a dropdown list populated dynamically or specify an ID using an expression. |
| Comment | Reason for the acknowledgment. This is a required text field where you explain why the host is acknowledged. |
| Notify | Boolean flag indicating whether to send a notification to the host's contacts upon acknowledgment. |
| Sticky | Boolean flag indicating whether to keep the acknowledgment active even if the host's state changes. |
| Persistent | Boolean flag indicating whether to keep the acknowledgment after the monitoring scheduler restarts. |
| Acknowledge Services Attached | Boolean flag indicating whether to also acknowledge all services attached to the host. |
Output
The node outputs JSON data representing the result of the acknowledgment request. The structure includes:
- Confirmation of success or failure.
- Details about the operation performed.
- Timestamp of the operation.
- Any error messages if the operation failed.
Example output JSON snippet:
{
"success": true,
"message": "POST /monitoring/hosts/123/acknowledgements completed successfully",
"timestamp": "2024-06-01T12:00:00Z"
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Centreon Web API.
- Needs the Centreon API base URL and user credentials configured in n8n credentials.
- The node uses HTTPS requests to communicate with the Centreon API endpoints.
- Supports ignoring SSL certificate errors based on credential configuration.
Troubleshooting
Common Issues
- Authentication failures: If the API credentials are incorrect or expired, the node will throw an authentication error.
- Invalid host ID: Specifying a host that does not exist or is not accessible will cause the API call to fail.
- Missing required fields: The "Comment" property is mandatory; omitting it will cause validation errors.
- API version mismatch: Using an unsupported or incorrect API version string may lead to unexpected errors.
Error Messages and Resolutions
"Cannot authenticate to Centreon": Check API credentials and ensure they are correct."Unknown operation: ack": Verify that the operation name is correctly set to "ack" for acknowledging hosts.- HTTP request errors: Network issues or invalid endpoint URLs can cause failures; verify connectivity and API base URL.
- Validation errors for missing parameters: Ensure all required properties, especially "Comment" and "Host Name or ID," are provided.
Links and References
- Centreon Web API Documentation
- n8n Expressions Documentation
- Centreon Acknowledge Host API Endpoint (general reference)
This summary covers the static analysis of the Host Acknowledge operation within the Centreon node implementation for n8n workflows.