Monitoring Integration
Connect Prometheus, Grafana, Loki, and ServiceNow to give Damira real-time visibility into your network.
Connect your monitoring stack and Damira pulls metrics, alerts, and logs automatically during troubleshooting. No more switching between tools — ask a question and Damira checks your monitoring systems first.
Supported Integrations
| Tool | What Damira Does | Access |
|---|---|---|
| Prometheus | Query metrics, check active alerts, discover devices from scrape targets | Read-only |
| Grafana | Search dashboards, pull alert states, check panel data | Read-only |
| Loki | Search logs by label, time range, and content. Pull log context around events | Read-only |
| ServiceNow | List incidents, create tickets, update ticket status, create change requests | Read + write (with approval) |
All monitoring queries are read-only. Damira never modifies your monitoring configuration.
Setup
VS Code Extension Settings
Open VS Code Settings (Cmd+,) → search "Damira" → Monitoring section:
| Setting | Example |
|---|---|
| Prometheus URL | https://prometheus.yourcompany.com |
| Grafana URL | https://grafana.yourcompany.com |
| Loki URL | https://loki.yourcompany.com |
| ServiceNow Instance | yourinstance (just the subdomain) |
| ServiceNow Username | admin |
| ServiceNow Password | Stored securely in VS Code secrets |
Integration Picker
The Settings panel includes a category-based integration picker. Check the boxes for the tools you use and fill in the connection details. Damira only loads tools for integrations you've configured.
How It Works During Troubleshooting
When you report a problem like "BGP is down on WAN-RTR-01", Damira automatically:
- Queries Prometheus — checks
frr_bgp_peer_state, interface metrics, and active alerts - Checks Grafana alerts — looks for any firing alerts related to the device
- Searches Loki logs — pulls recent log entries containing BGP or the device name
- Reports findings — tells you what it found before asking you to run any CLI commands
You only need to provide manual CLI output for data your monitoring doesn't cover.
Device Discovery
Damira can discover your network devices from Prometheus scrape targets:
"Discover my devices from Prometheus"
This pulls device hostnames and IPs from your Prometheus target configuration and populates the Devices sidebar in VS Code. Discovered devices are available as context in all subsequent conversations.
ServiceNow Tickets
Damira creates properly structured ITSM tickets:
- Incidents — with category, subcategory, assignment group, priority, and affected device (CMDB CI)
- Change requests — with implementation plan, risk assessment, and rollback procedure
Tickets are created only when you explicitly ask for them. Damira presents a confirmation gate before creating any ticket — you see exactly what will be created and approve or modify before it's submitted.
Ticket Fields
| Field | How It's Set |
|---|---|
| Category | Auto-detected from the issue type (Network, Hardware, Software) |
| Priority | Based on impact and urgency from the conversation |
| Assignment Group | NOC for P1/P2, Network Engineering for P3/P4 |
| Affected Device | Linked to CMDB CI if the device exists in ServiceNow |
| Description | Structured template: Impact, Detection Method, Affected Devices, Symptoms |
Prerequisites
- Tier: Starter or above for Prometheus/Grafana. ServiceNow available on all paid tiers.
- Monitoring endpoints must be reachable from your VS Code machine (or via VPN/tunnel)
- ServiceNow requires a Personal Developer Instance (PDI) or production instance with API access
Related
- Troubleshooting — How monitoring data feeds into diagnosis
- Security — How monitoring credentials are handled
- VS Code Extension — Extension settings and configuration