Enabling JMX counters for performance monitoring

Administer Bitbucket Data Center and Server

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This article describes how to expose JMX MBeans within Bitbucket Data Center and Server for monitoring with a JMX client.

Related reading: Understanding JMX (Oracle)

On this page:

What is JMX?

JMX (Java Management eXtensions) is a technology for monitoring and managing Java applications. JMX uses objects called MBeans (Managed Beans) to expose data and resources from your application.

Why would I want to enable JMX monitoring within Bitbucket?

For large Bitbucket instances, enabling JMX allows you to more easily monitor the consumption of application resources. This enables you to make better decisions about how to maintain and optimize machine resources.

How to enable JMX monitoring?

Starting from Bitbucket 8.0, Git operations are run in the Bitbucket Mesh sidecar by default. That’s why, to enable full JMX monitoring for Bitbucket 8.0 and later, you should enable JMX for both the Bitbucket main process and the Mesh sidecar process.

To enable JMX for the Bitbucket main process:

  1. Go to Administration > General configuration > Monitoring.

  2. Use the JMX monitoring toggle to enable or disable the feature.

Learn how to enable JMX monitoring on the Mesh sidecar

What can I monitor with JMX?

JMX counters allow you to monitor various statistics across Bitbucket. Select the one that interests you and find out more about it in the document.

Mail performance

Mail statistics (com.atlassian.bitbucket:name=MailStatistics)

NameDescription
AverageMessageSizeAverage size (in bytes) of messages sent
LargestMessageSentLargest message that has been sent (in bytes)
LastMessageFailureDate of the last failure to send a message
LastMessageSuccessDate of the last successful message send operation
LastQueueFullEventLast time the message queue was full
QueueFullEventCountNumber of times the message queue was full
QueueUsageQueue usage as a fraction, 0.0d indicates empty and 1.0d indicates full
QueuedMessagesCountCurrent count of queued (unsent) messages
QueuedMessagesSizeCurrent size (in bytes) of the queued (unsent) messages
TotalMailDataSentTotal size (in bytes) of messages sent
TotalMessagesFailedTotal number of messages that failed to send
TotalMessagesSentTotal number of messages sent

Diagnostics

Alerts total (com.atlassian.diagnostics:type=Alerts,name=Total)

NameDescription
LatestAlertTimestampTimestamp of the most recent alert
TotalCountTotal number of alerts since the JVM was started
ErrorCountNumber of alerts of severity ERROR since the JVM was started
InfoCountNumber of alerts of severity INFO since the JVM was started
WarningCountNumber of alerts of severity WARNING since the JVM was started

Plugin (com.atlassian.diagnostics:type=Alerts,Category=Plugin,name=${PLUGIN_NAME})

NameDescription
LatestAlertTimestampTimestamp of the most recent alert
TotalCountTotal number of alerts since the JVM was started
ErrorCountNumber of alerts of severity ERROR since the JVM was started
InfoCountNumber of alerts of severity INFO since the JVM was started
WarningCountNumber of alerts of severity WARNING since the JVM was started
PluginNamePlugin name, if available

Issue (com.atlassian.diagnostics:type=Alerts,Category=Issue,name=${ISSUE_ID})

NameDescription
LatestAlertTimestampTimestamp of the most recent alert
ComponentComponent the issue is defined for
CountNumber of alerts for the issue since the JVM was started
SeverityIssue's severity
DescriptionIssue's description

Hosting statistics

ProtocolObject name
SSHcom.atlassian.bitbucket:name=SshHostingStatistics
HTTPcom.atlassian.bitbucket:name=HttpHostingStatistics

Hosting statistic attributes

All the hosting statistics attributes are monotonically increasing since the JVM was restarted

NameDescription
CloneCacheBypassClone requests that have bypassed the scm-cache
CloneCacheHitClone requests served from the scm-cache
CloneCacheMissClone requests that could not be served from the scm-cache
CloneReadBytes read from clients during clone operations
CloneRequestCountNumber of clone requests served
CloneWrittenbytes written to clients during <i>clone</i> operations
FetchReadBytes read from clients during <i>fetch</i> operations
FetchRequestCountNumber of fetch requests served
FetchWrittenBytes written to clients during fetch operations
RequestsTotal number of requests served
TotalBytesReadTotal bytes read from clients
TotalBytesWrittenTotal bytes written to clients

