Is your feature request related to a problem? Please describe.
Hazelcast 5.x is not currently included in the Java agent’s supported libraries. I’d like to contribute instrumentation for Hazelcast map operations.
Describe the solution you'd like
Hazelcast 5.0+ Java client operations on IMap
Synchronous and asynchronous calls
Local operation spans only; no cross-member context propagation in v1
No keys, values, or query payloads captured
Describe alternatives you've considered
There was previously an open-tracing contribution for Hazelcast project here.
Manual instrumentation could also work?
Additional context
Before implementation, I’d appreciate guidance on:
Whether client-only v1 is an acceptable scope;
Appropriate span naming/attributes given Hazelcast’s cache/data-grid model;
Whether this should be disabled by default because of potential span volume;
Whether there is a preferred Hazelcast interception point or public API boundary.
Tip
No response
Is your feature request related to a problem? Please describe.
Hazelcast 5.x is not currently included in the Java agent’s supported libraries. I’d like to contribute instrumentation for Hazelcast map operations.
Describe the solution you'd like
Hazelcast 5.0+ Java client operations on IMap
Synchronous and asynchronous calls
Local operation spans only; no cross-member context propagation in v1
No keys, values, or query payloads captured
Describe alternatives you've considered
There was previously an open-tracing contribution for Hazelcast project here.
Manual instrumentation could also work?
Additional context
Before implementation, I’d appreciate guidance on:
Whether client-only v1 is an acceptable scope;
Appropriate span naming/attributes given Hazelcast’s cache/data-grid model;
Whether this should be disabled by default because of potential span volume;
Whether there is a preferred Hazelcast interception point or public API boundary.
Tip
No response