First Quarter of 2019
Analytics
This topic provides a list of product changes released for this module on the dates listed below.
Release Date: March 29, 2019
| Description | Tracking ID |
|---|---|
| To enhance the usability in analytic template and deployments, you can now download a .zip file of logs containing all analytic deployments for the current version of the Analytic Template. | F42079 |
| To enhance the usability in analytic deployments, you can now configure your tenant to connect to an instance of PostgreSQL that has been previously configured on Spark runtime as one of the input data source. |
|
| To enhance the usability in analytic orchestrations, you can now schedule analytic orchestrations to run in a recurring mode for Spark runtime. | F42076 |
| To enhance the asset applicability during deployment, the asset applicability can now be derived from existing deployments and asset filters associated with each deployment. Newly commissioned assets that fit the filter criterion are automatically available for selection during deployment. | F42074 |
| To enhance the I/O Mapping step during deployment, you can now configure the Entity Type for inputs, outputs, and constants in the analytics template. During the I/O mapping step in deployment, the Entity Type tells Application Analytics to retrieve the tags and attributes of all assets and their children starting at the defined level. Note: This is not available for all runtimes. | F42072 |
| To enhance the usability in the analytic template creation, you can now associate a Machine Learning (ML)/Artificial Intelligence (AI) model to an analytic or blue print. This is only available for the PowerDataFabric runtime. | F42071 |
| To enhance the Scheduling step during deployment, you can now trigger an analytic to run when a specific alert event happens. Note: This is not available for all runtimes. | F18922 |
| Description | Tracking ID |
|---|---|
| Previously, when a deployment used more than 1000 assets but did not have all outputs explicitly mapped, then the error ConcurrentModificationException occurred and the deployment failed. This issue has been resolved. | DE97332 |
| Previously, on dedicated tenants, administrators could not access the audit logs for Analytics using the Audit Log Management. This issue has been resolved. | DE94501 |
| Previously, sometimes, even though there were no current deployments associated with the version of the analytic templates you were trying to delete, an error occurred asking you to first delete any associated deployments before you can delete the version of the analytic artifact in the template. This issue has been resolved. You can now delete analytic templates which have no current deployments. | DE77551 |
| Previously, when you modified an Analytic Template configuration after it had already been used in a deployment, the deployment status in the Deployments page was expected to display Updates Not Deployed. Sometimes, the status did not automatically refresh. This issue has been resolved. | DE63501 |
| Description | Tracking ID |
|---|---|
| If a deployment uses more than 250 assets that generate alerts at frequent intervals of less than one hour, you may not be able to access these alerts. There are some known limitations when using a combination of high-volume and high-frequency alerts generated by analytics. If you have a need to deploy analytics that are expected to produce alerts at high frequencies and for large volume of assets (over 250), please contact the Analytics Support Team prior to deploying such analytics. This limitation is limited to the Predix runtime environment. A future enhancement for rendering high-frequency, high-volume analytics alerts is scheduled for a future release. At that time, all existing deployments must be re-deployed to benefit from the enhancement. | DE105943 |
Limitations
- Application Analytics does not support cross-tenancy; therefore, you will not be able to access assets from a different tenant.