Webhooks statistics (com.atlassian.webhooks:name=Webhooks)

NameDescription
PublishCountA count of the total number of events that could trigger webhooks
(A publish may create many dispatches)
DispatchSuccessCountTotal number of webhooks to fire successfully with a successful HTTP response
DispatchRejectedCountA count of the number of webhook dispatches that were rejected for execution
DispatchLastRejectedTimestampThe last time a webhook was rejected, either from circuit breaking, or due to too many webhooks being in flight
DispatchInFlightCountTotal number of dispatches that have been triggered and are awaiting resolution
DispatchFailureCountTotal number of webhooks that fired successfully, but the HTTP response indicates a failure
(non 2xx code)
DispatchErrorCountTotal number of webhooks to have had an error while they were being dispatched
DispatchCountTotal number of webhooks to have been dispatched

Thread pools

Thread poolDescriptionObject name
BuildActionsThreadPoolThreads that handles Integrated CI/CD build actionscom.atlassian.bitbucket.thread-pools:name=BuildActionsThreadPool
EventThreadPoolThreads that dispatch events to @EventListenermethodscom.atlassian.bitbucket.thread-pools:name=EventThreadPool
IoPumpThreadPoolThreads that handle blocking process I/Ocom.atlassian.bitbucket.thread-pools:name=IoPumpThreadPool
NioPumpThreadPoolThreads that handle nonblocking process I/Ocom.atlassian.bitbucket.thread-pools:name=NioPumpThreadPool
ScheduledThreadPoolThread pool that takes care of several miscellaneous scheduled taskscom.atlassian.bitbucket.thread-pools:name=ScheduledThreadPool
QueuedThe number of requests currently waiting for an available ticketN/A

Thread pool attributes

Name

Description

ActiveCountReturns the approximate number of threads that are actively executing tasks
MaximumPoolSizeReturns the maximum allowed number of threads
PoolSizeReturns the current number of threads in the pool
QueueLengthThe number of tasks awaiting execution by the thread pool
LargestPoolSizeThe largest number of threads that have ever been simultaneously in the pool
CompletedTaskCountThe approximate total number of tasks that have completed execution. Because the states of tasks and threads may change dynamically during computation, the returned value is only an approximation, but one that does not ever decrease across successive calls

Repositories (com.atlassian.bitbucket:name=Repositories)

NameDescription
CountNumber of repositories currently configured across all projects

Scm Statistics (com.atlassian.bitbucket:name=ScmStatistics)

NameDescription
PullsNumber of scm pulls serviced by this instance since it was started
PushesNumber of scm pushes received by this instance is it was started

Ticket statistics

Starting from Bitbucket 8.0, the Ticket metrics are absent from the com.atlassian.bitbucket property and must be fetched from the Bitbucket Mesh sidecar.

Learn how to enable JMX monitoring for the Mesh sidecar in BSERV-13623 - Getting issue details... STATUS

Bitbucket uses tickets as a mechanism for creating back pressure to prevent the system from being overloaded with requests. There are two types of tickets: hosting tickets and command tickets.

  • Hosting tickets (com.atlassian.bitbucket:name=HostingTickets) limits the number of SCM hosting operations, meaning pushes and pulls over HTTP or SSH, which may be running concurrently. 
  • Command tickets (com.atlassian.bitbucket:name=CommandTickets) limits the number of SCM commands, such as: git diff, git blame, or git rev-list, which may be running concurrently.

Bitbucket supports the following metrics for each ticket type.

NameDescription
AvailableThe number of tickets available for acquisition (lower number means higher load)
NameThe name of the ticket bucket either 'scm-command' or 'scm-hosting'
TotalThe maximum number of tickets that can be acquired concurrently before back-pressure is applied
UsedThe number of tickets that have been acquired (higher number means higher load)
LastRejection

The timestamp of the last rejected ticket, or null if no tickets have been rejected.

If this metric is missing, follow the public issue BSERV-19088 to stay updated on the fix.

OldestQueuedRequest

The timestamp at which the oldest queued request started waiting, or null if there are no queued requests.

If this metric is missing, follow the public issue BSERV-19088 to stay updated on the fix.

Event statistics (com.atlassian.bitbucket:name=EventStatistics)

