Actions9
- Host Actions
- Service Actions
Overview
This node integrates with the Centreon monitoring platform API to manage hosts and their states. Specifically, for the Host - Acknowledge operation, it allows users to acknowledge alerts or issues related to a specific host in Centreon. Acknowledging a host typically means marking an alert as recognized, optionally notifying contacts, and controlling how the acknowledgement behaves over time.
Common scenarios where this node is beneficial include:
- Automatically acknowledging known issues during maintenance windows.
- Integrating alert workflows where external systems mark Centreon hosts as acknowledged after processing.
- Sending notifications to relevant teams when an acknowledgement occurs.
Practical example:
- When a host goes down and an alert is generated, an automated workflow can use this node to acknowledge the host with a comment explaining the reason (e.g., "Scheduled maintenance"), optionally notify contacts, and decide if the acknowledgement should persist through state changes or scheduler restarts.
Properties
| Name | Meaning |
|---|---|
| API Version | Version of the Centreon API to use (e.g., "latest", "v24.10"). |
| Host Name or ID | The host to acknowledge, selectable from a list or specified by ID via expression. |
| Comment | Reason for the acknowledgement (mandatory). |
| Notify | Whether to send a notification to the host's contacts upon acknowledgement (true/false). |
| Sticky | Whether to keep the acknowledgement active on state changes (true/false). |
| Persistent | Whether to keep the acknowledgement after the scheduler restarts (true/false). |
| Acknowledge Services Attached | Whether to also acknowledge all services attached to the host (true/false). |
| Options Avancées > Ignore SSL Errors | Whether to ignore TLS certificate errors when connecting to the API (true/false). |
Output
The node outputs JSON data representing the response from the Centreon API after performing the acknowledgement. This typically includes details about the acknowledgement action such as status, timestamps, and any messages returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"acknowledgement_id": 12345,
"host_id": 67890,
"comment": "Scheduled maintenance",
"notify": true,
"sticky": false,
"persistent": false,
"acknowledge_services": true,
"status": "success"
}
Dependencies
- Requires an API key credential for authenticating with the Centreon API.
- Needs network access to the Centreon server URL configured in the credentials.
- Supports specifying the API version to target different Centreon API releases.
- Optional setting to ignore SSL/TLS certificate errors if the Centreon server uses self-signed certificates.
Troubleshooting
- Authentication failures: If the node cannot authenticate, verify that the API credentials (username, password, base URL) are correct and that the Centreon API endpoint is reachable.
- Invalid host ID: Ensure the host ID or name selected exists in Centreon. Use the provided dropdown or expressions carefully.
- Missing comment error: 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 the "Ignore SSL Errors" option to avoid TLS validation failures.
- API version mismatch: Using an unsupported or incorrect API version string may cause unexpected errors. Confirm the version matches your Centreon installation.
Links and References
- Centreon API Documentation
- n8n Expressions Documentation
- Centreon Acknowledgement Concepts (general reference)