Solutions

  • Products
  • Use Cases
  • Industries
  • EBOOK
  • Making it #EasyForEmployees
  • A guide with best practices for transforming the employee service experience.
  • WHITE PAPER
  • Modernizing government via ITSM
  • A research doc about government agencies’ digital transformation challenges.

Platform

  • REPORT
  • Gartner names ServiceNow a leader
  • 2018 Magic Quadrant for Enterprise High-Productivity Application PaaS.

Customers

  • CUSTOMER STORY
  • General Mills transforms HR
  • Global employee service experience shows entire corporation how it’s done.

Explore

  • PERSPECTIVE
  • Do you need an AI council?
  • Formal collaboration helps implement new technology safely and effectively.

Collect data and populate scores

Build snapshots of your performance to measure progress toward goals.

  • To see your historical and daily process performance, run Performance Analytics data collection jobs.

Data collection jobs gather the indicator and breakdown data that will show up on your dashboards and in your widgets. This is what drives the snapshot nature of Performance Analytics data, so you can see how the measurements change day by day.

Step 1: Run a historical data collection job

First, run the historical data collection job to assemble the scores for existing records up to the current date.

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Expert Tip

EXPERT TIP

Only run historical jobs once per ServiceNow product upon initial configuration.

Historical jobs are configured by default to run only on demand. Resist the urge to schedule or repeatedly run these jobs!

To start a historical data collection job:

  1. Navigate to Performance Analytics > Data Collector > Jobs.
  2. Click a job with “Historic” in the title to view its details.
  3. Review the job details, especially the Relative Start field in the Collection Parameters section. Each of the historical data collection jobs are configured to retrieve up to 60 days of data by default. To adjust the amount of historical data collected, increase or decrease the Relative Start value. You can also change the Operator to Fixed and set a specific date range by completing the Fixed Start and Fixed End fields.
  4. Click Update to save your changes.
  5. Click Execute Now to start the job. The duration of the job will vary depending on the record count in your ServiceNow instance.

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Figure 3: Starting a historical data collection job

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Step 2: Schedule a daily data collection job

After you run the historical data collection job, you must schedule daily or recurring data collection jobs. These jobs will update the Performance Analytics scores and snapshots daily, building on the data that the historical job already collected.

Set at least one of the daily data collection jobs to Active status before you move on to the next stage. Failure to set up a recurring data collection job will result in stale scores that only reflect your historical data. To monitor a process over time, you need to configure a daily data collection job.

To schedule a daily data collection job:

  1. Navigate to Performance Analytics > Data Collector > Jobs
  2. Click a job with “Daily” in the title to view its details. 
  3. In the Job Parameters section, select the Active check box. 
  4. Check the Time field, which shows when the job will run. ServiceNow recommends setting the job to run shortly after midnight in the instance’s time zone in order to collect a full day’s worth of data. 
  5. Ensure the Run As field is set to a user role with rights to read the indicator source tables. 

Click Update to save your changes.

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Figure 4: Scheduling a daily data collection job in Performance Analytics 

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Step 3: Validate the data collection job logs

The last step in the data collection stage is validating the log files to ensure that your historical and recurring jobs are running without any issues.

  1. Navigate to Performance Analytics > Data Collector > Job Logs.
  2. Scan the list of records. The State field for jobs that ran without any issues are marked as Collected with a green circle indicator.

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Figure 5: Job logs in Performance Analytics

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Review the job details, especially the Relative Start field in the Collection Parameters section. Each of the historical data collection jobs are configured to retrieve up to 60 days of data by default. To adjust the amount of historical data collected, increase or decrease the relative Start value. You can also change the Operator to Fixed and set a specific date range by completing the Fixed Start and Fixed End fields. 

If the state of a job is marked as Collecting, the job is still in progress. Click the name of any completed job with data in the Warnings or Errors columns to receive a full report of actions taken and to investigate any problems. For help with any issues, see the Data collection process and logging product documentation.

MID Server

Each MID Server is a lightweight Java process that can run on a Linux, Unix, or Windows server. During discovery, the MID Server executes probes and patterns and returns the results back to the instance for processing. It doesn’t retain any information.

 

Before you continue, make sure you:

  • Ran a historical data collection job one time
  • Ran and scheduled a daily data collection job
  • Validated that the jobs ran successfully using the logs

Related tools and resources

Explore additional phases

Plan

You want to be sure everything is in place for a smooth, successful deployment.

Deploy

You want to be sure you’re following best practices during implementation.

Optimize

You’re up and running and want to get the most from your investment.

Extend

You’re ready to extend ServiceNow into other areas of your enterprise.

Thank You

Thank you for submitting your request. A ServiceNow representative will be in contact within 48 hours.

form close button

Contact Us

I would like to hear about upcoming events, products and services from ServiceNow. I understand I can unsubscribe any time.

  • By submitting this form, I confirm that I have read and agree to the Privacy Statement.