System Events Archiv

Insgesamt 4 archivierte Events
  • 1
20.12.2018
Incident Management on 18.12.2018 | agrirouter

additional Information

Since approximately 18.12.2018 11:00 UTC customers may have experienced a disruption impacting agrirouter Connectivity-Platform.

We have indicated a possible disruption on the agrirouter Connectivity Plattform impacting client's ability to onboard the endpoints. Engineers are now investigating and an update will be provided shortly.

Update 18.12.2018 16:00 UTC:

Since approximately 16:00 UTC the disruption has been resolved. The Onboarding via EU1-URL is working again. But for a successful Onboarding a workaround is necessary: the external ID for the Onboarding-Request must only consist of <=36 characters. Engineers are still working on a final solution.

Update 20.12.2018 at 13:30 UTC:

Today at 20:00 CET(19:00 UTC) a fix for the current problem will be provided. After that the workaround is no longer necessary. All Services on the quality assurance and production environment have been restored.

Component:


quality assurance:operational

production: operational


 

Status definition:


operational:                   The component is functioning as expected and in a timely manner.

under maintenance:       The component is currently being worked on.

degraded performance:  The components are working but is slow or otherwise impacted in a minor way. The component response time is longer as expected.

partial outage:                 The components are completely broken for a subset of customers but is working for the rest.

major outage:                  The components are completely unavailable.


19.12.2018
agrirouter Release Management | Deployment of new agrirouter Version for 19 December 2018

additional Information

Component:

• agrirouter Quality Assurance Environment

• agrirouter Production Environment

Period:
19 December 2018 15:00 UTC to 16:00 UTC, no downtime foreseen.

Trigger:
• Rollout of router device functionality (improved cloud integration).

Impact:

• UI update for improved cloud integration mechanism based on router device

• Visually improved print template for registration code

14.12.2018
agrirouter Release Management | Deployment of new agrirouter Version for 14 December 2018

additional Information

Component:

• agrirouter Quality Assurance Environment

• agrirouter Production Environment

Period:

14 December 2018, 12:00 until 17 December 2018, 08:00 (German time)  -> agrirouter Production Environment

17 December 2018 16:00 to 17:00 (German time)                                        -> agrirouter Quality Assurance Environment

Trigger:

• Delivery of new cloud integration concept

• New release of agrirouter messaging gateway

• Fix agrirouter protobuf schema definition issue: https://github.com/DKE-Data/agrirouter-api-protobuf-definitions/issues/31

• Measures for the system stabilization and troubleshooting

• Resolved native protobuf data exchange issue.

Impact:

• The end user and developer accounts can be further used

• All in your accounts existing endpoints and routes cannot be used

• All endpoints must be onboarded again in your accounts

• And all routes must be created again

• Availability of router device (new cloud integration concept) in development account

• For using a new cloud integration concept, please change your agrirouter communication gateway protocol form HTTP to MQTT

• The update of the agrirouter protobuf schema definition has only an impact on the telemetry cloud solutions

  1. Please adjust your onboarding and offboarding agrirouter interface
  2. Please update as soon as possible your protobuf schema definition: https://github.com/DKE-Data/agrirouter-api-protobuf-definitions
04.12.2018
agrirouter Release Management | Deployment of new agrirouter Version for 04 December 2018

additional Information

Component:

• agrirouter Quality Assurance Environment

• agrirouter Production Environment

Period:
04 December 2018 18:00 UTC to 19:00 UTC, no downtime foreseen.

Trigger:
• Measures for the system stabilization and troubleshooting.

Impact:

• The end user and developer accounts can be further used.

• All your registered, onboarded endpoints, groups as well as defined data routes can be further used.

Bugfix Package:

• RQ N/A - sending timelog data between two endpoints not possible

TwitterFacebookYouTube