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 provides an operation to stop an observability server. It allows users to gracefully stop the server or force an immediate termination. This is useful in scenarios where you need to halt monitoring or observability services, for example, during maintenance or when shutting down the system.
Use Case Examples
- Stopping the observability server gracefully to ensure all processes complete properly.
- Forcing an immediate stop of the observability server in case of emergency or unresponsive state.
Properties
| Name | Meaning |
|---|---|
| Force | Determines whether to forcefully terminate the server immediately or stop it gracefully. |
| Request Options | Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout. |
Output
JSON
status- Indicates the result of the stop operation, e.g., success or failure.message- Additional information or error message related to the stop operation.
Dependencies
- Requires connection to the observability server API, potentially using API authentication credentials.
Troubleshooting
- If the server does not stop, check if the 'force' option is set correctly to force termination if needed.
- Timeout errors may occur if the server is unresponsive; adjust the timeout setting accordingly.
- SSL certificate validation errors can be bypassed by enabling 'Ignore SSL Issues', but this reduces security.
- Proxy settings must be correctly configured if a proxy is required for network access.