Phone:400-882-3320
Multiple observability signals
Organize metrics, logs, traces, events, and supported external sources in one dashboard.
Documented capabilities
These capabilities are grounded in the current Guance dashboard and scene documentation. Availability can vary by data type, component, edition, and workspace permissions.
Organize metrics, logs, traces, events, and supported external sources in one dashboard.
Use simple queries, DQL, PromQL, view variables, chart links, and filters for multidimensional analysis.
Use visibility settings, shared links, embeds, and scheduled reports for the intended audience.
A useful dashboard answers what changed, who is affected, and where to investigate next. Guance connects charts and queries to object context and underlying records so a summary can lead into incident analysis.
Inconsistent context:
Business, application, infrastructure, and alert data use different time ranges, objects, and labels.
Display without investigation:
A static trend shows that something moved but offers no path to the affected service, log, trace, or object.
Unmanaged publishing:
Without ownership, variables, permissions, and review dates, teams accumulate conflicting dashboard copies.
Create shared context:
Align time, service, environment, region, release, and business-object tags before composing charts.
Connect summaries to evidence:
Use variables, links, and viewers to move from an anomaly to logs, traces, and object details.
Publish by audience:
Give executives, business teams, SREs, and developers focused views with explicit access boundaries.
Combine Metrics, Logs, Traces, and Events around services, environments, releases, regions, or business entities.
Let view variables update multiple charts and use chart links or viewers to continue into logs, traces, and performance details.
Use visibility, links, embeds, and scheduled reports while checking data permissions and link lifetime before external distribution.
Bring in observability and required business data, then standardize service, env, version, region, and business-object tags.
Define the questions executives, operators, SREs, and developers must answer before choosing queries, windows, and chart types.
Use view variables and links to connect the summary to logs, traces, viewers, and related dashboards.
Record the owner, visibility, share-link lifetime, report schedule, and review cadence so the dashboard stays trustworthy.
Track errors, latency, throughput, and dependencies by service, environment, and release.
Bring hosts, containers, cloud resources, and capacity risks into one resource view.
Summarize active events, affected objects, and the next investigation path.
Compare orders, payments, conversion, and API performance in the same time window.
View volume, experience, and system status by location, region, or channel.
Keep a small set of decision metrics with a traceable path to technical evidence.
Guance dashboards cover observability queries, charts, interaction, sharing, and reports. Digital-twin 3D modeling, external-system integration, and custom visual production are separately scoped services. Capability review date: August 17, 2026.
BI dashboards usually emphasize business reporting. Observability dashboards emphasize live signals, alert context, object relationships, and investigation. They can share business measures while serving different response tasks.
Current documentation lists simple queries, DQL, PromQL, and supported external data sources. The exact options depend on the data type, component, and edition.
View variables, chart links, and viewers can form a drill-down path. Define the destination, filters, and access permissions as part of dashboard design.
Standard dashboards provide documented charts, maps, media, and embedding options. 3D modeling, field-system integration, and custom interaction require separate project scoping.