SigNoz
Why SigNozDocs
PricingCustomer Stories
Docs
IntroductionContributingMigrate from DatadogSigNoz API
OpenTelemetry
What is OpenTelemetryOpenTelemetry Collector GuideOpenTelemetry Demo
Community
Support
Slack
X
Launch Week
Changelog
Dashboard Templates
DevOps Wordle
Newsletter
KubeCon, Atlanta 2025
More
SigNoz vs DatadogSigNoz vs New RelicSigNoz vs GrafanaSigNoz vs Dynatrace
Careers
AboutTermsPrivacySecurity & Compliance
SigNoz Logo
SigNoz
All systems operational
HIPAASOC-2
SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

Dashboard Creation from Natural Language

You need to monitor a new microservice you just deployed, but building a dashboard from scratch means clicking through metrics, logs, and traces and configuring visualization panels.

You open your AI assistant, connected to SigNoz via the MCP server, and ask it to build the dashboard for you.

Prerequisites

  • Connect your AI assistant to SigNoz using the MCP Server guide.

Step 1: Create the Dashboard from a Natural Language Prompt

Confirm the recommendation service is sending data. Then search for its relevant data and create a dashboard with three panels: p99 latency, error rate, and request throughput.

Your assistant will first verify the service exists and is actively sending telemetry data, then build the dashboard:

āœ“ Service confirmation: The recommendation service is actively sending data
  - 3,342 calls over the last 24 hours
  - Primary operation: oteldemo.RecommendationService/ListRecommendations
  - Current error rate: ~4.28%

āœ“ Dashboard created: "Recommendation Service Overview"
  - Dashboard ID: 019dad7d-a6b2-7269-b5a0-65e0ebd42924

Three panels configured (all scoped to service.name = 'recommendation' over last 24h):

1. P99 Latency (top-left)
   - Metric: p99(durationNano) on traces
   - Visualization: Time series

2. Error Rate (%) (top-right)
   - Formula: (error spans / total spans) Ɨ 100
   - Visualization: Time series

3. Request Throughput (req/s) (full-width, bottom)
   - Metric: rate() on traces
   - Visualization: Time series

You can open it in SigNoz under Dashboards → "Recommendation Service Overview"

The dashboard is now live with all three panels displaying real-time metrics for the recommendation service.

Final Summary

You now have a fully functional dashboard created from just using a simple prompt.

Recommendation Service Dashboard
Recommendation Service Dashboard Overview
Recommendation Service Dashboard Detailed View
Recommendation Service Dashboard Detailed View

Under the Hood

During this workflow, the MCP server called these tools:

StepMCP ToolWhat It Did
1signoz_list_servicesVerified the recommendation service exists and is actively sending telemetry data
1signoz_aggregate_tracesRetrieved p99 latency, error rate, and request throughput metrics over the last 24 hours
1signoz_create_dashboardCreated the dashboard with three panels configured for the recommendation service

Related Use Cases

  • Incident Specific Dashboard Spin-Up - Instantly generate focused dashboards for active incidents with relevant metrics and traces.
  • Alert Correlation Analysis - When multiple services alert simultaneously, identify whether it's a cascade from one failure or separate incidents.
  • Post Deployment Monitoring - Compare key metrics before and after a deployment to detect performance regressions or unexpected changes.

If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack.

If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.

Last updated: May 3, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

Prev
Trace Failing Request
Next
Incident Specific Dashboard Spin-Up
On this page
Prerequisites
Step 1: Create the Dashboard from a Natural Language Prompt
Final Summary
Under the Hood
Related Use Cases

Is this page helpful?

Your response helps us improve this page.