Actions116
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ļø Sessions Actions
- š Profile Actions
- š¼ļø Screenshot Actions
- š¤ Chatting Actions
- š¢ Channels Actions
- š¢ Status Actions
- š„ Groups Actions
- Add Participants
- Demote To Admin
- Create Group
- Get Groups
- Join Info Group
- Join Group
- Refresh Groups
- Get Group
- Delete Group
- Leave Group
- Get Chat Picture
- Set Picture
- Delete Picture
- Set Description
- Set Subject
- Set Info Admin Only
- Get Info Admin Only
- Set Messages Admin Only
- Get Messages Admin Only
- Get Invite Code
- Revoke Invite Code
- Get Participants
- Remove Participants
- Promote To Admin
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
- š Auth Actions
Overview
This node interacts with an observability service to check the status of the system or service being monitored. It is useful for monitoring the health and operational status of applications or infrastructure, enabling users to programmatically retrieve status information for alerting, reporting, or automated decision-making. For example, it can be used to verify if a service is up and running or to gather metrics about system performance.
Use Case Examples
- Check the current status of a web service to trigger alerts if the service is down.
- Retrieve observability data to log system health metrics periodically.
Properties
| Name | Meaning |
|---|---|
| Request Options | Settings to control how the request is made, including batching, SSL certificate validation, proxy usage, and timeout settings. |
Output
JSON
status- The current status information retrieved from the observability service.details- Additional details or metadata about the status response.
Dependencies
- Requires connection to an observability API service, authenticated via an API key or token as configured in the node credentials.
Troubleshooting
- If the node fails due to SSL certificate errors, enable 'Ignore SSL Issues' to bypass certificate validation (not recommended for production).
- Timeout errors may occur if the server is slow to respond; increase the 'Timeout' setting accordingly.
- Proxy configuration errors can cause request failures; verify proxy URL and credentials if used.
- Batching settings may affect performance; adjust batch size and interval to optimize throughput and avoid rate limits.