Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node performs an observability check operation, which is useful for monitoring and verifying the status or health of systems or services. It allows users to configure request options such as batching, SSL certificate validation, proxy settings, and request timeout to customize how the check requests are sent and handled. Practical applications include automated health checks of APIs, services, or infrastructure components to ensure they are operational and responsive.
Use Case Examples
- Performing periodic health checks on a web service to monitor uptime.
- Batching multiple observability check requests to avoid overwhelming the target system.
- Using a proxy to route observability check requests through a specific network path.
Properties
| Name | Meaning |
|---|---|
| Request Options | Settings to customize the HTTP request behavior for the observability check, including batching, SSL validation, proxy, and timeout. |
Output
JSON
status- The status of the observability check, indicating success or failure.responseData- The data returned from the observability check request, containing details about the checked system or service.
Dependencies
- Requires an API key credential or authentication token to access the observability service API.
Troubleshooting
- If requests time out, increase the timeout setting or check network connectivity.
- If SSL errors occur, enable 'Ignore SSL Issues' to bypass certificate validation, but be aware of security risks.
- Batching settings may cause delays; adjust batch size and interval for optimal performance.
Links
- Observability Node Documentation - Official documentation for the Observability node in n8n, providing detailed usage instructions and examples.