Integration · Automate and collaborate

Better Stack and Meteor AI agents

Connect Better Stack to a Met: check monitors and incidents, see who is on call and post an update on your status page.

How does Better Stack connect to Meteor?

With the Better Stack ready connector, your Met uses Better Stack's official MCP server with the account the admin authorizes. On WhatsApp it tells you which incidents are open, which monitor failed, how much availability your site had and who is on call. It also acknowledges an incident, escalates it, marks it resolved, leaves comments for the team and posts a report on your status page so your customers know what is going on. If your team sends logs to Better Stack, the Met queries them and reviews your application's errors. Only the direct SQL query starts switched off; the rest comes on and the admin decides in Connections which ones stay on.

What it automates

What a Meteor Met does with Better Stack

Answer whether your site is down

When you ask on WhatsApp whether the online store is down, the Met looks up open incidents, opens the one for the failing monitor and tells you since when and which error it returned.

Tell your customers on the status page

With the incident identified, the Met creates a report on your status page so your customers see you already know about the problem, and marks it resolved when the monitor recovers.

Know who has to act

The Met tells you who is on call, acknowledges the incident or escalates it to the right person or team, and leaves a comment with what was said in the chat.

Measure how your site did this month

The Met calculates a monitor's availability and response times for the period you ask, so the agency can show them to the client with Better Stack's numbers.

Review your application's errors

If your team sends logs or errors to Better Stack, the Met finds the application's new errors, returns their stack trace and answers which release brought them and how many users they affected.

29 tools

Everything your Met can ask Better Stack for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`incidents`	Finds incidents by date, status, monitor or other criteria.
`incident`	Returns the full details of an incident, with error messages and screenshots.
`incident_timeline`	Shows the complete history of an incident, from start to end.
`incident_comments`	Returns the comments the team left on an incident.
`create_incident_comment`	Adds a comment to an incident so the team sees it.
`acknowledge_incident`	Takes ownership of an incident for the connected account, which stops its escalations.
`escalate_incident`	Escalates an incident to people, teams, on-call calendars or policies.
`resolve_incident`	Marks an incident as resolved.
`create_status_page_report`	Creates an incident report or a maintenance notice on your status page.
`monitors`	Lists the account's monitors, with filters.
`monitor`	Returns a monitor's configuration, status and settings.
`monitor_availability`	Calculates a monitor's availability and SLA summary, per region.
`monitor_response_times`	Analyzes a monitor's response times and their trend, per region.
`create_monitor`	Creates a monitor that tracks the availability of a website, host or service.
`create_heartbeat`	Creates a heartbeat that alerts when a scheduled job stops reporting.
`escalation_policies`	Lists the configured escalation policies and their steps.
`escalation_policy`	Returns the details of an escalation policy, that is, who gets alerted next.
`on_calls`	Lists the on-call calendars and their rotations.
`on_call`	Tells who is on call for a calendar, now or at a given time.
`sources`	Lists the log sources with their status and configuration.
`source`	Returns the details of a source, with the data it holds and its services.
`source_fields`	Shows the fields you can query in a source's logs and spans.
`query`	Runs a ClickHouse SQL query over your logs, spans, metrics, errors and replays. It starts switched off.
`render_chart`	Runs a query and shows the result as a line, bar or pie chart.
`query_windows`	Estimates how many rows a long query reads and splits the range into time windows.
`applications`	Lists the applications that use Better Stack error tracking.
`errors`	Lists an application's error groups with their status, such as new or reoccurring.
`error`	Returns an error group with its stack trace, releases and affected users.
`documentation`	Searches the Better Stack documentation and returns the articles that answer.

The limits

What the Better Stack integration does NOT do

We would rather say it here than have you find out during rollout.

It does not edit, pause or delete monitors: it can create and read them, but changing a URL, a check frequency or the alerts happens in Better Stack.
It does not create or change escalation policies or on-call calendars: it only reads them to know who gets alerted.
It does not ask for confirmation in the chat before acknowledging, escalating or resolving an incident, or before posting on your status page. The admin chooses in Connections which actions stay on.
It does not create scripted browser monitors: that type is set up in Better Stack, because the create monitor tool takes no script.
It does not fix the outage or watch your site on its own: Better Stack runs the checks, and the Met queries what Better Stack already recorded.
It does not pay your Better Stack plan. Usage runs on your own account and plan.

Before you start

What you need to connect Better Stack

1

A Better Stack account with monitors

The Better Stack account where you monitor your site, with at least one monitor. For the status page, logs or errors, those products need to be set up in the account.
2

Connect it in Met

In Met, open Connections → Better Stack → Connect. A Better Stack window opens so you can sign in and authorize Met.
3

Decide which actions stay on

The workspace admin reviews the list of actions and turns off the ones the Met should not take alone, such as posting on the status page or resolving incidents.

Frequently asked questions

Questions about Better Stack and Meteor

This page covers what the Met looks up when you ask. Outage alerts come from Better Stack through its own integrations; the Met helps you understand the incident and act on it.

Yes, if the admin leaves that action on: it creates an incident report or a maintenance notice. Your customers see that report, so decide who gets to ask for it.

No. The server has no tools to edit, pause or delete monitors. The Met gives you the monitor's link so you can adjust it in Better Stack.

You do, with your Better Stack account and plan. Meteor does not resell Better Stack: the connector uses your company's account.

Step by step