When you’d use this
- Your logs and monitors live in Observe. Each alarm gets an investigation without anyone opening a worksheet.
- You want RCAs built on your own data. With a connection, Rubix reads your Observe datasets as evidence.
Connect it
Make its webhook in RubixKube
Go to Environments > Connect and pick Observe. Give it a name, then choose Make its webhook. Copy the URL. It’s shown once, and anyone who has it can post to it.
Paste the payload
Paste this as the action’s payload. The Connect dialog shows the same text, with a copy button.
What opens an incident and what resolves it
Severity comes from the alarm: Critical is critical, Error is high, Warning is medium, and anything else is low.
Each alarm is one incident.
What you’ll see
The source appears on Environments as soon as you make its webhook, then shows as connected when the first message arrives. Its page has an Events tab with the last 20 messages, so you can check what Observe really sent. The automation Observe alerts become incidents is on under Automations. If events arrive and no incident opens, the source page says so and offers Turn on. Each incident carries the alert’s details and a link back to Observe. Triage, the RCA and Tasks then work as they do for any other incident.What Rubix can read too
To let Rubix read Observe while it investigates, open Customize > Integrations, pick Observe, and enter your customer id and region. Your customer id is the number at the start of your Observe address: forhttps://123456789012.observeinc.com, it’s 123456789012. Then choose Sign in with Observe or paste an API token.
The connection’s Reads section shows what Rubix can reach: logs from each dataset, monitors and Observe’s docs. See the Reads check.
Related pages
Integrations overview
The two ways to connect a tool.
Incidents
What happens after an incident opens.
Datadog
Send monitor alerts from Datadog.
Sign-in and tokens
How connections sign in.