staging or production, so you can work across them.
Say your production label covers the prod-us-east-1 cluster, the AWS account behind it and the Datadog account watching both. That’s three sources and one environment. Every part of the product (Chat, Incidents, RCAs, Tasks) respects the environment you pick.


What counts as a source
- Kubernetes cluster. One EKS, GKE, AKS or self-managed cluster, with an observer inside it.
- Cloud account. One AWS account or Google Cloud project, watched by an observer.
- Machine. A Linux or macOS host with an observer installed.
- Connected tool. Datadog, PagerDuty, Grafana, Sentry, Jira, Linear, Observe or your own webhook.
Multi-source organizations
An organization is the top-level container. Inside it you can mix sources freely. A representative setup looks like:- One
prod-us-east-1Kubernetes cluster, labelledproduction. - One
staging-gkeKubernetes cluster, labelledstaging. - One AWS account, labelled
production. - One Datadog account that covers both labels.
orders-api in the last hour” spans them. An RCA that starts on a pod can read from the AWS account and Datadog too, because Rubix reads every source it can reach.
Source properties
Every source carries a small set of things that shape how RubixKube works with it.
Configuration can be set for the organization, for an environment label or for one source. Settings made higher up can be locked, and the source shows where each value came from.
How it scales
A few sources
Links between them start to pay off. Rubix follows a problem from a Datadog alert to the pod behind it.
Links between sources
Two sources often describe the same thing. A Datadog host and a Kubernetes node, say. RubixKube finds those links so an incident on one can reach what the other knows. The Correlate sources automation runs on a schedule and when you connect something. Shared ids, such as a node’s instance id, confirm a link in code. When only the names match, Rubix asks. You see a question on the source’s page, and you answer Yes, No or Skip. Your answer is final.

Common questions
How many environments can I connect?
How many environments can I connect?
Individual allows one, Business allows up to three, and Enterprise has no limit. See Pricing.
Does correlation across sources work automatically?
Does correlation across sources work automatically?
Partly. Links with shared ids confirm on their own. Links based on names wait for your answer. Rubix can read every source you’ve connected either way.
Can I group sources by team or region?
Can I group sources by team or region?
Yes. Environment labels are yours to name. An admin creates one from a source’s page, and a source can carry several.
What happens if an observer disconnects?
What happens if an observer disconnects?
After 5 minutes without a heartbeat the source reads disconnected. After 24 hours it’s archived. Its incidents and RCAs stay available, and the observer keeps trying to reconnect. New incidents from it stop until it does.
Can I delete a source without losing history?
Can I delete a source without losing history?
No. Deleting a source deletes its history and metrics, and it can’t be undone. For a connected tool, its incidents, webhook and automation go too. An observer keeps running until you uninstall it.
Related concepts
Observers
What you install to watch a cluster, account or machine.
Environments in the console
How to manage, label and configure sources day to day.
Connect your environment
How to connect your first source.
Integrations
Connect the tools you already use.