NameDescription
DispatchedCountTotal number of listener callbacks that have been performed. An event that is delivered to 10 listeners counts as 10 dispatches
LastRejectionDate of the last event being rejected, or null if no event has been rejected
PublishedCountTotal number of events delivered. An event that is delivered to 10 listeners counts as 1 event
QueueCapacityMaximum number of event callbacks that can be queued before events are rejected
QueueLengthNumber of event callbacks that have been queued but haven't been dispatched yet
RejectedCountTotal number of events that were not dispatched because the event queue was full
RemainingQueueCapacityRemaining number of event callbacks that can be queued before events are rejected

Cluster lock statistics (com.atlassian.bitbucket:name=ClusterLocks)

NameDescription

LockedCount

Number of cluster locks that are currently held by this node

QueuedThreadCount

Number of threads on this node that are currently blocked waiting for a lock

TotalAcquiredCount

Total number of times a cluster lock was acquired on this node since startup

TotalAcquireErrorCount

Number of times an exception was thrown while trying to acquire a cluster lock on this node since startup

TotalAcquireTimeMillis

Total time in milliseconds that any thread on this node has spent acquiring a lock (including time blocked waiting for a lock to become available)

TotalReleasedCount

Total number of times a cluster lock was released on this node since startup

TotalReleaseErrorCount

Total number of times an exception was thrown while releasing a cluster lock on this node since startup

SSH session statistics (com.atlassian.bitbucket:name=SshSessions)

NameDescription
ActiveSessionCountNumber of currently active SSH session
MaxActiveSessionCountHighest number of concurrently active SSH sessions since the last startup
SessionClosedCountTotal number of SSH sessions that have been closed since the last startup
SessionCreatedCountTotal number of SSH sessions that have been created since the last startup
SessionExceptionCountTotal number of SSH sessions that have been terminated because an exception was thrown from the SSH command run
SessionDisconnectedLimitCountTotal number of SSH sessions that have been disconnected due to maximum concurrent requests
SessionDisconnectedConnectionLostCountTotal number of SSH sessions that have been disconnected due to connection loss

Rate limiting statistics (com.atlassian.bitbucket:name=RateLimitStatistics)

NameDescription
RejectedRequestCountThe number of rate limited requests
UserMapSizeThe number of token buckets currently in memory

Licensed users statistics

NameDescription
LicenseCapacityThe maximum number of users for the existing license
LicensedUserCountThe number of licensed users for the existing license

Third-party library attributes

Bitbucket exposes the JMX attributes from number of third party libraries. Listed below is a sample of the attributes that are particularly interesting from an operations perspective. 

HikariCP (com.zaxxer.hikari:type=Pool (bitbucket))

Name

Description

ActiveConnections

Active Connections (in use)

IdleConnections

Idle Connection count

ThreadsAwaitingConnection

The number of threads waiting for a connection (when all available connections are in use)

TotalConnectionsTotal Connections

Hibernate (org.hibernate.core:sessionFactory=bitbucket.core,serviceRole=org.hibernate.stat.Statistics,serviceType=org.hibernate.stat.internal.ConcurrentStatisticsImpl)

NameDescription

QueryCacheHitCount

Global number of cached queries successfully retrieved from cache

QueryCacheMissCount

Global number of cached queries not found in cache

SecondLevelCacheHitCount

Global number of cacheable entities/collections successfully retrieved from the cache

SecondLevelCacheMissCount

Global number of cacheable entities/collections not found in the cache and loaded from the database

Expose JMX MBeans within Bitbucket

To enable Bitbucket to publish specific statistics using JMX:

  1. Locate and open the bitbucket.properties file in the <Bitbucket home directory>/shared directory. 
    1. Add this property to the file.

      jmx.enabled=true
    2. Save and close the file.
       
  2. Create a JMX password file for secure access to JMX monitoring.
     
  3. Modify the set-jmx-opts.sh file to enable Bitbucket to expose JMX Mbeans.

These changes will not take effect until Bitbucket is restarted.

Set up the JMX password file

Set up a JMX password file to secure access to JMX monitoring.

  1. Create a file named jmx.access.

    This file will contain password information. Ensure the file is only readable by the secure user Bitbucket will run under. However, note that if the user cannot read the file Bitbucket will fail to start.

  2. Edit the jmx.access file to include this property and save the file.

    monitorRole <password>

    If you wish to use a username other than monitorRole or controlRole you will need to modify the jmxremote.access file located in the /lib/management/ directory of the installed Java.

  3. Change ownership of jmx.access file,

    chown bitbucket:bitbucket <path>/jmx.access

    where bitbucket is the user that runs Bitbucket service.

  4. Change file permissions of jmx.access file.

    chmod 600 <path>/jmx.access

