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 a Ping operation within the Observability resource, typically used to check the availability and responsiveness of a service or endpoint. It is beneficial for monitoring system health, verifying connectivity, and ensuring that services are operational. For example, it can be used to periodically ping a web service to confirm it is online or to measure response times for performance monitoring.
Use Case Examples
- Use the Ping operation to verify that a remote API is reachable before making further requests.
- Monitor the uptime of a critical service by scheduling regular pings and triggering alerts if the service becomes unresponsive.
Properties
| Name | Meaning |
|---|---|
| Request Options | Settings to control how the ping requests are made, including batching, SSL certificate validation, proxy usage, and timeout settings. |
Output
JSON
statusCode- HTTP status code returned by the ping request, indicating success or failure.responseTime- Time taken to receive a response from the server, useful for performance monitoring.responseBody- Content of the response received from the pinged service, if any.
Dependencies
- Requires network access to the target service or endpoint being pinged.
Troubleshooting
- If the node fails due to SSL certificate issues, enable 'Ignore SSL Issues' to bypass validation, but be aware of security risks.
- Timeout errors indicate the target service did not respond within the specified time; consider increasing the timeout or checking network connectivity.
- Proxy configuration errors may occur if the proxy URL or credentials are incorrect; verify proxy settings.