- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
In step one we talked about Indicator Sources. Step two will we address Breakdown sources.
A Breakdown is a way to segment or slice your indicator data so you can analyze KPIs across different dimensions, such as Assignment Group, Priority, Location, or Category.
Can you use the same breakdown across multiple tables? For example, Assignment Group exists on Incident, and Change. Answer is Yes, absolutely, but you need to add a breakdown mapping so the “Assignment Group” breakdown knows which field to look at when it is reporting on your data.
Setting up a Breakdown Source is a three-step process that defines how ServiceNow will segment your Performance Analytics data.
Step 1 is to set the (facts) table and the field (typically sys_id):
Step 2 you define the field you want to use. In example below, Assignment Group:
Step 3 is where you add the table and field. In below example, you can see assignment group has different names across different tables:
There is also a breakdown source called Bucket. A bucket breakdown source allows you to group numeric or date-based data into defined ranges (buckets) rather than relying on a single field’s discrete values. It’s used when you want to segment your indicator data by value range:
- Incident age (0–3 days, 4–7 days, >7 days)
While it uses some scripting to make it work, you can typically copy another script from a bucket breakdown source and modify it to meet your needs.
In the next step we will talk about Job Collectors.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
