Ensuring high availability of Cumulocity microservice

[edso]

Product/components used and version/fix level are you on:

1015.0.329

Detailed explanation of the problem:

I have 3 microservices A, B and C. A is the master which when started will invoke B and B invoke C. So, the microservices have to be started in C,B, and A sequence. My microservice A sometimes get “stuck”. A is one that wakes up every 30 secs to repeat some processing in a loop. The status of the microservices that have dependencies are showing that it is up indicative of the green check mark. There were no alarms or alert. Wanted to know if there is a way to be notified if my microservice is “stuck” in a timely fashion?

Error messages / full error message screenshot / log fileL

Non

Is your question related to the free trial, or to a production (customer) instance?

Production

Have you installed all the latest fixes for the products and systems you are using?

Yes

[Stefan_Witschel]

You can & should use the “health” and “readinessProbe” defined in the manifest. This will be used to define if your microservice is health and ready to receive & process requests. You can also check with other microservices if they are available and ready.

https://cumulocity.com/guides/microservice-sdk/concept/#manifest

[edso]

It would appear that the reason for my microservice to be stuck was because I did not changed my APIversion to v2, which is a requirement when upgrading to 1015. The microservices have been running flawlessly since. So important to read the upgrade note.

[Harald_Meyer]

This should not have been the root cause, as v1 has only been deprecated but should still work.