Qubership Profiler Agent

This repository container the java agent that can attach as a -javaagent to the JVM and collect information as continuous tracing profiler.

• Qubership Profiler Agent
  • Features
  • Library and framework instrumentation
  • How to build
    • Local build

Features

• Trace for slow requests and errors
• Continuous profiling
• SQL capture (queries and binds)
• Service call capture

Library and framework instrumentation

Application servers or Portals:

• Liferay

Build systems:

• ANT
  • ANT (<=1.10.1)
  • ANT (>=1.10.2)

Databases:

• DataStax Cassandra
  • DataStax Cassandra 3.x
  • DataStax cassandra 4.x
• ElasticSearch
• MySQL JDBC
• PostgeSQL JDBC

Distribution tracing:

• Brave (Zipkin agent)
• Jaeger
• Ocelot

HTTP clients:

• HTTP
• Java HTTP Client
• Tomcat <= 9.x
• Tomcat >= 10.x
• Undertow < 2.3
• Undertow >= 2.3

Java Frameworks:

• Apache Felix
• Equinox
• Spring Framework
  • Spring REST

Loggers:

• Log4j

Other:

• Jackson
• Quartz Scheduler
• Rhino
• Test

Queues:

• ActiveMQ
• HornetQ
• RabbitMQ

How to build

Local build

Build requirements:

• Java 17

To build all the artifacts and execute tests, run the following:

git clone https://github.com/Netcracker/qubership-profiler-agent.git
./gradlew build # builds everything
./gradlew tasks # lists available tasks

Releasing Qubership Profiler

This project defines a manual release workflow.

To trigger a release, go to the 👉 Actions tab → release.yaml and run it manually.

The release workflow uses Release Drafter to prepare release notes, and it uses labels to group the changes. If you need to adjust the notes, update the labels as needed.

Here's the full step-by-step:

1. Navigate to Release Workflow
2. Click on Run workflow
3. Select the branch name to be released
4. By default, release workflow would pick the release version from gradle.properties, and you can overrided it if needed
5. Click on Run workflow

The release workflow would perform the following steps:

1. Check if the release tag v... does not exist yet, otherwise it would terminate
2. Bump the version in gradle.properties to the release version (e.g., if the manually provided version differs)
3. Build and publish the artifacts to Central Portal
4. Create the release tag and publish GitHub release
5. Bump the version in gradle.properties to the next patch version