Monitoring

Extensions: Getting Started

Logs

The plugins run in process with Control Center (CC) Java process. This implies that we can leverage Java logging, infrastructure.Logging.

The ConfigurableExtensionPoin class exposes a java.util.logging.Logger instance, which the extensions should use. The log will show up in the same location as the CC logs.

📘

Logging Libraries

It is not advisable to include external libraries like Log4j.

These are very widely used and result in lots of versions in the Java Virtual Machine (JVM), which can result in class loader issues.

Monitoring

Extension lifetime is tied to the lifetime of the HYPR CC. Extensions are started and stopped automatically with the CC start/stop. The CC UI displays the health status of the extensions. 

1420

If an extension is uploaded to a cluster, it might take a few seconds for the extension to propagate across the cluster. If there are any failures on cluster node(s), the CC UI will indicate them.

Extension status info can also be obtained from the following API call:
https://<HYPR CC URL>/extension/list/all

Monitoring in a Cluster

Each node reports its own status of the extension. An extension is considered UP|STARTED if all nodes report success.

1390