MindAccess Developer Plan Subscribers and MindAccess Operator Plan Subscribers

What's new?

This upgrade allows one additional instance of any Backing Service to concurrently run at the same time. Each available Backing Service size can be started within this Backing Service Pay per Use upgrade.

This service supports a 'pay per hour' billing model of utilized Backing Services.

At the end of month, billing will occur based on started hours per backing service instance. You may refer prices per hour for each backing service size:

• Backing Service XS - 0,20 € / started hour

• Backing Service S10 - 0,26 € / started hour

• Backing Service M50 - 0,33 € / started hour

• Backing Service S10_HA - 0,45 € / started hour

• Backing Service M - 0,66 € / started hour

• Backing Service M150_HA - 0,74 € / started hour

Available and Updated buildpacks:

Additional Info:

• LogMe Kibana dashboard URL has changed. Follow https://developer.mindsphere.io/paas/a9s-logme/using.html#see-your-applications-logs to find the new URL.

• Reminder: Backing Service MongoDB will be removed from Cloud Foundry after 31.10.2020

Known issues

• If you have problems logging off in Internet Explorer 11, please refer to Overcoming Logout Problems in IE11. 

What's new?

• Within this release we release a new set of REST APIs to search the data stored within the Integrated Data lake using object name and metadata.

• The Fleet Manager Plug-in now available for Integrated Data Lake.* List objects\files stored in Integrated Data Lake which are associated with your MindSphere asset

Known issues

• For security reasons a strict timeout is enforced. Currently, this leads to the situation that the size of a file which can be uploaded/ downloaded depends on the network bandwidth at client side.

• When uploading files to the File Service, a file name cannot contain blank spaces. Blank spaces in the file name will prevent the file form being stored.

• After deleting an asset, associated files might still be accessible for up to 30 minutes as this data is deleted asynchronously.

• After deleting a file, it will take some time (up to 60 seconds) to create the file with the same name again.

• After creating or deleting the file, it will take some time (up to 3 seconds) to get the file in "search file" API. 

Known issues

• The maximum payload size of a message sent to Time Series Service as part of a PUT request cannot exceed 1 MB.

• The service will never return more than 2000 records in a response.

• After deleting an asset, respective time series data might still be accessible for up to 30 minutes as this data is deleted asynchronously.

• When getting the job status of a bulk import job, the response might not always contain detailed information on errors that occurred.

• When creating or updating an aspect it might take up to 30 minutes until aggregated data can be read for this aspect. Writing data or reading raw data is possible immediately.

• When ingesting time series data for multiple asset and aspects in single request, the combination of records should be unique.

• Get Latest Value with query parameter "latestValue = true" will work with a delay up to 2 hours from the time of ingestion. Refer to developer documentation 'sample' section for more information.

• While using Get Latest Value with query parameter  "latestValue = true", historic/late arriving data may take more than 1 day to reflect in the response.