Skip to main content
Connect Better Stack with a global API token to sync team members, monitors, heartbeats and incidents, and run access reviews. Read-only.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the team members across your Better Stack organization with their name, email, role and the date they were added; pending invitations are left out. Better Stack reports no account status or MFA state, so every member is shown as Active with MFA Unknown. Uptime incidents from the last 90 days appear on your Incidents page.
A Global token is required. Better Stack also issues team-scoped Uptime API tokens; those cannot list the organization’s team members, and DSALTA rejects them at connect time.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Better Stack team member roster — names, emails, roles and join dates — which appears on your Access page; your Uptime monitors, which appear on your Inventory page with their type, status, check frequency, team and whether they are paused, and your heartbeats, which carry their status, period and team; and Uptime incidents that started in the last 90 days, which appear on your Incidents page. Each incident carries its cause and its acknowledged and resolved timestamps; an incident Better Stack has resolved shows Resolved, one that has been acknowledged shows Investigating, and any other shows Open. Every incident is recorded with severity Medium and type Availability, because Better Stack exposes neither.It calls these Better Stack endpoints:
  • betterstack.com/api/v2/team-members
  • uptime.betterstack.com/api/v2/monitors
  • uptime.betterstack.com/api/v2/heartbeats
  • uptime.betterstack.com/api/v3/incidents
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Better Stack environment.

​
Troubleshooting

The token is not a Global API token, or it was deleted. A team-based Uptime token connects to nothing DSALTA needs. Create a Global token and connect again.
Monitors, heartbeats and incidents are read best-effort after the team roster: a failure on one of those endpoints leaves that page empty without failing the sync. Click Sync from integrations on the Integrations page to retry. Incidents older than 90 days are never imported.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.