Discovery
Discovery
Discovery collects context from connected integrations so investigations can identify relevant services, resources, datasources, and alert rules. Open Aiden SRE -> Discovery to review the latest inventory, insights, and previous runs.
Run discovery
- Select Run Discovery.
- Review the integration instances grouped by provider. Select the instances to scan and clear any you want to exclude.
- If an instance is missing, use Want to add a new o11y integration? or follow Integrations for SRE.
- Select Run Discovery in the panel. To leave without starting a scan, select Close.
- Review the new history row and the Last run time and Duration when it finishes.
A discovery scan gathers context. It does not import the active alert queue; configure alert ingestion separately.
Read Discovered Entities
The tiles summarize what the connected sources expose. Examples include Kubernetes resources, datasources, services, alert rules, label keys, namespaces, and environments. Other integrations can expose different categories.
Use these counts to check coverage: does the intended environment appear, and are the datasources or services needed for an investigation represented? Counts summarize discovered inventory, not a live health assessment. A populated tile does not mean every resource is healthy or that every telemetry query is authorized.
The history's Entities count describes the records collected for a run; do not assume it equals the sum of the inventory tiles.
Review Insights
Insights call out gaps or findings in the available context, such as missing runbooks, service mapping gaps, or telemetry coverage. Each row shows Criticality and Insight. Select an expandable row to read its full description; use View more when additional insights are available.
For a missing-runbook finding, add operational guidance through Knowledge Hub and attach it to the relevant agent. For a telemetry gap, check the source integration and data collection before scanning again.
An insight is a finding to review. It does not mean Aiden has made a configuration change.
Inspect Discovery History
| Column | What to check |
|---|---|
| Date | When the scan ran |
| Entities | The run's discovered record count |
| Time Taken | How long the scan took |
| Integrations | Which connected instances contributed to the scan |
| Knowledge | Opens the published discovery inventory in workspace Knowledge Hub, when available |
| Status | Whether collection completed successfully or needs attention |
Use Rows per page and pagination to find an older run. The Knowledge document provides more detail than the summary tiles. A partial run can still publish knowledge from collectors that succeeded, so review the result before assuming all selected integrations were covered.
Private-network access
If the page shows Install a remote runner for in-VPC investigations, select Set up runner and follow the Remote Runners guide. Attach the runner to the SRE investigator agent so supported commands can reach resources inside your network.
If results are empty or incomplete
- No connected instances: Check the selected workspace and integration attachment.
- No entities: Verify source credentials, permissions, reachability, and that the source contains telemetry or inventory.
- No insights: Insights can still be generating after collection; also check whether entities were discovered.
- An expected environment is missing: Confirm the intended integration instance was selected and inspect the run's knowledge document.
- A scan succeeds but investigation access fails: Inspect the investigation's Events panel. Collection and a later query can require different permissions or network access.
Once coverage is useful, return to Alerts and investigate a representative signal.