ceven

Better Stack

Syncs uptime monitors, heartbeat checks, and incident schedules into your operational workflows to automate on call rotations and status updates.

Try Better Stack in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Better Stack integration

    • Describe the outcome and Ceven picks the right Better Stack calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Better Stack data, across all 117 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Better Stack access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Better Stack, when, and on whose behalf.
    • The agent pauses and asks when Better Stack is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Better Stack.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Better Stack action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Better Stack, and when to use it.

Create Escalation Policy
Use this when defining how incidents should escalate across team members to ensure no alert is missed.
Create Heartbeat Group
Use this when you need to organize related heartbeat checks under a single logical group for backend services.
Create Outgoing Webhook
Use this when you need to register an endpoint to receive event notifications from Better Stack in other apps.
Create Source Group
Use this to organize related log sources under a group once you have finalized the group name.
Delete Escalation Policy
Use this when you need to permanently remove an existing escalation policy after confirming its id.
Get Heartbeat Availability
Pull availability metrics for a heartbeat within a specific date range to check uptime percentages.
Get Monitor Availability
Pull uptime percentage and incident details for a specific monitor within an optional date range.
Get Monitor Response Times
Pull performance metrics over the last 24 hours for a specific monitor id.
List Heartbeats
Pull all configured uptime heartbeats with optional pagination to audit system health.
List Monitors
Pull existing uptime monitors with optional filtering by url or name.
List On Call Schedules
Pull all configured on call calendars to see who is currently active.
List Status Pages
Pull all existing status pages to manage public communication channels.
Create Outgoing Webhook Integration
Tool to create a new outgoing webhook integration. use when you need to register an endpoint to receive event notifications from better stack.
Delete Source Group
Tool to delete a source group by id. use when you need to permanently remove an existing source group after confirming it is no longer needed.
Get Heartbeat
Tool to get a single heartbeat by id. use when you need to fetch details of a specific heartbeat.
Get Monitor
Tool to get a single monitor. use when you need full details of a specific monitor by its id.
Get Status Page
Tool to get a single status page by id. use when you need detailed information about a specific status page.
Get Telemetry API Token
Tool to retrieve the telemetry api token from the integration configuration. use when you need to authenticate telemetry api requests.
Get Uptime API Token
Tool to retrieve the configured uptime api token. use when you need the uptime api token for subsequent authenticated api calls.
List Catalog Relations
Tool to list all catalog relations. use when you need to retrieve all catalog relations, supports pagination.
List Google Monitoring Integrations
Tool to list all google monitoring integrations. use when you need to view your configured google monitoring on call integrations with pagination support.
List Grafana Integrations
Tool to list all grafana integrations. use when you need to retrieve and inspect all configured grafana integrations.
List New Relic Integrations
Tool to list new relic integrations. use when you need to retrieve and inspect all configured new relic integrations with pagination support.
List Status Page Reports
Tool to list all reports on a status page. use when you need to retrieve existing status page reports with optional pagination via `page` and `per page`.
Update Heartbeat
Tool to update an existing heartbeat configuration. use after retrieving a heartbeat and choosing which fields to change.
Update Heartbeat Group
Tool to update an existing heartbeat group. use when you need to modify attributes like name, interval, or pause status.
Update Source Group
Tool to update an existing source group. use when you need to rename or reorder a source group.

27 actions · scroll to see them all

Frequently asked questions

Ceven implements a smart queuing system to respect Better Stack API limits. Better Stack applies rate limits based on your plan tier, and exceeding these can result in temporary 429 errors. Our agent monitors the headers returned by the Better Stack API to track remaining quota in real time. If a workflow triggers a high volume of requests, such as listing thousands of monitors, Ceven automatically throttles the execution and uses an exponential backoff strategy. This ensures that your critical monitoring alerts are never blocked by administrative API calls made by the agent. You can check your current usage within the Ceven integration dashboard to see if you are approaching your plan limits.
Yes. By using the List On Call Schedules and Create Escalation Policy actions, Ceven can synchronize your Better Stack rotation with an external source of truth like a Google Sheet or a HR system. When a team member changes roles or goes on leave, the agent can update the escalation path to ensure alerts route to the correct active engineer. This removes the need for a manual update in the Better Stack dashboard every time a shift changes. The agent verifies the identity of the new on call person before committing the change to prevent routing critical alerts to an inactive or incorrect account.
Ceven interacts with the Better Stack API to manage heartbeats, but the heartbeat signal itself comes from your server to Better Stack. You use the Create Heartbeat action to set up the expectation in Better Stack, and then your server sends the ping. Ceven monitors the status of those heartbeats via the Get Heartbeat Availability action. If a heartbeat is missed, Ceven can trigger a workflow to attempt a server restart via SSH or notify the infrastructure team. It does not act as the ping source but rather the orchestrator that reacts when Better Stack reports a missed signal.
Absolutely. This is a primary use case for the integration. You can build a workflow where a specific monitor failure in Better Stack triggers a status page update. For example, if your database monitor shows a critical failure, Ceven can call the status page API to change the status to Major Outage and post a message stating that the team is investigating. Once the monitor returns to a healthy state, the agent can automatically resolve the incident on the status page and post a summary of the downtime duration. This ensures your customers are informed without an engineer needing to manually update the page during a crisis.
Ceven uses the Create Source Group and Update Source Group actions to keep your logging environment clean. As you add new microservices, the agent can automatically categorize them into source groups based on their naming convention or the environment they are deployed in. This prevents the log viewer from becoming cluttered. If you rename a service in your deployment pipeline, Ceven can update the corresponding source group name in Better Stack to keep your monitoring and deployment data in lockstep. This is particularly useful for teams running hundreds of ephemeral containers that need logical grouping for efficient debugging.
The delay is minimal because Ceven can be configured to react to Better Stack outgoing webhooks. Instead of polling the API every few minutes, Better Stack pushes the event to Ceven the moment it happens. This trigger then kicks off the agent workflow in milliseconds. For read actions, like checking response times during an active incident, the agent fetches the data in real time from the Better Stack API. The only significant latency would occur if you are on a lower Better Stack plan with longer check intervals for your monitors, as Ceven can only act on data that Better Stack has already collected.
Ceven can retrieve the Telemetry and Uptime API tokens using the dedicated Get Token actions, which allows the agent to pass these credentials to other secure tools in your workflow. However, for security reasons, Ceven cannot create new master API keys or change your account password. All token access is governed by the permissions of the account used to connect the integration. We recommend using a dedicated service account with the minimum necessary permissions to manage monitors and schedules, ensuring that the agent has enough access to perform its duties without having full administrative control over your entire Better Stack organization.

Alternatives to Better Stack

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

PagerDuty logoPagerDutyDatadog logoDatadogNew Relic logoNew Relic

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Better Stack and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free