Skip to content

Support

Jump to bottom
Geir Arne Rødde edited this page May 18, 2022 · 164 revisions

Do you need help?

The Omnia Industrial IoT team is available Monday to Friday from 08:00 - 16:00 CEST for support, assistance and advisory. Here is how you can reach out to the team:

Operational status

2022.05.218
A minor upgrade of Timeseries API backend (timeseries DB) will be performed after lunch. Clients should not notice, except for a small performance decrease while each of the nodes are restarted.

2022.04.29 0100 - 1100 closed
Issues with dataflow from on-premise historian to Omnia for several assets.

2022.03.31 closed
A minor version 1.7.4 of Timeseries API (prod) will be deployed Thursday March 31st after lunch. Version 1.7 and 1.6 are based on same backend, the clients should notice only minor disturbance and no change in behavior due to the change.

2022.02.22 closed
A minor version 1.7.3 of Timeseries API (prod) will be deployed Tuesday February 22nd after lunch. Version 1.7 and 1.6 are based on same backend, the clients should notice only minor disturbance and no change in behavior due to the change.

2022.02.01 - 2022.02.02 closed
A minor version 1.7.2 of Timeseries API (prod) will be deployed Wednesday 2nd February before lunch. Version 1.7 and 1.6 are based on same backend, but the clients should notice only minor disturbance and no change in behavior due to the change.
Unfortunately we had some issues restarting API service after deploy, so API was out of service 0930-1050, we apologize for any inconveniences.

2021.11.30 closed
A minor version 1.7.1 of Timeseries API (prod) will be deployed Tuesday Dec 12th before lunch. Version 1.7 and 1.6 are based on same backend, but the clients should notice only minor disturbance and no change in behavior due to the change.

2021.11.23 closed
A minor upgrade of Timeseries API backend (timeseries DB) will be performed before lunch. Clients should not notice, except for a small performance decrease while each of the nodes are restarted.

2021.10.26 closed
A minor upgrade of Timeseries API Beta backend (timeseries DB) will be performed before lunch. Clients should not notice, except for a small performance decrease while each of the nodes are restarted.

2021.10.21 1600-1730 closed
Issues in Timeseries API, not responding.

2021.09.14 closed
A minor upgrade of Timeseries API backend (timeseries DB) will be performed after lunch. Clients should not notice, except for a small performance decrease while each of the nodes are restarted.

2021.08.31 closed
For the Timeseries API (service) Beta, a hard retention on 1 years will be applied to the Timeseries database.
The consequence of this is that no data older than 1 years will be kept and made available through Omnia Timeseries API.
This action does of course not affect timeseries data stored other places, as Timeseries PROD, Data Lake and on premise historians.

2021.04.12 closed
Timeseries API v1.5 shut down. As Timeseries API v1.6 where introduced one year ago, v1.5 was announced deprecated, according to our API versioning strategy. This shut down will now be effected this week, so all clients need to switch to v1.6.

2021.04.12 closed
For the Timeseries API (service) Beta, a hard retention on 2 years will be applied to the Timeseries database.
The consequence of this is that no data older than 2 years will be kept and made available through Omnia Timeseries API.
This action does of course not affect timeseries data stored other places, as Timeseries PROD, Data Lake and on premise historians.

2021.03.29 1000-1200 closed
Timeseries API, a hotfix will be applied today, you may experience some seconds (1-60) unavailability. Schedule for patch application, TEST ca. 10.00, PROD ca 11.00.
Ingestion pipeline IMS/historian data PROD, a new version will be deployed during the day. API clients should not be affected, but please keep us informed if you see abnormal behavior.

2021.03.22 1200-1400 closed
Issues with dataflow from Snorre A historian, probably caused by IP21 issues. Investigation ongoing.

2021.03.11 - 2021.03.18 closed
Timeseries API where switched over to API and timeseries DB backend in new Azure subscription 2021.03.15 0940.
A change in the Timeseries API is planned for 2021.03.15.
The change in the API is minor, meaning that consumers should not be affected.
The change backend is more comprehensive, as we are moving the timeseries database and metadata components from one Azure subscription to another.
Again, consumers should not be affected, but please let us know if you expect missing data or other unexpected behavior.

2021.03.15 0730-0830 closed
Dataflow from some assets Halten/Nord stopped. ASG, HDR, KRID, NOR affected. Root cause found, data being backfilled.

2021.02.16 1000 - 2021.02.17 1700 closed
Timeseries API ingest and read disturbed due to networking issues between API frontend and backend.
Networking issue fixed 16.02 1400, but a consequence is lag in ingest from data sources (IMS/historians), assumed to be on par 17.02 1200

2021.02.10 - 2021.02.18 closed
A change in the Timeseries API Beta is planned for 2021.02.15.
The change in the API is minor, meaning that consumers should not be affected.
The change backend is more comprehensive, as we are moving the timeseries database and metadata components from one subscription to another.
Again, consumers should not be affected, but please let us know if you expect missing data or other unexpected behavior.

2021.01.04 0800 - 2021.02.15 closed
From some consumers of the Omnia Timeseries API we observe that there are some references to:
https://omnia.azure-api.net/plant/timeseries/v1.6
This URL is not “supported”, and should not be used. Please ensure that your code use this URL:
https://api.gateway.equinor.com/plant/timeseries/v1.6

Clone this wiki locally