First Quarter of 2018
Analytics Release Notes for February 8, 2018
Provides a list of new and updated features for this release, as well as any resolved issues, limitations, and known issues.
Release Information
| Module Name | Analytics |
| Release Date | February 8, 2018 |
| Documentation Build Date | February 8, 2018 |
What's New or Changed in This Release
- Bring Your Own Runtime - Ability to register, enable for a tenant, and utilize an external custom runtime with APM Application Analytics. This feature is release with limited availability.
- Ordering of deployments in Orchestrations
- Ability to assign a priority value to individual deployments in the 3. Schedule page.
- This is enabled only for deployments associated with analytics orchestrations for a registered, external custom runtime.
Limitations and Known Issues
| Tracking ID | Description |
|---|---|
| DE62740 |
For analytics that are deployed and run in the Predix Analytic runtime, redeploying with a newer version of the analytic uploaded to the catalog results in a failed deployment with the newer version. The deployment status resets to Not Deployed and the system responds with an error invalid service task name <task id>. Workaround: For all analytics that must be deployed to the Predix Analytic runtime, make sure that you create a new deployment for every time a new version of analytics is uploaded to the catalog. All existing deployments will continue to use the older version of the analytics used to first deploy it. |
| DE62748 | The Analytics Deployment will be saved; however, the Analytic will fail to deploy or run if the Sampling Interval for interpolated data is set to 0 minutes or 0 seconds. The minimum expected value is 1 second. |
| DE63501 |
After tenant creation, default asset filters and filter fields data may not be available for the new tenant that was set up in QA2 environment. If this happens then, do the following: Note: Only a system administrator can perform these steps.
|
Resolved Issues
| Tracking ID | Description |
|---|---|
| DE56659 | Intermittently, during analytics deployment, even after selecting the asset in the 1. Asset Selection page, the Save, Reset, and Next buttons may remain disabled. Workaround: Navigate to the main Deployment tab, then select the deployment. Select Edit to re-attempt the 1. Asset Selection and 2. I/O Mapping pages. |
| DE56646 | After selecting Deployments in the main navigation, the status of a deployment in the deployments list may not match the status listed in the Deployments details page. For example, the deployment list may show the status In Progress for the deployment Deployment1, but the Details section for the same deployment lists the status Completed. Workaround: Refer to the deployment status on the details page instead of status in the list. |
| DE56620 | In Deployments, 2. I/O Mapping page, on attempting to clear the value in the Data Points field for an analytic step or its iteration, the system may default to an older, previously saved value. Workaround: At this time, configure the affected Data Points field to a higher value than the number of points configured for the Date Range in the 3. Schedule page; the system will then update the Data Points value for the step or iteration. |
| DE56563 | This defect only applies to analytics that use the resolveAndExecute API for event-based triggering. If analytics deployments were scheduled for event-based triggering, and the 1. Asset Selection page was configured using a default asset filter such as All Assets, All Enterprises, All Segments, and All Sites, the deployments will not run correctly. Workaround: At this time for analytics that use the resolveAndExecute API for event-based triggering, create custom asset filters and use them to configure assets in the 1. Asset Selection page in Deployments. Do not use default asset filters to configure assets selection during deployment. |
| DE57027 | In Deployments, 1. Asset Selection page, if you had previously configured assets with a custom asset filter, and later updated to select a different asset filter containing the same filter criteria (for example, both asset filters produced the same results of assets), the system may revert the filter to the older, previously selected version. Navigate to the main Deployments page, select the deployment, and then select Edit to re-attempt asset selection configuration. Alternatively, if the filter criteria are the same in both filters, use the previously configured asset filter. |
| DE56906 | In the Deployments details page and 2. I/O Mapping page, analytics that have long names appear with the name and version columns overlapping to obscure some text. Workaround: Navigate to the Deployments details page. You can note the name of the analytic orchestration heading in the deployment header. You can then navigate to the Orchestrations list, and then search for that specific orchestration and access it in the details page. You can then access the analytics template names and version used in the data flow. |
Analytics Release Notes for March 30, 2018
Provides a list of new and updated features for this release, as well as any resolved issues, limitations, and known issues.
Release Information
| Module Name | Edge Analytics |
| Release Date | March 30, 2018 |
| Documentation Build Date | March 22, 2018 |
What's New or Changed in This Release
- Support for Analytics/Orchestrations on Spark Runtime (Limited Availability)
- Uses the Predix Insights (Beta) capabilities.
- Orchestration data flows are supported for both Java and Python based analytics in this runtime.
- Provides the ability to modify and delete orchestration deployments.
- Provides the ability to map an existing output tag as the input for the next step in the orchestration data flow. This functionality is limited to configuring already ingested tags in the asset model. It is not possible to use output tags generated by the analytic during runtime.
- Ability to Ingest, Configure and Deploy analytics to the Edge Analytics Runtime (Limited Availability - available on request only)
- Users can download and install the Edge Analytics Editor to create analytics. This is accessible from the Edge Manager repository for the (cloud) application tenant.
Limitations
- Analytics/Orchestrations on Spark Runtime has the following limitations:
- Orchestration deployments for Spark runtime can only be scheduled using the RunOnce and Streaming options.
- Orchestration deployments for Spark runtime scheduled using Streaming option limits it to one step only.
- Spark runtime does not cache the analytic outputs during analytic execution.
- No fallback supported if an orchestration deployment fails in the Spark runtime after running the deployment.
- Edge Analytics runtime has the following limitations
- Currently Edge Analytics only supports OPC UA for automated data collection and deployment.
- While most functionality is available, there is no support to modify existing Edge Analytics deployment instances.
- You must configure and set up the Edge Manager separately. For example, installation of Edge Analytics runtime and other software must be performed separately.
- Deployments are sequential: only a single Deploy or Delete operations can be done at any time. You must first complete the action before another user initiates the next Deploy or Delete operation.
- Deployment Deletion
- Failed deployments, that go from, In Progress status to Not Deployed status, must be:
- Deleted from Deployments list in Application Analytics
- All CAF_Configuration files and Analytics on each Edge Device must be manually deleted (cleaned up) using Edge Manager to ensure that Edge Device state remains consistent with Deployments listed in Application Analytics.
- Application Analytics automatically deletes deployments in the Edge Devices, when you delete deployments in Application Analytics that have successful Edge Analytics Deployments statuses of Deployed, or Scheduled.
- While a Delete operation is in progress, indicated by spinning wheel - wait/busy icon, a user must not navigate away, but just wait until busy icon disappear. The deployment is removed from Deployments, which indicates that Delete operation has been completed. After which, the user should confirm in Edge Manager that all analytics, and related configuration to this Deployment has been removed/updated on the relevant Edge Devices.
- After a deployment has been deleted, you cannot reuse the same name for another Edge Analytics Deployment.
- Failed deployments, that go from, In Progress status to Not Deployed status, must be:
Known Issues
| Tracking ID | Description |
|---|---|
| DE64497 |
For analytics deployments to Edge Analytics runtime, during the 2. I/O Mapping step in Deployment, the Deploy button remains disabled if optional input fields are not fully mapped even though it is not required. Make sure that during 2. I/O Mapping step in Deployment, all input tags are fully mapped before proceeding irrespective of whether or not they are required inputs. |
| DE67658 |
In Predix runtime, tags conforming to the expected tag nomenclature do not get listed as expected in I/O Mapping when selecting the Map for All Assets and Add Suggested Tags options. Workaround: Manually perform the I/O mapping to the correct input and output tags. |
| DE67897 |
The Delete button remains disabled for deployments with the status In-Progress for analytics deployed to the Edge Analytics runtime. Typically, even though deletion of deployments is not currently supported for Edge Analytics runtime, the Delete button is expected to remain enabled. When you select the button, an error message In-progress deployments cannot be deleted should appear. |
| DE64793 |
Even though a deployment only requires either the output definition or output event to be configured correctly in an analytic template, Application Analytics does not allow the user to create deployments using a template that does not have output definitions. Even if the Deployment tab is enabled, the user cannot create deployments and the error message: Unable to create deployment as there are no 'outputs' for the <analytic_template> analytic appears. |
| DE62724 |
For analytics deployed to SmartSignal runtime, in the rm deployment- IOMappingMetadata1.json, Application Analytics does not display a warning or error message when the configured constant value does not match the constant data type. This can potentially lead to deployment failures. Workaround: Always ensure that the constant values entered must match the data type defined in the analytic template configuration. |
| DE69377 |
For analytics deployed to the Spark runtime and scheduled to Runonce; even though the interpolated option is selected, the data always returns as raw data from timeseries instead of the expected interpolated results. |
Resolved Issues
| Tracking ID | Description |
|---|---|
| DE63501 |
After tenant creation, default asset filters and filter fields data may not be available for the new tenant that was set up in QA2 environment. If this happens then, do the following: Note: Only a system administrator can perform these steps.
|