Bronto¶
Search Bronto logs, metrics and monitors during investigations.
Before you connect, find your Bronto region and choose either signing in or an API key. If you want Bronto monitors to open investigations, also do step 5 after you connect.
1. Find your region¶
Your Bronto sign-in address shows your region. Select the matching label when you connect.
| You sign in at | Label |
|---|---|
app.eu.bronto.io |
EU |
app.us.bronto.io |
US |
2. Enable MCP access in Bronto¶
A Bronto admin must enable MCP access once for the organization:
- In Bronto, go to Settings > Authentication.
- Enable the MCP login method, select Configure, choose the login methods allowed for MCP, and select Save.
3. Choose how to authenticate¶
Sign in (default)¶
Sign in to Bronto with a login method enabled for MCP and approve the requested access. You don't need to create a client ID or secret.
The agent acts as the user who signs in, with that user's Bronto permissions. Use a user who can search the datasets the agent should investigate and view monitors. A dedicated user with the Agent Read Only role gives the agent read-only access to logs, monitors, dashboards, integrations and SLOs. Do not use a shared administrator account.
API key¶
Use a key when the agent must act as itself, not as a person. Creating an API key requires the Admin role in Bronto; if you don't have it, ask a Bronto administrator to create the key.
- In Bronto, go to Settings > API Keys and select Create a new API Key.
- Name it after its purpose, such as
aws-devops-agent. - Select the Agent Read Only role. It gives read-only access to logs, monitors, dashboards, integrations and SLOs, and no access to API keys, users or billing. Do not use a Search key, which can't read monitors, or Ingestion key.
- Select Create Key and copy the key. It is shown only once.
When you connect, paste the key by itself into Bronto API key. DevOps Agent sends it in the X-BRONTO-API-KEY header.
4. Select the tools¶
The Bronto skills use get_datasets, get_datasets_by_name, get_keys, get_key_values, get_error_summary, timeseries, search_logs, get_saved_searches and run_saved_search.
- With the Agent Read Only role, Bronto offers only its read-only tools, so you can select all of them.
- With other roles, the tools Bronto offers depend on the role's permissions. If
create_monitororcreate_saved_searchis offered, leave it unselected. They are the only tools that change anything in Bronto, and the skills never call them. With sign-in the agent has the signed-in user's permissions, so leaving them unselected is what keeps it read-only.
5. Let Bronto monitors open investigations¶
After you connect, the console shows a webhook URL and a signing secret for your Agent Space. Add them to Bronto:
- In Bronto, go to Settings > Integrations and select AWS DevOps Agent.
- Paste the Webhook URL and the Signing secret, and save. Bronto builds and signs the request body for you, so you don't need to paste the body the console shows.
- Open each monitor that should start an investigation, add the integration under Notifications, and save.
Bronto notifies the agent only when a monitor alerts. Each alert opens one investigation; warnings, no-data states and resolutions are not sent. Fill in each monitor's Description: it is sent with the alert, and the agent reads it as context.
Sending a test notification from a monitor opens a real investigation.
More in the Bronto docs: AWS DevOps Agent, Hosted MCP Server and API Keys.
Skills¶
The console offers to install these skills when you add this connector: