SDKs
9n9s provides several official SDKs to make integrating Heartbeat Monitoring into your applications as seamless as possible. These libraries provide convenient wrappers around the raw HTTP pulse endpoints and automatically add useful context to your pulses.
Key Features
Section titled “Key Features”- Simple API: A clean and consistent API across all languages:
nines.pulse(),nines.start(),nines.fail(). - Automatic Context: Where possible, SDKs automatically capture context like hostname, script name, or serverless function details.
- Log Capture: Easily send application logs or error objects along with your pulses.
- Runtime Tracking: Built-in support for signaling job start and completion to track execution time.
- Error Handling: Gracefully handles network issues and provides helpers for easy integration with application-level error handling.
Supported Languages
Section titled “Supported Languages”Select a language to see detailed installation and usage instructions:
If your language is not listed, you can always use the raw HTTP pulse endpoints with any standard HTTP client.
Getting Started
Section titled “Getting Started”- Install the SDK for your preferred language
- Create a Heartbeat Monitor in your 9n9s dashboard
- Initialize the SDK with your monitor’s unique ID
- Send pulses from your application or scripts
For detailed examples and best practices, see our Use Cases guide and Getting Started guide.
Integration Patterns
Section titled “Integration Patterns”The SDKs support several common integration patterns:
- Cron Job Monitoring: Wrap your scheduled tasks with pulse notifications
- Background Worker Monitoring: Track queue processors and long-running jobs
- Serverless Function Monitoring: Monitor AWS Lambda, Google Cloud Functions, etc.
- Pipeline Monitoring: Track ETL processes and data workflows