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 performs a Heapsnapshot operation within the Observability resource, typically used for capturing memory heap snapshots to analyze memory usage and detect leaks in applications. It is beneficial in scenarios where developers or system administrators need to monitor and troubleshoot memory consumption issues in their systems.
Use Case Examples
- Capturing a heap snapshot to analyze memory usage of a Node.js application.
- Using the node to periodically take memory snapshots for performance monitoring and debugging.
Properties
| Name | Meaning |
|---|---|
| Request Options | Settings to customize the HTTP request behavior for the Heapsnapshot operation, including batching, SSL certificate handling, proxy configuration, and timeout settings. |
Output
JSON
heapSnapshotData- The captured heap snapshot data, typically in a format suitable for memory analysis tools.status- Status of the heapsnapshot operation, indicating success or failure.timestamp- The time when the heap snapshot was taken.
Dependencies
- Requires an API key credential or similar authentication to access the observability service endpoint.
Troubleshooting
- If the node fails due to SSL certificate errors, enable 'Ignore SSL Issues' to bypass certificate validation, but be aware of security risks.
- Timeout errors can occur if the server is slow to respond; increase the 'Timeout' setting as needed.
- Batching settings should be adjusted carefully to avoid overwhelming the server or causing rate limits.