Getting Started
- Navigate to any asset’s Intelligence tab
- Click Ask Agent in the top right
- Type a question or request in plain English
What Makes It Powerful
The Web Agent isn’t just a chatbot. When you ask a question, it:- Reads your monitoring context: Schema drift history, freshness status, data quality metrics, tags, lineage, and alert rules for the selected asset
- Chains tools automatically: A single question can trigger multiple tool calls across domains
- Shows its work: Every tool call is visible with parameters and results, so you can verify what the agent is doing
Example: Diagnosing a Problem
Capabilities by Domain
Discovery
Browse your data assets without leaving the chat.Monitoring Setup
Set up freshness schedules, schema monitoring, and data quality metrics in one conversation.Alert Management
View, acknowledge, resolve, or dismiss alerts. The agent shows context from monitoring data alongside each alert.Data Quality
Create metrics and validity rules. The agent asks for confirmation before creating anything.Schema Drift
Review changes, trace their origin, and understand downstream impact.Tags and Classification
Apply and manage tags for organization and compliance.Sessions
Conversations are organized into sessions. Each session maintains full context, so follow-up questions work naturally.- New session: Click + in the session sidebar
- Resume session: Click a previous session to continue where you left off
- Pin session: Pin important sessions to the top of the list
- Session history: Sidebar shows all past conversations with timestamps and message counts
Tool Visibility
As the agent works, you see each tool call in real time:- Which tool was called (e.g.,
list_schema_changes,check_freshness) - What parameters were passed
- The result returned
Tips
- Be specific about scope: “Check freshness for the 3 gold fact tables” works better than “check everything”
- Chain requests: “Find tables with spiking null rates, then show me their schema changes” works in one message
- Ask diagnostic questions: “Why is X broken?” triggers cross-domain investigation, which is where the agent is strongest
- Let it discover first: Say “find tables with customer data” instead of typing exact table paths
- Review before acting: For bulk operations, ask “what tables match?” before “set up monitoring for all of them”
Available Tools
| Domain | Count | Capabilities |
|---|---|---|
| Discovery | 7 | Browse assets, catalogs, schemas, tables, columns |
| Freshness | 4 | Check freshness, find stale tables, create schedules, get recommendations |
| Schema | 3 | List changes, view details, enable monitoring |
| Data Quality | 3 | Create metrics, list existing, view health summary |
| Validity | 3 | Create rules, list existing, view results |
| Alerts | 4 | List alerts, view details, list rules, create rules |
| Alert Actions | 5 | Acknowledge, resolve, dismiss, snooze alerts |
| Tags | 2 | List and apply tags |
| Health | 1 | Overall health summary |
Next Steps
Intelligence Overview
How monitoring context powers the agent’s answers
MCP Server
Use the same tools from your IDE
Status Skill
Health monitoring details
Alerts Skill
Alert management details
