Overview | Package | Class | Tree | Deprecated | Index | Help
| JProfiler API
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD

## com.jprofiler.api.agent.probe
Interface ProbeProvider

    public interface ProbeProvider

A probe provider is queried by the profiling agent for the probes that should be activated. To add your probes to the profiled JVM, you have to create an implementation that instantiates all probes and returns them in an array. In addition, you have to add the VM parameter

     -Djprofiler.probeProvider=fully-qualified-class

to the java call of the profiled process.

Probes are only functional if the JVM is actually profiled, i.e. the `-agentpath:[path to jprofilerti library]` (JVMTI) or the `-Xrunjprofiler` (JVMPI) argument is present as a JVM parameter.

Note that if you define custom probes in the JProfiler GUI, you will not have to use this class since JProfiler deploys your custom probes in that case.

Method Summary
`Probe[]` | `getProbes()` Returns the probes that should be activated.

Method Detail

### getProbes

    Probe[] getProbes()

  Returns the probes that should be activated.

  If you analyze payload information with the profiling platform, the payload id is always equal to the one-based index in the returned array, i.e. if you return a single interceptor, the payload id is always 1.

  Returns:
    the interceptors

Overview | Package | Class | Tree | Deprecated | Index | Help
| JProfiler API
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD