Monitoring Dashboards#
Note
This section covers operational monitoring (infrastructure metrics — Azure Monitor, CloudWatch, GCP Cloud Monitoring). For cost monitoring (spend dashboards, budgets, report scheduling), see FinOps → Monitor Dashboards.
The Monitoring module provides fully native dashboards built directly on top of each cloud provider’s metrics and log APIs. Dashboards are composed of configurable widgets, saved per tenant, and can trigger Alert Rules that notify you when a metric crosses a threshold.
Navigate: left navigation → Monitoring → Dashboards.
The dashboard canvas#
A Monitoring dashboard is a free-form grid of widgets. Each widget independently queries one or more cloud connections and renders the result as a chart, stat, table, or alert list.
Layout#
The grid is 12 columns wide; each widget occupies a configurable number of columns and rows
Drag widgets to reposition; resize from the bottom-right handle
Changes are auto-saved when you stop dragging
Setting a default dashboard#
Mark one dashboard as the default to make it the landing page every time you open Monitoring. Only one dashboard can be the default at a time — setting a new default automatically unsets the previous one.
Creating a dashboard#
Navigate to Monitoring → Dashboards
Click “+ New dashboard”
Give it a name (required, max 64 characters) and optional description
The dashboard opens with an empty canvas — add widgets from the “+ Add widget” button
Widgets#
Widget types#
Type |
What it shows |
|---|---|
Timeseries |
Line chart of one or more metrics over time |
Stat |
Single numeric value (e.g. current CPU, total cost) |
Table |
Tabular results from a log query |
Alert List |
Active alerts from the cloud provider’s alert management API |
Configuring a widget#
Each widget has a query definition specific to its provider and query type:
Query type |
Provider |
Config fields |
|---|---|---|
Azure Metrics |
Azure |
Subscription resources, metric name, aggregation, dimension filters |
Azure Log Analytics |
Azure |
KQL query, Log Analytics workspace |
Azure Alerts |
Azure |
Severity filter, max results |
AWS CloudWatch Metrics |
AWS |
Namespace, metric name, dimensions, statistic |
AWS Logs Insights |
AWS |
Log group, CloudWatch Insights query |
AWS Alarms |
AWS |
State filter, alarm name prefix, namespace filter |
GCP Cloud Monitoring Metrics |
GCP |
GCP project, metric type, alignment period, reducer |
GCP Alert Policies |
GCP |
Filter expression |
Time range#
A widget’s time range can be set to a preset (last 1 h / 3 h / 12 h / 24 h / 7 d / 30 d) or a custom absolute range. Widgets on the same dashboard can have independent time ranges.
Import & export#
Dashboards can be exported to a .welkin-dashboard JSON file and imported to other tenants. This is useful for sharing standard monitoring templates across environments.
Export: Dashboard options menu → Export Import: Dashboards list → Import → select file
Note
All widget IDs are regenerated on import to prevent collisions. Connection references inside widgets are preserved by connection ID — make sure the same connections exist in the target tenant.
Alert Rules#
Alert Rules evaluate a monitoring query on a configurable schedule and fire a notification when a threshold condition is met. See Alert Rules for the full reference.
Permissions#
Action |
Required permission |
|---|---|
View dashboards and run queries |
|
Create, edit, delete dashboards |
|
View alert rules and history |
|
Create, edit, delete, evaluate alert rules |
|
Delete alert rules |
|
The built-in Monitoring Reader role grants all Read permissions. The built-in Monitoring Contributor role grants all Read and Write permissions.
Troubleshooting#
For troubleshooting guidance — widget errors, missing data, import issues — see Troubleshooting → Monitoring Errors.