Log OPCH start and stop

Product Suggestions
,
1

Greetings.

I’ve had several cases where I had issues with an OPCH on a customer’s network which lead me to inspect the Docker container’s logs. I know OPCH logs are probably not the most used “feature” in Tulip, but in my case I noticed several times that logs are not very readable when it comes to determining when the OPCH was started or stopped.

I know it’s possible to know when OPCH is starting by spotting lines such as:

yarn run v1.22.19
$ node dist
using nodejs crypto (native)

But I don’t find it very clear. Logging OPCH startups would be the occasion to give information about which OPCH version is running (e.g. lts13.3, lts13.4, lts14…). Most importantly, not logging OPCH shutdowns means that we cannot differentiate between a graceful shutdown and an unexpected one.

So I suggest that OPCH startups and shutdowns are logged to facilitate OPCH troubleshooting during client infrastructure maintenance (and the Tulip support’s job :slight_smile: ).

2

Hello
In our context, we have the same need to monitor our OPCH (+15 OPCH).
Today, we monitor and be alert by the following log pattern (using Datadog solution):

  • Start: “Connectors Service starting”
  • Backend system issue: “connector failure”

For stop or if OPCH is in a bad state, we have implemented an Automation that monitor an hearttbeat through the OPCH, if Tulip don’t receive this heartbeat, an email is send.