Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Profiling Java using the Grafana Agent
Grafana Agent supports Java profiling in Flow mode. Written in the River language, the configuration file is composed of components that are used to collect, transform, and send data.
Configure the components
The pyroscope.java
component is used to continuously profile Java processes running on the local Linux OS
using
async-profiler.
pyroscope.java "java" {
profiling_config {
interval = "15s"
alloc = "512k"
cpu = true
lock = "10ms"
sample_rate = 100
}
forward_to = [pyroscope.write.endpoint.receiver]
targets = discovery.relabel.java.output
}
Using the targets
argument, you can specify which processes and containers to profile on the machine. The targets
can be from discovery.process
component. You can use discovery.process
join argument to join process targets with
extra discoveries such as dicovery.kubernetes
, discovery.docker
and discovery.dockerswarm
.
You can use the discovery.relabel
component to relabel discovered targets and set your own labels . For more
information, see
Components.
The forward_to
parameter should point to a pyroscope.write
component to send the collected profiles to your
Pyroscope Server or
Grafana Cloud.
The special label __process_pid__
must always be present in each target of targets
and corresponds to the PID
of
the process to profile.
The special label service_name
is required and must always be present. If service_name
is not specified, pyroscope.java
attempts to infer it from discovery meta labels. If service_name
is not specified and could not be inferred, then it is
set to unspecified
.
The profiling_config
block describes how async-profiler is invoked.
The following arguments are supported:
For more information on async-profiler configuration, see profiler-options.
Set privileges for the Agent
You must run the agent as root and inside host pid namespace for the pyroscope.java
and discover.process
components to work.
Send data to Grafana Cloud Profiles
When sending to Grafana Cloud Profiles, you can use the following pyroscope.write
component configuration which uses environment variables.
Ensure that you have appropriately configured the GC_URL
, GC_USER
, and GC_PASSWORD
environment variables.
pyroscope.write "endpoint" {
endpoint {
basic_auth {
password = env("GC_PASSWORD")
username = env("GC_USER")
}
url = env("GC_URL")
}
}
Examples
Profiling local process
Profiling docker containers
Profiling kubernetes pods
References
For more information: