Metric aggregation not working for me

[chanda1998]

we want to achieve metric aggregation using custom attribute in span. We have provided a meter provide customizer in autoConfiguration object like this

`@Override
public void customize(AutoConfigurationCustomizer autoConfiguration) {
configure();
autoConfiguration .addTracerProviderCustomizer(this::configureSdkTracerProvider) .addMeterProviderCustomizer(this::meterProviderCustomizer);
}

private SdkMeterProviderBuilder meterProviderCustomizer(SdkMeterProviderBuilder builder, ConfigProperties config) {  
    return builder.registerView(InstrumentSelector.builder().setName("http.server.request.duration").build()        , View.builder().setAttributeFilter(new HashSet(Arrays.asList("cav.BT"))).build()); }`

but still there is no aggregation of metric, spans and metrices are comming same way as before. Is there any other configuration or code needed to achieve custom aggregation?

[jkwatson]

Can you provide a full reproduction repository with the full configuration and implementation? Along with an explanation of what you expected to happen, and a demonstration of what actually happens? I don't understand what you are trying to do, just based on this little snippet you've provided. A full reproduction would be very helpful in understanding.

[chanda1998]

i want to modify the behaviour of otel java agent, for that i am using extension(https://opentelemetry.io/docs/zero-code/java/agent/extensions/) from the repo https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/examples/extension,

i am inserting a custom attribute in span using DemoSpanProcessor(https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/examples/extension/src/main/java/com/example/javaagent/DemoSpanProcessor.java) which is implementing io.opentelemetry.sdk.trace.SpanProcessor using method io.opentelemetry.api.trace.Span.setAttribute(String key, String value) in implementation of onStart method of SpanProcessor

this span processor is

so i am getting each span with my custom attribute included like this

{traceId=13be054e25837932982af1cb098cf879, spanId=67dab964e0c997c4, parentSpanContext=ImmutableSpanContext{traceId=00000000000000000000000000000000, spanId=0000000000000000, traceFlags=00, traceState=ArrayBasedTraceState{entries=[]}, remote=false, valid=false}, name=POST /dbcallout, kind=SERVER, attributes=AttributesMap{data={cav.TR=22222, url.scheme=http, thread.name=http-nio-8080-exec-1, user_agent.original=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36, server.port=8080, thread.id=63, server.address=localhost, client.address=0:0:0:0:0:0:0:1, url.path=/dbcallout, http.request.method=POST, cav.BT=/dbcallout, http.route=/dbcallout}, capacity=128, totalAddedValues=15}, status=ImmutableStatusData{statusCode=UNSET, description=}, totalRecordedEvents=0, totalRecordedLinks=0, startEpochNanos=1752731544541670529, endEpochNanos=0}

as you can see this span have an attribute cav.BT=/dbcallout

i want metrices to ignore all other fields and consider only this field to report metrics for.

so lets say application generates 5 transactions having cav.BT = /dbcallout and 5 transaction having cav.BT=/http in spans than there should generate 2 metrics, one for all the transaction having /dbcallout and one for all the transaction having /http no matter what other attributes the span have or have not.

command to execute this extension with otel java agent
java -javaagent:/home/apps/opentelemetry-javaagent.jar -Dotel.javaagent.extensions=/home/netdiagnostics/lib/ndotelsdkext-1.0-all.jar -Dotel.service.name=test_by_chandan -Dotel.traces.expor ter=otlp -Dotel.metrics.exporter=cav-nd-metrics-exporter -Dotel.semconv-stability.opt-in=database -Dotel.metrics.collection.enabled=true -Dcav.ndAgentJar=/home/netdiagnostics/lib/ndagent-with-dep.j ar -Dcav.ndHome=/home/netdiagnostics -Dcav.ndlPort=1 -jar /home/Downloads/apache-tomcat-9.0.33/webapps/agentTestingApp.war