Performance Analytics for Incident Management is enabled for all instances starting with Eureka. This functionality is configured to work with default Incident table columns. On instances that upgraded to Eureka, these columns may not exist. For example, Performance Analytics uses the "resolved_at" column from the Incident table. For instances that upgraded to Eureka, this column has the name "u_resolved_at" instead.

Steps to Reproduce

  1. Open an instance with a version earlier than Eureka installed.
  2. Upgrade the instance to Eureka or a later version.
  3. Activate the Performance Analytics for Incident Management plugin.
  4. Run a Performance Analytics data collector job for the Incident table.
    The data collector job ends with the state Collected with errors and the data collector job log contains an error similar to the following:

    Invalid query conditions: <list of query conditions>
    --> Fetched too many rows from indicator source <indicator source>
    --> Error Error during JavaScript evaluation java.lang.IllegalStateException: Sparse storage format has one field, sys_id at com.glide.db.meta.SparseStorage.getValue(SparseStorage.java:70)


  1. Run the attached script named Validate.PluginData.js.
    This script checks for all objects and columns that are needed. Script results are written to the Plugin Activation logs for the Performance Analytics (ID: com.snc.pa) plugin as warnings. If the script is successful, no warnings are written. The warnings tell you about any Performance Analytics objects that are missing.
  2. Reconfigure the Performance Analytics content plugin so it matches your data structure.
  3. Re-run the script to ensure that you have resolved all warnings.

Related Problem: PRB654826

Seen In

Geneva Patch 5
Geneva Patch 7
Helsinki Patch 3

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-01-19 02:43:19