Modify the Bitbucket environment file

Modify the set-jmx-opts.sh (for Windows set-jmx-opts.bat) files to enable JMX monitoring:

  1. Within the bin directory, locate the file set-jmx-opts.sh (for Windows set-jmx-opts.bat) and change these properties.

    JMX_REMOTE_AUTH=password
    JMX_REMOTE_PORT=3333
    RMI_SERVER_HOSTNAME=-Djava.rmi.server.hostname=<hostname>
    JMX_PASSWORD_FILE=<path>/jmx.access
  2. Restart Bitbucket.

Docker

For Docker deployments, the properties can be passed as Docker environment variables:

Sample:

docker run -v /data/bitbucket:/var/atlassian/application-data/bitbucket \
  --name="bitbucket" \
  -d -p 7990:7990 -p 7999:7999 -p 3333:3333 \
  -e JMX_ENABLED=true \
  -e JMX_REMOTE_AUTH=password \
  -e JMX_REMOTE_PORT=3333 \
  -e JMX_REMOTE_RMI_PORT=3333 \
  -e RMI_SERVER_HOSTNAME=<hostname> \
  -e JMX_PASSWORD_FILE=<path>/jmx.access \
  atlassian/bitbucket

Verify JMX is configured correctly

These steps use JConsole to test that JMX has been configured correctly. JConsole is a utility that ships with the Oracle JDK.

  1. To start the jconsole utility, from a command line prompt enter

    jconsole

  2. Create a new JConsole connection with similar connection settings.

    bitbucketthe hostname of the instance to monitor

    3333

    the JMX port number previously configured.

    username, passwordvalues configured within the JMX password file jmx.access.
  3. Click Connect.

When configured correctly, you will see the following properties.

com.atlassian.bitbucket

Starting from Bitbucket 8.0, the Ticket metrics are absent from the com.atlassian.bitbucket property and must be fetched from the Bitbucket Mesh sidecar.

Learn how to enable JMX monitoring for the Mesh sidecar in BSERV-13623 - Getting issue details... STATUS

  • CommandTickets
  • HostingTickets
  • Projects
  • Repositories
  • ScmStatistics
  • Tickets
  • EventStatistics
  • ClusterLocks

  • SshSessions

com.atlassian.bitbucket.thread-pools
  • EventThreadPool
  • IoPumpThreadPool
  • ScheduledThreadPool

Example performance dashboard

This dashboard was generated using Java Mission Control that ships with the Oracle JDK (since 1.7u40). See the documentation that comes with your JMX client of choice for more information. 

Configuring JMX to use SSL

You can find information about the options for configuring JMX to use SSL in the set-jmx-opts files. Comprehensive documentation is available from Oracle.

In-product diagnostics metrics

Expand the following sections to learn more about the metrics available for in-product diagnostics.

To use these metrics, make sure you've first enabled JMX.

SSH connection metrics
Bean ObjectNameMetric Description
com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=active,name=value
  • ssh.sessions.active.value

The latest measure of the number of active SSH sessions.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=active,name=statistics
  • ssh.sessions.active.statistics

Aggregated statistics of the number of active SSH sessions.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=closed,name=value
  • ssh.sessions.closed.value

The latest measure of the number of closed SSH sessions.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=created,name=value
  • ssh.sessions.created.value

The latest measure of the number of created SSH sessions.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=created,name=statistics
  • ssh.sessions.created.statistics

Aggregated statistics of the number of created SSH sessions.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=disconnected,category03=connection,
category04=lost,name=value
  • ssh.sessions.disconnected.connection.lost.value

The number of disconnected SSH requests due to too many concurrent connections.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=disconnected,category03=connection,
category04=lost,name=statistics
  • ssh.sessions.disconnected.connection.lost.statistics

Aggregated statistics of the number of disconnected SSH requests due to too many concurrent connections.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=disconnected,category03=limit,
name=value
  • ssh.sessions.disconnected.limit.value

The number of disconnected SSH requests due to connection lost.

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=disconnected,category03=limit,
name=statistics
  • ssh.sessions.disconnected.limit.statistics

Aggregated statistics of the number of disconnected SSH requests due to too many concurrent connections

