Page created: 24 Jul 2019 |
Page updated: 6 Nov 2019
Add custom statistics based on any attribute in any entry under cn=monitor using the Custom Logged Stats object. This configuration object provides powerful controls for how monitor attributes are written to the log. For example, you can extract a value from a monitor attribute using a regular expression. Newly created Custom Logged Stats will automatically be included in the Periodic Stats Logger output.
Besides allowing a straight pass-through of the values using the 'raw' statistic-type, you can configure attributes to be treated as a counter (where the interval includes the difference in the value since the last interval), an average, a minimum, or a maximum value held by the attribute during the specified interval. The value of an attribute can also be scaled by a fixed value or by the value of another monitor attribute.
Note: Custom third-party server extensions that were written using the Server SDK can also expose interval statistics using a Periodic Stats Logger. The extension must first implement the SDK's
MonitorProviderinterface and register with the server. The monitor attributes produced by this custom
MonitorProviderare then available to be referenced by a Custom Logged Stats object.
To illustrate how to configure a Custom Logged Statistics Logger, the following procedure reproduces the built-in "Consumer Total GB" column that shows up in the output when the
included-resource-statproperty is set to memory-utilization on the Periodic Stats Logger. The column is derived from the
total-bytes-used-by-memory-consumersattribute of the cn=JVM Memory Usage,cn=monitor entry as follows:
dn: cn=JVM Memory Usage,cn=monitor objectClass: top objectClass: ds-monitor-entry objectClass: ds-memory-usage-monitor-entry objectClass: extensibleObject cn: JVM Memory Usage ... total-bytes-used-by-memory-consumers: 3250017037