Quarkus

Supported OS Linux Windows Mac OS

Versión de la integración1.1.0

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Overview

This check monitors Quarkus through the Datadog Agent.

Setup

Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.

Installation

The Quarkus check is included in the Datadog Agent package starting with Agent 7.62. No additional installation is needed on your server.

Configuration

Follow these steps to set up metric generation in Quarkus.

Then configure the Agent:

Edit the quarkus.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Quarkus performance data. See the sample quarkus.d/conf.yaml for all available configuration options.
Restart the Agent.

Collecting Logs

Follow these steps to configure Quarkus to emit logs.

Collecting logs is disabled by default in the Datadog Agent. Enable it in your datadog.yaml file:

logs_enabled: true

Edit the logs section of your quarkus.d/conf.yaml file to start collecting your RabbitMQ logs:

logs:
 - type: file
   path: /var/log/application.log
   source: quarkus
   service: quarkus-app

Validation

Run the Agent’s status subcommand and look for quarkus under the Checks section.

Data Collected

Metrics

quarkus.http_server.active_requests (gauge)	Requests to the server that are active right now. Shown as request
quarkus.http_server.bytes_read.count (count)	Number of times some bytes were received by the server.
quarkus.http_server.bytes_read.max (gauge)	Maximum number of bytes currently received by the server. Shown as byte
quarkus.http_server.bytes_read.sum (count)	Total number of bytes received by the server since it started. Shown as byte
quarkus.http_server.bytes_written.count (count)	Number of times some bytes were by the server.
quarkus.http_server.bytes_written.max (gauge)	Current maximum number of bytes sent by the server. Shown as byte
quarkus.http_server.bytes_written.sum (count)	Total number of bytes sent by the server. Shown as byte
quarkus.http_server.connections.seconds.max (gauge)	The duration of the connections in seconds. Shown as second
quarkus.http_server.requests.seconds.count (count)	The number of requests observed so far.
quarkus.http_server.requests.seconds.max (gauge)	The current longest request duration in seconds. Shown as second
quarkus.http_server.requests.seconds.sum (count)	Total number of seconds that all requests took so far. Shown as second
quarkus.jvm.buffer.count_buffers (gauge)	An estimate of the number of buffers in the pool. Shown as buffer
quarkus.jvm.buffer.memory_used.bytes (gauge)	An estimate of the memory that the Java virtual machine is using for this buffer pool. Shown as byte
quarkus.jvm.buffer.total_capacity.bytes (gauge)	An estimate of the total capacity of the buffers in this pool. Shown as byte
quarkus.jvm.classes.loaded_classes (gauge)	The number of classes that are currently loaded in the Java virtual machine.
quarkus.jvm.gc.live_data_size.bytes (gauge)	Size of long-lived heap memory pool after reclamation. Shown as byte
quarkus.jvm.gc.max_data_size.bytes (gauge)	Max size of long-lived heap memory pool. Shown as byte
quarkus.jvm.gc.overhead (gauge)	An 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].
quarkus.jvm.memory.committed.bytes (gauge)	The amount of memory in bytes that is committed for the Java virtual machine to use. Shown as byte
quarkus.jvm.memory.max.bytes (gauge)	The maximum amount of memory in bytes that can be used for memory management. Shown as byte
quarkus.jvm.memory.usage_after_gc (gauge)	The percentage of long-lived heap pool used after the last GC event, in the range [0..1]. Shown as fraction
quarkus.jvm.memory.used.bytes (gauge)	The amount of used memory. Shown as byte
quarkus.jvm.threads.daemon_threads (gauge)	The current number of live daemon threads. Shown as thread
quarkus.jvm.threads.live_threads (gauge)	The current number of live threads including both daemon and non-daemon threads. Shown as thread
quarkus.jvm.threads.peak_threads (gauge)	The peak live thread count since the Java virtual machine started or peak was reset. Shown as thread
quarkus.jvm.threads.states_threads (gauge)	The current number of threads. Shown as thread
quarkus.netty.allocator.memory.pinned (gauge)	Size, in bytes, of the memory that the allocated buffer uses. Shown as byte
quarkus.netty.allocator.memory.used (gauge)	Size, in bytes, of the memory that the allocator uses. Shown as byte
quarkus.netty.allocator.pooled.arenas (gauge)	Number of arenas for a pooled allocator. Shown as byte
quarkus.netty.allocator.pooled.cache_size (gauge)	Size, in bytes, of the cache for a pooled allocator. Shown as byte
quarkus.netty.allocator.pooled.chunk_size (gauge)	Size, in bytes, of memory chunks for a pooled allocator. Shown as byte
quarkus.netty.allocator.pooled.threadlocal_caches (gauge)	Number of ThreadLocal caches for a pooled allocator.
quarkus.netty.eventexecutor.tasks_pending (gauge)	Number of pending tasks in the event executor. Shown as task
quarkus.process.cpu.usage (gauge)	The recent cpu usage for the Java Virtual Machine process.
quarkus.process.files.max_files (gauge)	The maximum file descriptor count. Shown as file
quarkus.process.files.open_files (gauge)	The open file descriptor count. Shown as file
quarkus.process.uptime.seconds (gauge)	The uptime of the Java virtual machine. Shown as second
quarkus.system.cpu.count (gauge)	The number of processors available to the Java virtual machine.
quarkus.system.cpu.usage (gauge)	The recent cpu usage of the system the application is running in.
quarkus.system.load_average_1m (gauge)	The 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.
quarkus.worker_pool.active (gauge)	The number of resources from the pool currently used.
quarkus.worker_pool.idle (gauge)	The number of resources from the pool currently used.
quarkus.worker_pool.queue.delay.seconds.count (count)	Number of items that spent time in the waiting queue before being processed.
quarkus.worker_pool.queue.delay.seconds.max (gauge)	Current maximum time spent in the waiting queue before being processed. Shown as second
quarkus.worker_pool.queue.delay.seconds.sum (count)	Total time spent in the waiting queue before being processed.
quarkus.worker_pool.queue.size (gauge)	Number of pending elements in the waiting queue.
quarkus.worker_pool.ratio (gauge)	Ratio of workers being used at the moment. Shown as fraction
quarkus.worker_pool.usage.seconds.count (count)	Number of times resources from the pool were being used. Shown as second
quarkus.worker_pool.usage.seconds.max (gauge)	Maximum time spent using resources from the pool. Shown as second
quarkus.worker_pool.usage.seconds.sum (count)	Total time spent using resources from the pool. Shown as second

Events

The Quarkus integration does not include any events.

Service Checks

quarkus.openmetrics.health
Returns CRITICAL if the Agent is unable to connect to the Quarkus OpenMetrics endpoint, otherwise returns OK.
Statuses: ok, critical

Troubleshooting

Need help? Contact Datadog support.