com.atlassian.bitbucket:type=metrics,
category00=ssh,category01=sessions,
category02=error,name=counter
  • ssh.sessions.error.counter

The count of SSH connection failures since the last restart.

Ticket metrics
Bean ObjectNameMetric Description
com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=command,
category02=available,name=value
  • tickets.command.available.value

The latest measure of the number of available Command tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=command,
category02=available,name=statistics
  • tickets.command.available.statistics

Aggregated statistics of the number of available Command tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=command,
category02=used,name=value
  • tickets.command.used.value

The latest measure of the number of used Command tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=command,
category02=used,name=statistics
  • tickets.command.used.statistics

Aggregated statistics of the number of used Command tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=hosting,
category02=available,name=value
  • tickets.hosting.available.value

The latest measure of the number of available Hosting tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=hosting,
category02=available,name=statistics
  • tickets.hosting.available.statistics

Aggregated statistics of the number of available Hosting tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=hosting,
category02=used,name=value
  • tickets.hosting.used.value

The latest measure of the number of used Hosting tickets.

com.atlassian.bitbucket:type=metrics,
category00=tickets,category01=hosting,
category02=used,name=statistics
  • tickets.hosting.used.statistics

Aggregated statistics of the number of used Hosting tickets.

Storage metrics
Bean ObjectNameMetric Description

com.atlassian.bitbucket:type=metrics,

category00=storage,category01=space,

category02=local,category03=free,name=value

  • storage.space.local.free.value

The value of the free space on the disk where the BB local storage is located.

com.atlassian.bitbucket:type=metrics,

category00=storage,category01=space,

category02=local,category03=used,name=value

  • storage.space.local.used.value

The value of the used space on the disk where the BB local storage is located.

com.atlassian.bitbucket:type=metrics,

category00=storage,category01=space,category02=local,

category03=caches,name=value

  • storage.space.local.caches.value

The size of the BITBUCKET_HOME/caches directory in bytes.

com.atlassian.bitbucket:type=metrics,

category00=storage,category01=space,

category02=local,category03=logs,name=value

  • storage.space.local.logs.value

The size of the BITBUCKET_HOME/log directory in bytes.

com.atlassian.bitbucket:type=metrics,

category00=storage,category01=space,category02=local,

category03=tmp,name=value

  • storage.space.local.tmp.value

The size of the BITBUCKET_HOME/tmp directory in bytes.

Enabling in-product diagnostics monitoring

In-product monitoring is enabled by default. 

JMX logging polling interval is set to 60 seconds and can't be modified.

To manage it:

  1. Go to Administration > General configuration > Monitoring.
  2. Use the Enable in-product diagnostics toggle to enable or disable in-product monitoring.

Log formatting

Writing to atlassian-bitbucket-ipd-monitoring.log is done via log4j. Its configuration is managed in logback-spring.xml.

Log contents

By default, a concise set of data is included in each log entry. An extended set of data can be logged by enabling the bitbucket.in.product.diagnostics.extended.logging dark feature flag.

Learn how to enable the dark feature flag

In the following tables, see the structures of the concise and extended logging formats.

The metrics in JMX always go in the extended data format

Concise data

MBean TypePropertiesAttributes
Counter

timestamp

label

attributes

_count
Value_value
Statistics

_99thPercentile

_max

_min

_mean

Show me an example of the concise log line format
2023-01-13 11:51:13,106 IPDMONITORING {"timestamp":"1673610673","label":"DB.CONNECTION.POOL.NUMACTIVE.STATISTICS","attributes":{"_max":"2.0","_mean":"1.2436699769063984","_99thPercentile":"2.0","_count":"5","_min":"1.0"}}

Extended data

The metrics in JMX always go in the extended data format. Learn more about the metric attributes

MBean TypePropertiesAttributes
Counter

timestamp

label

attributes

objectName

_count

_fifteenMinuteRate

_fiveMinuteRate

_meanRate

_oneMinuteRate

_rateUnit

Value

_value

_number

Statistics

_50thPercentile

_75thPercentile

_95thPercentile

_98thPercentile

_99thPercentile

_999thPercentile

_count

_min

_max

_mean

_stdDev

_durationUnit

_fifteenMinuteRate

_fiveMinuteRate

_meanRate

_oneMinuteRate

_rateUnit

