Analytics Troubleshooting
Cannot Access Application Analytics Module and Apps
You cannot access the Analytics module and apps in your tenant.
Condition
You are logged in to your tenant with the necessary privileges to access the Analytics module and apps. However, when you select any navigation links in the Analytics module, the following error message appears: Your tenant provisioning is incomplete. Request your tenant Administrator to create the analytic functional user in the Tenant.
Cause
Your tenant administrator has not set up the password for the analytic system user to enable the Application Analytics to communicate with the configured runtime for your tenant.
Remedy
Perform the steps in Set Up the Analytics Functional User.Cannot Access Application Analytics Module and/or Features
You are not able to access some or all of Application Analytics modules, sub-modules, apps and features in your tenant.
Condition
You are logged in to your tenant, you have one or more of the following problems:
- You cannot access any sub-modules.
- You can access but cannot make additions or modifications in the sub-module/app. For example, you can access deployments, but cannot add new deployments or modify existing deployments.
- You cannot access some of the sub-modules/apps. For example, you can view Analytics Templates and Orchestrations, but cannot access Deployments or Asset Filters.
Cause
Your tenant administrator has not enabled access to the required permission sets to access the appropriate sub-modules/apps. Your tenant configuration may be older and still uses the wide default permission set of Manage Analytics Catalog. It must be configured with the granular permission sets.
Remedy
Work with your tenant administrator to give you the needed permission sets to access the required sub-modules/Apps.
Cannot Access Custom Properties For Alerts in Analytic Output
You cannot access the custom properties key-values pairs that were passed to Predix Essentials Alerts through an analytic output event.
Condition
The Predix Essentials alert service does not publish the custom properties passed through events in the analytic output. The analytic had passed these custom properties as an array of key-value pairs in the analytic output.
Cause
The related keys in custom properties of an analytic output are not pre-registered within the specific tenant.
Remedy
Because of security considerations, prior to passing values as alert attributes via the custom properties of an analytic output, you are required to first register all related keys in custom properties within the specific tenant. This step allows the tenant to recognize these keys as valid, and properly pass the key-values to an alert as an attribute, allowing access and visualization in Alerts via the grid view. To register key(s) as custom attribute(s) recognizable by Predix Essentials, follow these steps:
- Determine all keys to be registered.
- Register all keys per instructions in the API documentation. Select the link below to access the API documentation:
https://apm-apidocs-preprod.preprod-app-api.aws-usw02-pr.predix.io/alarms/#_create_custom_attribute
- After you have registered all keys, pass the key-value pairs for alert custom properties in the required JSON format of the analytic output.
Cannot Deploy an Analytic to Predix Runtime
You cannot deploy an analytic even after completing all the required steps in deployment.
Condition
You have uploaded an analytic template and configured all required inputs, outputs, and constants. You successfully add a deployment with the configured Analytic Template. However, after completing all the steps required in the deployment successfully, the error appears when you select Deploy. The deployment status remains Not Deployed.
Cause
The analytic template has not yet been uploaded to the analytic catalog. The current status of the analytic template still displays In Progress. Deployments cannot be staged to the Predix runtime unless the analytics template is available in the catalog.
Remedy
Make sure that the current status of the analytic template used in your deployment no longer displays as In Progress. Open the deployment in the edit mode. Navigate to the Review page, and then select Deploy to stage the deployment to Predix runtime.
Verification
The deployment status should changes from Not Deployed to In Progress. This indicates that the deployment has been uploaded to the runtime to be staged for execution.
Cannot Access Attributes in the Asset Filter
In the Analytics module, you cannot access a list of attributes during asset filter creation.
Condition
You are logged in to your tenant with the necessary privileges to access the Analytics module and apps. However, when you are adding a new asset filter, you are not able to see all required attributes to create the filter.
Cause
You have not yet configured the attribute, or you have configured attributes that are not part of your asset model. Using non-existing model attributes in your analytics configuration will not add them to the asset model, nor will they show up for use in the asset filters as they do not exist in the system.
Remedy
Add the needed system attributes to the asset model in your tenant. Use system attributes that you have ingested in your analytics configuration. After, you have configured them, you can use them in the asset filters.
Failed Analytics Deployment
You cannot run the deployment successfully on Predix runtime.
Condition
You selected the deploy button to deploy an analytic to run on the Predix runtime. You had completed the asset selection, I/O mapping, scheduling, and review steps prior to deploying the analytic to the runtime. However, after running the deployment you see the following error message when you hover over the Run Once Failed deployment status:
“Invalid input port name <analyticInputName>. Cannot find it in ports to data source list.”
Cause
It is possible that the analytic generates alerts but the output event is not defined in your deployed analytic template. This causes the alert ingestion to fail as no template definition can be found for it.