Operations Basics / Version 2110
Table Of ContentsThe attributes and metrics mentioned in Table 5.2, “ContentServer JMX Monitoring” are suggested for monitoring.
For a complete overview of available attributes and metrics have a look at Section 5.2, “Managed Properties” in Content Server Manual.
Server.LicenseValidUntilHard
| |
| Type | Gauge |
| Value Type | long |
| Unit | milliseconds |
| Description |
Time in epoch milliseconds when a license will expire and thus
servers will fail to start. Note, that it is recommended to
monitor |
Server.LicenseValidUntilSoft
| |
| Type | Gauge |
| Value Type | long |
| Unit | milliseconds |
| Description |
Time in epoch milliseconds when a license warning will be filed to the logs. You should monitor this limit and raise and raise an alert if your license will expire soon. |
Server.RepositorySequenceNumber
| |
| Type | Counter |
| Value Type | long |
| Description |
The sequence number of the latest successful repository transaction, useful for comparison between Master Live Server and Replication Live Server.
A typical health check monitors
|
Server.RunLevel
| |
| Type | Attribute |
| Value Type | String |
| Description |
The current run level of a server. For details on available run levels see Section 2.4, “Server Run Levels” in Content Server Manual. Possible values are:
A standard server should reach run level online after some given grace period. |
Server.RunLevelNumeric
| |
| Type | Attribute |
| Value Type | int |
| Description |
The current run level of a server. For details on available run levels see Section 2.4, “Server Run Levels” in Content Server Manual. Possible values are:
A standard server should reach run level online after some given grace period. |
Table 5.2. ContentServer JMX Monitoring
