Performance Analytics properties

These system properties control the behavior of Performance Analytics.

To configure properties, navigate to Performance Analytics > Properties or to sys_properties.list.

Collection cleanup properties

Several properties determine how long Performance Analytics scores and snapshots are maintained before being deleted by the scheduled cleanup job.
Property Description
com.snc.pa.dc.keep_scores_for.frequency Maximum number of periods that scores will be kept before being deleted, for each indicator frequency, such as Daily or Weekly.

The length of each period depends on the indicator frequency. For example, daily scores are kept for 732 days by default, or weekly scores for 105 weeks.

Additionally, scores older than this limit are not collected during data collection.

  • Type: String
  • Default value: 732;105;53;40;60;30;20;20;20;10;10
  • Location: Performance Analytics > System > Properties
com.snc.pa.dc.keep_snapshots_for.frequency Maximum number of days the snapshots related to a score will be kept before being deleted for each indicator frequency, such as Daily or Weekly.

The unit of each period depends on the indicator frequency. For example, daily snapshots are kept for 183 days by default, or weekly snapshots for 26 weeks.

Additionally, snapshots older than this limit are not collected during data collection.
  • Type: String
  • Default value: 183;26;13;10;15;8;5;5;5;3;3
  • Location: Performance Analytics > System > Properties

Fiscal year properties

These properties set the year in Performance Analytics to match your company fiscal year.

Property Description
com.snc.pa.fy_start Start of the fiscal year of your company

Data collector properties

Data collector properties enable you to configure various limits for Performance Analytics data collection. The properties are configured to safeguard the data collection process. The default values are appropriate for most environments.

Property Description
com.snc.pa.dc.script_timeout 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
com.snc.pa.dc.query_time_limit The maximum duration in minutes that a single query for a data collection job can run before a warning is logged.
  • Type: integer
  • Default value: 60
com.snc.pa.dc.max_row_count_indicator_source The maximum number of records that a job can collect from a single indicator source.
Warning: If an indicator source contains a number of records higher than the value of this property, no indicators are collected for this 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
com.snc.pa.dc.max_breakdown_elements_limit 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 groups enable you to maintain a manageable number of breakdown elements, and simplify navigation for users viewing the broken-down data.

  • Type: integer
  • Default value: 10,000
com.snc.pa.dc.max_error_count 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
com.snc.pa.dc.max_breakdown_elements_level2_limit 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 data collection to use a large amount of memory which may impact performance.

This limit is also affected by the com.snc.pa.dc.max_breakdown_elements_limit 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
com.snc.pa.dc.max_records 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
com.snc.pa.breakdown_element_cutoff Maximum number of elements that a breakdown can have for the elements without scores to be shown in a scorecard. If the value of this parameter is exceeded, no scoreless elements are shown in the scorecard.

Example: The value of the parameter is 10. Breakdown A has 8 elements. All 8 are shown in the scorecard. Breakdown B has 12 elements, of which 5 have scores. Only those 5 elements are shown.

Notes:
  • This parameter does not affect whether unmatched elements are shown.
  • If the element involves a formula with multiple scores, the element is considered to have a score if all parts of the formula have scores at any point in time. The formula is considered to have a score even if the result is invalid, such as a division by 0.

Target and Threshold properties

Table 1. Target properties
Property Description
com.snc.pa.default_chart_personal_target_color The line color for personal targets displayed on scorecards.
  • Type: string
  • Default value: #BDC0C4
Table 2. Threshold properties
Property Description
com.snc.pa.default_chart_personal_threshold_color The line color for personal thresholds displayed on scorecards.
  • Type: string
  • Default value: #BDC0C4
com.snc.pa.thresholds.frequency_intervals_in_the_past The maximum number of frequency intervals in the past that a threshold check job will analyze.
  • Type: integer
  • Default value: 2