@bishida  the kind `Server` is working. Thank you very much for your time ... View more

@bishida Hi! I tried everything and it still does not work. I believe there is something missing on my span that is skipping it from dashboard filters somehow. Look, now I tried changing my span to use a service name which is a field that should automatically works without a metricSet.  This is now my new tag using a new service name that works filtering through trace analyzer and the service.name seems to be the right one Captura de pantalla 2026-02-11 a la(s) 12.22.59 p.m..png   Captura de pantalla 2026-02-11 a la(s) 12.23.26 p.m..png This is the span information for that trace: Captura de pantalla 2026-02-11 a la(s) 12.24.10 p.m..png And If I download the trace from splunk this is it: { "traceId": "672aed1f27501bdb3e82ddf815bd2e83", "spanId": "ee7324d1d26ee5aa", "parentId": null, "serviceName": "conduit-elasticsearch", "operationName": "elasticsearch.query", "startTime": "2026-02-11T17:11:24.735159Z", "durationMicros": 46540, "tags": { "server.host": "elasticsearch", "otel.scope.name": "conduit-elasticsearch", "service.name": "conduit-elasticsearch", "db.elasticsearch.params": "{\"timeout\":\"120s\"}", "http.url": "test?/doc/_search", "version": "deploy_sha\n", "environment": "development", "db.elasticsearch.body": "{\"query\":{\"bool\":{...}}}", "http.request.method": "GET", "span.kind": "client", "db.elasticsearch.status": "success", "server.port": "9200", "db.system.name": "elasticsearch", "url.full": "test?/doc/_search", "app_env": "development", "db.operation.name": "GET", "db.elasticsearch.method": "GET" }, "processTags": { "environment": "development", "host.name": "5ad3d42c0fa2", "os.type": "linux", "env": "development", "version": "deploy_sha\n", "app_env": "development" }, "logs": [], "splunk": {}, "objectType": "span" }, However in the dashboard these kind of spans still do not appear and filters here do not work even with service name Captura de pantalla 2026-02-11 a la(s) 12.26.44 p.m..png   and trying with other kind of service names using sf_service it works when it is populated via open telemetry libraries. Howerver this custom one should be having something wrong. I appreciate your help, thanks! ... View more

Thanks for sharing @bishida I sill have no luck. Quick question in this example are you generating the record as "cloud.availability.zone" or as "cloud_availability_zone" In my case I send the record with dots and expect that spunk accept the filter with underscore. Thanks! ... View more

Hi @bishida Thanks for your answer. Yes, after creating the new metricSet I generate new traces and tried with multiple filter ways like:  data('service.request.count', filter=filter('db.system.name', 'elasticsearch'), rollup='sum').sum().publish() data('service.request.count', filter=filter('db_system_name', 'elasticsearch'), rollup='sum').sum().publish() data('spans.count', filter=filter('db.system.name', 'elasticsearch'), rollup='sum').sum().publish(label='Total Queries') data('spans.count', filter=filter('db_system_name', 'elasticsearch'), rollup='sum').sum().publish(label='Total Queries')  I even tried using `sf_mms_id` When creating the MetricSet I selected All Services, also I tried switching "Create Monitoring MetricSet (MMS)" on and off. Thank you! ... View more