Data collector properties

Data collector properties allow you to configure various limits for Performance Analytics data collection.

The data collector properties are configured to safeguard the data collection process. The default values are appropriate for most environments.

Navigate to Performance Analytics > Properties to configure properties.

Table 1. Performance Analytics Data Collector properties
Property Description The maximum time in seconds that a script is allowed to run during a data collection cycle, such as an indicator source script or a breakdown script.

This limit applies individually for each record processed by the data collection job. If a script exceeds this limit, the current record is skipped by the data collection job.

If your scripts frequently reach the default limit, simplify the scripts as much as possible before modifying this property.

  • Type: integer
  • Default value: 30 The maximum number of records that a job can collect from a single indicator source.

Increasing this value may cause data collection jobs to take longer to complete.

This limit applies separately to each indicator source included in a data collection job. The number of indicators associated with each indicator source does not affect this limit.

For example, if a data collection job collects scores for twelve indicators from three indicator sources, the job can collect a maximum of 150,000 records by default, 50,000 from each indicator source.

  • Type: integer
  • Default value: 50,000 Maximum number of breakdown elements for a breakdown to be included in data collection. You may encounter this limit when defining a breakdown based on a reference field, such as the Assigned to or Configuration item fields.

Increasing this limit may impact performance when viewing breakdown information on a detailed scorecard. Additionally, it may be difficult for users to access data for a specific breakdown element when there are a very large number of elements.

If you have more breakdown elements than this limit, consider defining a breakdown based on a bucket group instead. Bucket group allow you to maintain a managable number of breakdown elements, and simplify navigation for users viewing the broken-down data.

  • Type: integer
  • Default value: 10,000 The maximum number errors that may occur for a single data collection job run before data collection is stopped.

Errors during data collection usually occur due to an invalid script, or when encountering the script timeout limit.

Do not increase this value. If you encounter this limit, review any scripts that run during data collection to ensure they are valid and perform as expected.

  • Type: integer
  • Default value: 500 Maximum number of breakdown elements resulting from the combination of two breakdowns for a data collection. For example, if the first-level breakdown has 10 elements, and the second-level breakdown has 5, 50 breakdown elements are collected.

Increasing this limit can cause the Scores [pa_scores] table to store a very large number of records. Having many records on this table may impact performance when performing operations on the Scores table, such as when calculating formula values for formulas with breakdowns.

Note: This limit is also affected by the property. For example, if the first-level breakdown has greater than 10,000 elements, only 10,000 are collected by default. In this scenario, the second-level breakdown can specify at most 100 breakdown elements before reaching the default second-level limit of 1,000,000 total elements.
  • Type: integer
  • Default value: 1,000,000 Maximum number of records that are stored on the Snapshots [pa_snapshots] table during each data collection. This limit applies only when Collect records is selected for an indicator. This limit does not apply to scores.

Generally, the default limit provides enough detail into collected records. Increasing this limit may impact performance during data collection or when performing operations on the Snapshots table.

  • Type: integer
  • Default value: 5000