Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 39 ยท ITSM and Administration

Dashboards, Analytics and Knowledge Management

Create ServiceNow reports and dashboards, understand Performance Analytics, and run a knowledge base with articles, workflow, feedback and deflection metrics.

Managers want numbers: how many incidents are open, how fast we resolve them, which categories grow. Agents want answers: has anyone solved this before? ServiceNow serves both needs with reports and dashboards for the numbers and knowledge management for the answers. They also feed each other, because knowledge that deflects tickets shows up in the metrics.

Reports and knowledge live on an instance. This lesson describes the menus and rules; the runnable blocks are JavaScript stand-ins that compute the same figures from sample data.

Building a report

Open Reports > Create New (or the Reports application's View / Run). The builder asks for:

  1. Data: a table (for example incident) or a database view or data source.
  2. Type: bar, column, pie, donut, line, area, spline, step, pivot table, list, heatmap, histogram, calendar, gauge, single score, control and others.
  3. Group by, Aggregation (Count, Sum, Average, Min, Max) and the field.
  4. Filter conditions, the same filter builder as lists.
  5. Style, title, colors, and Sharing (everyone, groups, roles or just you).

A good report has a title that states the question ("Open P1 and P2 incidents by assignment group") and a filter that matches it. You can also schedule a report by email, as PDF or CSV.

Report access follows ACLs: a user can only report on rows they could read, so two people may see different counts from the same report.

Dashboards

A dashboard (Dashboards > Overview) arranges widgets (reports, single-score tiles, lists) in tabs, with filters that apply across them. Use dashboard filters to let viewers pick a group or date without cloning the dashboard. Keep the first screen focused: five to eight numbers that lead to action beat thirty charts.

Performance Analytics

Standard reports show now. Performance Analytics (PA) adds history: it takes snapshots of an indicator every day (for example "Number of open incidents") and builds time series, targets and thresholds. A PA Indicator is a measure, a Breakdown is a way to slice it (by group, by priority), and a Data Collection job gathers values on a schedule. PA is a separately licensed capability. Use it for trends and targets such as "mean time to resolve below 8 hours".

Useful metrics in ITSM:

Metric Meaning
MTTR Mean time to resolve incidents
First contact resolution Share solved without reassignment
Backlog Open incidents older than a threshold
SLA attainment Share of task SLAs achieved
Reopen rate Share of resolved incidents reopened

Compute metrics carefully: decide how to treat on-hold time, business hours and canceled records, and write the definition down.

JS Stand-in: count by group and compute MTTR

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Knowledge management

The Knowledge application stores articles that answer questions. Structure:

  • Knowledge base (kb_knowledge_base): a collection with an owner and access rules, such as "IT" or "HR".
  • Category: topics within the base.
  • Article (kb_knowledge): the content, with a Short description, Text (rich editor), Valid to (expiry date), Meta (keywords) and attachments.
  • User criteria: who can read or contribute (by role, group, company, location).

Article life cycle

Typical states: Draft, Review, Published, Outdated, Retired. A knowledge base can use instant publish (authors publish directly) or approval publish (review before release). Editing a published article creates a new version, and the old one stays in history. Valid to dates remind owners to review before the content rots, and a scheduled job moves expired articles to Outdated.

Using knowledge

  • Agents search from the incident form and attach an article to the record, which counts as use.
  • Portal users search from the Knowledge Search widget and see articles matched by user criteria.
  • Agents can create an article from a resolved incident with Create Knowledge, which pre-fills the resolution notes.
  • Feedback: users can rate articles (helpful or not) and comment. Flagging reports an inaccurate article.
  • Deflection: when a portal user finds an article and does not open a ticket, that is a deflection. Track the self-service ratio: deflected cases over total contacts.

Write good articles: answer the question in the title ("How to reset your VPN password"), put the fix first, number the steps, state which versions apply, and review them on a schedule.

JS Stand-in: article usefulness and expiry

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What do you choose first when building a report?

    A report starts with its data: a table, a database view or another data source.
  2. 2. What does Performance Analytics add beyond ordinary reports?

    PA collects indicator values on a schedule, so you can see change over time.
  3. 3. Why does the same report show different counts to two users?

    Reports respect row-level access, so each person sees only what they may read.
  4. 4. What is a deflection in knowledge management?

    Deflection means self-service avoided a ticket; it is a key knowledge success measure.

Summary

  • Reports use a table, filter, grouping and chart type; dashboards combine reports with shared filters.
  • Performance Analytics adds history, targets and breakdowns.
  • Knowledge bases hold articles with versions, review states, user criteria, feedback and expiry dates.
  • Define metrics carefully and treat knowledge as living content.

Next: Project: Automate Incident Triage