Operator
You run what others have built: platform component health, service objectives, incidents and installs in tenants.
The operator runs what others have built. On the platform you watch component health, service objectives and incidents; you see integrations and the installs in tenants.
inlorus doesn't hide the difference between “I don't know” and “healthy”. A component with no measurement is marked as a blind spot; in a window with no measurements at all, whether the objective was met is written as unknown. A pending install isn't shown as failed either.
The operator archetype reads application, capability and configuration; it reads and writes operations and integrations. It exists to keep things running, not to change them.
Start here
- On the Operations screen, see component health, service objectives and open incidents.
- Measure the components with “Check now”; a component with no measurement is not healthy, it is unknown.
- Open an incident, take it on, and close it when it is resolved.
- Follow on the tenant operations screen which step a stuck install in a tenant stopped at.
- On the Integrations screen, see the registered external systems, connections and pipelines.