obsdog

Quarkus integration metrics

The official Datadog integration for monitoring Quarkus. It collects 50 metrics.

Official summary

Monitor your application built with Quarkus.

Metric types

  • gauge (value at a point in time): 40
  • count (occurrences in the interval): 10

Metrics

Descriptions are the official definitions, unedited.

MetricTypeUnit
quarkus.http_server.active_requestsRequests to the server that are active right now.gaugerequest
quarkus.http_server.bytes_read.countNumber of times some bytes were received by the server.count-
quarkus.http_server.bytes_read.maxMaximum number of bytes currently received by the server.gaugebyte
quarkus.http_server.bytes_read.sumTotal number of bytes received by the server since it started.countbyte
quarkus.http_server.bytes_written.countNumber of times some bytes were by the server.count-
quarkus.http_server.bytes_written.maxCurrent maximum number of bytes sent by the server.gaugebyte
quarkus.http_server.bytes_written.sumTotal number of bytes sent by the server.countbyte
quarkus.http_server.connections.seconds.maxThe duration of the connections in seconds.gaugesecond
quarkus.http_server.requests.seconds.countThe number of requests observed so far.count-
quarkus.http_server.requests.seconds.maxThe current longest request duration in seconds.gaugesecond
quarkus.http_server.requests.seconds.sumTotal number of seconds that all requests took so far.countsecond
quarkus.jvm.buffer.count_buffersAn estimate of the number of buffers in the pool.gaugebuffer
quarkus.jvm.buffer.memory_used.bytesAn estimate of the memory that the Java virtual machine is using for this buffer pool.gaugebyte
quarkus.jvm.buffer.total_capacity.bytesAn estimate of the total capacity of the buffers in this pool.gaugebyte
quarkus.jvm.classes.loaded_classesThe number of classes that are currently loaded in the Java virtual machine.gauge-
quarkus.jvm.gc.live_data_size.bytesSize of long-lived heap memory pool after reclamation.gaugebyte
quarkus.jvm.gc.max_data_size.bytesMax size of long-lived heap memory pool.gaugebyte
quarkus.jvm.gc.overheadAn approximation of the percent of CPU time used by GC activities over the last lookback period or since monitoring began, whichever is shorter, in the range [0..1].gauge-
quarkus.jvm.memory.committed.bytesThe amount of memory in bytes that is committed for the Java virtual machine to use.gaugebyte
quarkus.jvm.memory.max.bytesThe maximum amount of memory in bytes that can be used for memory management.gaugebyte
quarkus.jvm.memory.usage_after_gcThe percentage of long-lived heap pool used after the last GC event, in the range [0..1].gaugefraction
quarkus.jvm.memory.used.bytesThe amount of used memory.gaugebyte
quarkus.jvm.threads.daemon_threadsThe current number of live daemon threads.gaugethread
quarkus.jvm.threads.live_threadsThe current number of live threads including both daemon and non-daemon threads.gaugethread
quarkus.jvm.threads.peak_threadsThe peak live thread count since the Java virtual machine started or peak was reset.gaugethread
quarkus.jvm.threads.states_threadsThe current number of threads.gaugethread
quarkus.netty.allocator.memory.pinnedSize, in bytes, of the memory that the allocated buffer uses.gaugebyte
quarkus.netty.allocator.memory.usedSize, in bytes, of the memory that the allocator uses.gaugebyte
quarkus.netty.allocator.pooled.arenasNumber of arenas for a pooled allocator.gaugebyte
quarkus.netty.allocator.pooled.cache_sizeSize, in bytes, of the cache for a pooled allocator.gaugebyte
quarkus.netty.allocator.pooled.chunk_sizeSize, in bytes, of memory chunks for a pooled allocator.gaugebyte
quarkus.netty.allocator.pooled.threadlocal_cachesNumber of ThreadLocal caches for a pooled allocator.gauge-
quarkus.netty.eventexecutor.tasks_pendingNumber of pending tasks in the event executor.gaugetask
quarkus.process.cpu.usageThe recent cpu usage for the Java Virtual Machine process.gauge-
quarkus.process.files.max_filesThe maximum file descriptor count.gaugefile
quarkus.process.files.open_filesThe open file descriptor count.gaugefile
quarkus.process.uptime.secondsThe uptime of the Java virtual machine.gaugesecond
quarkus.system.cpu.countThe number of processors available to the Java virtual machine.gauge-
quarkus.system.cpu.usageThe recent cpu usage of the system the application is running in.gauge-
quarkus.system.load_average_1mThe sum of the number of runnable entities queued to available processors and the number of runnable entities running on the available processors averaged over a period of time.gauge-
quarkus.worker_pool.activeThe number of resources from the pool currently used.gauge-
quarkus.worker_pool.idleThe number of resources from the pool currently used.gauge-
quarkus.worker_pool.queue.delay.seconds.countNumber of items that spent time in the waiting queue before being processed.count-
quarkus.worker_pool.queue.delay.seconds.maxCurrent maximum time spent in the waiting queue before being processed.gaugesecond
quarkus.worker_pool.queue.delay.seconds.sumTotal time spent in the waiting queue before being processed.count-
quarkus.worker_pool.queue.sizeNumber of pending elements in the waiting queue.gauge-
quarkus.worker_pool.ratioRatio of workers being used at the moment.gaugefraction
quarkus.worker_pool.usage.seconds.countNumber of times resources from the pool were being used.countsecond
quarkus.worker_pool.usage.seconds.maxMaximum time spent using resources from the pool.gaugesecond
quarkus.worker_pool.usage.seconds.sumTotal time spent using resources from the pool.countsecond

Official documentation

Official documentation for the Quarkus integration

Metric names and descriptions are the official Datadog integration definitions (Copyright Datadog, Inc., BSD-3-Clause), reproduced unedited. The full license terms are on the About page.

Related products

IntegrationsIntegrations are the bundle of entry points that pour data from external systems such as AWS and MySQL into Datadog. Where you configure them splits into two families, the Agent side and the cloud account side, and which one you choose changes both what you can see and how billing is counted.Foundation and data collectionLog ManagementLog Management is the product that gathers logs from servers, containers, and cloud services in one place and connects them to search, retention, and notification. It has a distinctive structure in which ingestion and indexing are billed separately.Log managementDatadog AgentSoftware that runs resident on the servers and containers you monitor and delivers metrics, logs, and traces to Datadog.Foundation and data collectionMetricsFrom CPU utilization to user sign-ups, metrics are the core data of Datadog, recording every number in your environment as a time series. If you understand how they are counted before how they are collected, you avoid aggregation mistakes and unexpected charges.Foundation and data collection

Other Metrics integrations

RingCentral36 metricsSilverstripe CMS14 metricsSlurm87 metricsSonatype Nexus41 metricsStorage Management7 metricsStreamNative125 metricsSupabase302 metricsSupabase Cloud65 metricsTemporal Cloud26 metricsTibco EMS50 metricswlan (Wi-Fi)6 metricsWorkato3 metrics