Troubleshooting Envision

Troubleshooting resources and tips for Envision.

Table of Contents

Data not showing up as expected: data type mismatch

Data can come in to Envision via the Gateway, or a third-party application can add data to Envision using a custom connector.

When Envision rolls up data, from either of these sources, it validates that the data is of the data type specified in the dataset definition; for example, text, numeric, or ZIP code. Data that is not the correct data type is ignored. As a result, if there is a mismatch between the dataset definition and the data coming in, the data representation will not be correct.

If you are not seeing your data, check the data types defined for your dataset dimensions, and make sure that the input data conforms.

Data not showing up as expected: remote writer not enabled

As part of configuring Envision, you might need to enable remote writing on the Gateway manually, as covered in the Policy Manager / Envision Integrated Installation document: Step 5: Modify Usage Writer Properties.

If you're not seeing the expected data in Envision, go to the Akana Administration Console for the Policy Manager container, and verify that remote writing is enabled.

Slow performance

If there are performance issues, review the guidelines in these two documents to make sure your datasets are designed efficiently:

  • Chart Building Guide for Envision—Provides information to help you make design decisions for using Envision.
  • Dataset Building Guide for Envision—Includes guidance for balancing information detail and performance efficiency to represent the information that's important to you in a way that will be timely and resource-efficient.

Checking for startup errors

If for any reason some of the Envision file bundles do not start up correctly, you might see one or more issues such as:

If there are problems, make sure that there are no startup errors in your Envision container, and verify that all the bundles have started. If necessary, restart the container.

For information about reviewing startup errors, restarting the container, and other general troubleshooting tips, refer to Troubleshooting Content Overview and linked files. For example:

Updating the list of allowed/denied characters

Valid in Version: 2020.2.4 and later

You might find that there are issues in Envision with names or descriptions being rejected due to denied characters.

When Envision is installed, there is a default list of characters that are rejected in Envision when creating charts, dashboards, or database objects. This is controlled by a configuration property in the Akana Administration Console, and can be modified by the Administrator if needed, to either remove characters from the denylist or add new ones.

For more information, and instructions, see Configuration properties: Configuring the denylist characters.

Aggregation rollup job is failing

You might find that the aggregation rollup batch job is failing due to the following:

  • The aggregation rollup batch Job is failing with the 'document constructed by $facet is 104859192 bytes, which exceeds the limit of 104857600 bytes' error. You must update the 'internalQueryFacetMaxOutputDocSizeBytes' property with '17179869184' in the mongod.cfg file by using the following command:

    setParameter: 
 internalQueryFacetMaxOutputDocSizeBytes: 17179869184

  • The aggregation rollup Job is failing with an 'unrecognized time zone identifier: "Etc/GMT+10"' error even after configuring the valid INA time zone. You must comment the 'timeZoneInfo' property in the mongod.cfg file by using the following command:

    #timeZoneInfo: /usr/share/zoneinfo