Skip to content

Architect track

Dashboards & analytics

Reports, Platform Analytics dashboards and Performance Analytics, designed to scale.

4 sections · 24 entries

Performance Analytics building blocks

Real-time reports answer "what is happening now". PA answers "are we getting better".

  1. Indicator sourceTable + conditions + collection frequency. The population you measure.
  2. IndicatorThe KPI: count, sum or average over the source. Automated, formula or manual.
  3. BreakdownSlice a KPI by group, priority, category. Breakdown sources define the members.
  4. Data collector jobScheduled job that stores daily scores (and snapshots) per indicator and breakdown.
  5. DashboardScore widgets, trends, targets and thresholds, shared by role or group.

Analytics tables

Handy when you need to audit or bulk-review analytics config.

Every report on the instance, with owner and sharing
PA indicator sourcesHidden gem
PA indicators
PA breakdowns
PA dashboards (legacy responsive dashboards)
PA data collector jobsHidden gem
Data collector job logs: why yesterday’s scores are missingHidden gem

Report, PA or database view?

Choose the cheapest tool that answers the question.

QuestionUseWatch out for
How many open P1s right now?Real-time report / single scoreKeep conditions indexed
Is MTTR improving month over month?PA indicator with breakdownsCollect daily; backfill with a historic job
Trend of a field that changes over timePA snapshot or metric definitionsPlan it before go-live; history is hard to rebuild
Join two tables for one reportDatabase view (sparingly)Can be slow on big tables; filter tightly
Executive scorecard with targetsPA dashboard with targets and thresholdsAgree KPI definitions before building

Dashboard best practices

Dashboards people open every morning, not once.

  • ✦One question per dashboard. Design around a decision someone makes, not around available data.
  • ✦Lean tabs. Every widget is a query. Fewer widgets per tab load faster and get read.
  • ✦Interactive filters. One dashboard with filters beats ten near-identical copies.
  • ✦Avoid heavy tables. Never report directly on sys_audit, sys_journal_field or syslog for dashboards.
  • ✦Share by role or group. Not by individual user; it outlives reorganisations.
  • ✦Platform Analytics. New dashboards go in the Next Experience Platform Analytics experience; plan migration of legacy homepages and dashboards.
  • ✦Governance. Owner, purpose and review date on every shared dashboard. Retire unused ones quarterly.Hidden gem

Snippets are provided as-is under the MIT licence, without warranty. Test in a sub-production instance first. ServiceNow is a trademark of ServiceNow, Inc.; this page is independent and not affiliated with or endorsed by ServiceNow.