Overview
Monitors, dashboards, SLOs and the service catalog. Modus mines each resource type you select and keeps that context current.
What Modus reads
- 1Resource Type
- 2Dashboard
- 2Monitor
- 2SLO
- 2Service
- 2Notebook
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
6context types mined
6agent tool groups
1connection method
4security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Resource Type list
The Resource Type collections in the connection you select.
Dashboard metadata
A Datadog dashboard and its widget definitions.
Monitor metadata
A Datadog monitor: an explicit query plus the thresholds and alert message that define what the org treats as a failure, and the @-handles it escalates to.
SLO metadata
A service level objective: its target and warning thresholds per timeframe, and either the good/total queries or the monitors it aggregates.
Service metadata
A Software Catalog entity (service, system, datastore, queue or api), addressed by its stable `kind:name` ref.
Notebook metadata
A Datadog notebook — in practice a runbook.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
API key & application key
An API key and an application key from the source. Both are stored as secrets, and agents never see them.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.