Show me an example of the concise log line format
2022-09-06 18:38:48,015 IPDMONITORING {"timestamp":"1662453528","label":
"DB.CONNECTION.LATENCY.STATISTICS","objectName":
"com.atlassian.confluence:category00\u003ddb,category01\u003dconnection,category02\
u003dlatency,name\u003dstatistics,type\u003dmetrics",
"attributes":{"_oneMinuteRate":"0.02012497818617073","_50thPercentile":"0.0",
"_mean":"1.9379304604014412E-25","_max":"1.0","_stdDev":"4.40219315841711E-13",
"_98thPercentile":"0.0","_meanRate":"0.003612560785169162","_rateUnit":
"events/second","_99thPercentile":"0.0","_count":"16","_durationUnit":
"milliseconds","_75thPercentile":"0.0","_fiveMinuteRate":
"0.005912972095043379","_fifteenMinuteRate":"0.0037696657500141968",
"_999thPercentile":"0.0","_95thPercentile":"0.0","_min":"0.0"}}

Definitions of metric attributes

Expand the following sections to learn more about metric attributes.

Counter metric attributes

Attribute

Definition

_count

The number of occurrences of a metric within the current time window

_fifteenMinuteRate

The number of occurrences of a metric over the last 15 minutes

_fiveMinuteRate

The number of occurrences of a metric over the last five minutes

_meanRate

The mean rate at which events have occurred since the meter was created

_oneMinuteRate

The number of occurrences of a metric over the last one minute

_rateUnit

The unit of measure used for rates

Pay attention to the following attributes:  _oneMinuteRate, _fiveMinuteRate, and _fifteenMinuteRate.

The _count gives no indication of how the measurements have changed over time. A sense of recency is provided with the minute rates.

Value metric attributes

Attribute

Definition

_value

A most recently sampled value of the metric

_number

Contains the same value as the _value attribute

Statistics metric attributes

The metrics of the statistics MBean type are also known as aggregated values. They provide statistics for the items that have been subjected to any changes over a period of time. For example, for the items that have been processed in a mail queue or added to an error mail queue.

Time window

Unless stated, aggregated values are calculated over a sliding time window. It covers the last five minutes, approximately.

Percentile values are calculated using a reservoir sampling technique. This technique uses a small, manageable set of values that is statistically representative of the data stream as a whole, hence reducing the quantity of data that must be held in memory.

Resets

Outside of the sliding time window, all aggregated values are reset:

  • After each system restart.

  • After each time JMX monitoring or in-product diagnostic metrics are enabled.

Learn more about JMX monitoring and in-product diagnostic in other Data Center products:

In the following table, find the definitions of statistics metric attributes.

Attribute

Definition

_50thPercentile

A measured value below which 50% of all measurements can be found within the current time window; also referred to as the median value.

This attribute provides an alternative to the mean as a representation of the middle measurement. The median is less likely to be skewed by outlier values than the mean.

_75thPercentile

The measured value below 75% of all measurements that can be found within the current time window; the third quartile value

_95thPercentile

The measured value below 95% of all measurements that can be found within the current time window

_98thPercentile

The measured value below 98% of all measurements that can be found within the current time window

_99thPercentile

The measured value below 99% of all measurements that can be found within the current time window

_999thPercentile

The measured value below 999% of all measurements that can be found within the current time window

_count

The number of occurrences of a metric within the current time window

_min

The minimum measured value within the current time window

_max

The maximum measure value within the current time window; the statistical range between _max and _min provides a measure of values variability

_mean

The average value within the current time window.

This attribute can be skewed by large outlier measurements. In such cases, the _50thPercentile provides a better measure of the middle value.

_stdDev

A measure of the data variability.

A low standard deviation indicates that the values tend to be close to the mean of the set, while a high standard deviation indicates that the values are spread out over a wider range of values.

_durationUnit

The unit of measure used for durations

_fifteenMinuteRate

The number of occurrences of a metric over the last 15 minutes

_fiveMinuteRate

The number of occurrences of a metric over the last five minutes

_meanRate

The mean rate at which events have occurred since the meter was created

_oneMinuteRate

The number of occurrences of a metric over the last one minute

_rateUnit

The unit of measure used for rates

Pay attention to the following attributes:  _oneMinuteRate, _fiveMinuteRate, and _fifteenMinuteRate.

The _count gives no indication of how the measurements have changed over time. A sense of recency is provided with the minute rates.

Last modified on Feb 7, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.