5.5.X to 5.6.0¶
This document explains what configuration changes MUST be performed during a PunchPlatform update from version 5.5.2 to 5.6.0
Punchplatform will remove
punchplatform-channel.sh in the future. All commands must
punchctl command instead.
The punchplatform monitoring service was integrated and executed by the shiva master. Now it is an external shiva task configured as any other channel task running in shiva, but in some platform channel.
You can see a running example in the standalone (tenant
Please refer to Platform monitoring task setup for setting up this task in one of the platform tenant (usually "platform" tenant on a back-office platform, or the main tenant on a LTR platform).
In addition, if the platform monitoring is performed on a LTR platform, then the platform metrics reporter (in punchplatform.properties) must be configured so that the document is forwarded to a back-office platform, and there into platform-health-* Elasticsearch Indices (possibly through a kafka topic first), to then allow REST querying of this health by the central monitoring system (outside Punchplatform scope).