- Category: server monitoring
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 7
- Triggers: 0
- Slug:
HONEYBADGER - Version: 20261101_00
Tools
Report Check-In
Report Check-In
Slug:
HONEYBADGER_REPORT_CHECK_INReports a check-in (ping) to Honeybadger for uptime monitoring. Check-ins are used to monitor scheduled tasks, cron jobs, and background processes. By pinging this endpoint regularly, you signal that your task is running on schedule. If Honeybadger doesn’t receive a ping within the expected timeframe, it will alert you that the task may have failed or stopped running. Use this action at the end of successful task executions to notify Honeybadger the task completed as expected.Input Parameters
Output
Report Check-In With Payload
Report Check-In With Payload
Slug:
HONEYBADGER_REPORT_CHECK_IN_WITH_PAYLOADReport a check-in to Honeybadger with execution status, duration, stdout, stderr, or exit code. Use it to monitor scheduled tasks or cron jobs.Input Parameters
The unique identifier of the check-in to report. This acts as authentication for the check-in endpoint.
Output
Report Deployment
Report Deployment
Slug:
HONEYBADGER_REPORT_DEPLOYMENTReport a new deployment to Honeybadger for deployment tracking and error correlation. Use this tool after deploying code to notify Honeybadger, which allows you to: - Track deployment history on your project’s Deployments page - Correlate errors with specific deployments - Automatically resolve errors when deploying to an environment All deployment fields are optional, but providing environment and revision is recommended for better tracking.Input Parameters
Deployment details including environment, revision, repository, and username. All fields are optional but providing more details helps track deployments.
Output
Report Event
Report Event
Slug:
HONEYBADGER_REPORT_EVENTSend custom events to Honeybadger Insights for tracking, monitoring, and analytics. Use this action to record any structured event data such as: - User activity and behavioral events (logins, page views, feature usage) - Application errors and exceptions with context - Performance metrics and timing data - Custom business events and audit trails - System health and operational metrics Events are sent as newline-delimited JSON (NDJSON) and can include any custom fields. The API returns tracking IDs for each successfully recorded event.Input Parameters
List of event objects to send to Honeybadger Insights. Each event is a flexible dictionary that can contain any fields relevant to your tracking needs (e.g., event name, user_id, timestamps, custom metadata). Common patterns include: error events with error_type/message fields, user activity events with user_id/action fields, or performance metrics with timing data. Size constraints: each event < 100 kB, total payload < 5 MB.
Output
Report Exception
Report Exception
Upload File to S3
Upload File to S3
Upload Source Map
Upload Source Map
Slug:
HONEYBADGER_UPLOAD_SOURCE_MAPUpload JavaScript source maps to Honeybadger for error stack trace de-minification. Use this tool after deploying minified JavaScript assets to enable Honeybadger to display un-minified, readable stack traces when errors occur. Source maps allow Honeybadger to map minified code back to your original source code with proper file names, function names, and line numbers. The tool uploads: (1) the minified JS file, (2) its corresponding .map file, and optionally (3) additional source files referenced by the map, all associated with the production URL.Input Parameters
Deploy revision identifier (e.g., Git commit SHA, version tag) for tracking which deployment this source map applies to. Should match the revision configured in honeybadger.js. Defaults to ‘master’ if not provided.
Absolute production URL of the minified JS file in production; supports '' wildcard for domain/protocol matching. Query strings are ignored. Example: ‘https://cdn.example.com/app.min.js’ or ‘https:///assets/app.min.js’
Additional original source files referenced by the source map. Each filename must match the source file’s production URL path. Used when source map references files not embedded inline.