A list of methods for which to create a transaction or span. If you want to monitor a large number of methods, use trace_spans_enabled instead. This works by instrumenting each matching method to include code that creates a span for the method. While creating a span is quite cheap in terms of performance, instrumenting a whole code base or a method which is executed in a tight loop leads to significant overhead.

Syntax

Using a pointcut-like syntax, you can match based on:
  • Method modifier (optional): public, protected, private or *
  • Package and class name (wildcards include sub-packages): org.example.*
  • Method name: myMeth*d
  • Method argument types (optional): (*lang.String, int[])
  • Classes with a specific annotation (optional): @*ApplicationScoped
  • Classes with a specific annotation that is itself annotated with the given meta-annotation (optional): @@javax.enterpr*se.context.NormalScope
The full syntax is:

Examples

Configuration

Configuration Reference

Common Configurations

Trace all public methods in CDI-Annotated beans

Trace specific service methods

Trace multiple patterns

Use comma to separate multiple patterns:

Important Notes

  • Only use wildcards if necessary. The more methods you match the more overhead will be caused by the agent.
  • Changing this value at runtime can slow down the application temporarily.

See also