One place for everything a team uses
Alert rules, incidents, SLOs, investigations, connectors and notification channels sit next to the telemetry they watch. Someone who opens Services and then Incidents is still looking at the same data.
Platform
Your workspace is where your telemetry lives.
Sign up and Onyx creates an organization with one workspace. Your tokens, dashboards, alert rules, incidents, SLOs and team all live there, and what you send is read only in your workspace.
What you get
Access you can explain
Admins invite people by email. Each invite is single-use, goes to one address and expires after seven days. Add single sign-on over OIDC or SAML 2.0, and require two-step verification for everyone from the Governance page.
Tokens that stay in their lane
A token has scopes: ingest telemetry, read and query, manage dashboards, workspace configuration. The secret is shown once, revoking takes effect within about ten seconds, and no token can manage members, single sign-on or billing.
How it is set up
Create it
Sign up with a company name, your name, an email and a password. Industry is optional. You get a 14-day free trial.
Invite your team
Admins send invites from the Team page. The person you invite chooses their own password. Pending invites count toward your seats.
Connect data
Create an ingest token in Connect data and put it, with the workspace endpoint, into your OpenTelemetry settings.
Look around
Services, Traces, Logs and Metrics fill in as data arrives. The sample workspace below shows what that looks like.
How workspaces are kept apart
- The token decides. The workspace a piece of telemetry lands in comes from the token that sent it. A payload cannot choose another workspace.
- Reads are filtered on the server. Every request that reads telemetry is limited to the workspace it belongs to.
- It is logical separation. Telemetry from all workspaces is kept in shared tables, separated by that filter. It is not a separate database per customer.
- Production and staging. Within one workspace, tell environments apart with the deployment.environment.name attribute. If you want them fully apart, ask Onyx for a second workspace.
Take the product tour
Open a clickable workspace modeled on the product. Explore a fictional payments company; every number and record is illustrative.
Payments workspace
Follow authorization, KYC, FX routing, payout and settlement signals.
OpenOverview
How every service is doing, on one screen.
OpenServices
Each service with its volume, failures and latency.
OpenQuery Studio
Ask the data a question and get a table or a chart.
OpenAlert rules
Rules, incidents and error budgets.
OpenAsk Onyx Oracle
A sample question about a failing service.
OpenPayment topology
See the sample services and payment processors connected together.
OpenMake your own.
A trial workspace takes a company name, an email and a password.