https://signoz.io logo
Powered by
a

Alexei Zenin

08/17/2022, 3:47 PM
I added service.namespace and deployment.environment to my process but don’t see the ability to filter by it in the UI (using 0.10.2). The process was running without those parameters before and sending to SigNoz. Is there something I need to do to enable it? Config for collector:
Copy code
receivers:
  otlp/spanmetrics:
    protocols:
      grpc:
        endpoint: localhost:12345
  otlp:
    protocols:
      http:
        endpoint: 0.0.0.0:4318

processors:
  batch:
    send_batch_size: 10000
    send_batch_max_size: 11000
    timeout: 10s
  signozspanmetrics/prometheus:
    metrics_exporter: prometheus
    latency_histogram_buckets: [100us, 1ms, 2ms, 6ms, 10ms, 50ms, 100ms, 250ms, 500ms, 1000ms, 1400ms, 2000ms, 5s, 10s, 20s, 40s, 60s ]
    dimensions_cache_size: 10000
    dimensions:
      - name: service.namespace
        default: default
      - name: deployment.environment
        default: default

exporters:
  clickhousetraces:
    datasource: tcp://${CLICKHOUSE_HOST}:${CLICKHOUSE_PORT}/?database=signoz_traces&username=${CLICKHOUSE_USER}&password=${CLICKHOUSE_PWD}
  clickhousemetricswrite:
    endpoint: tcp://${CLICKHOUSE_HOST}:${CLICKHOUSE_PORT}/?database=signoz_metrics&username=${CLICKHOUSE_USER}&password=${CLICKHOUSE_PWD}
    resource_to_telemetry_conversion:
      enabled: true
  prometheus:
    endpoint: 0.0.0.0:8889

extensions:
  health_check:
    endpoint: 0.0.0.0:13133
service:
  telemetry:
    metrics:
      address: 0.0.0.0:8888
  extensions: [health_check]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [signozspanmetrics/prometheus, batch]
      exporters: [clickhousetraces]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [clickhousemetricswrite]
    metrics/spanmetrics:
      receivers: [otlp/spanmetrics]
      exporters: [prometheus]
Note: I am not sending directly to this collector but via an agent collector on the instance which forwards to this one via OTLP
The app is Spring boot with this command line config: 
-Dotel.resource.attributes=service.name=${ProjectName}-${EnvironmentName}-${ServiceName},service.namespace=${ProjectName},deployment.environment=${EnvironmentName}
I see the bar, when I click on it it says no attributes to filter by
Some apps are sending attributes others arent which might play a role.
Most of the data sent never had service.namespace and deployment.environment sent before
Would be nice if you could filter by service.name as well
p

Pranay

08/17/2022, 4:43 PM
Ah, I see. No it should filter for apps with those attributes available. @Prashant Shahi @Vishal Sharma do you have more insights on this
p

Prashant Shahi

08/17/2022, 10:36 PM
@Alexei Zenin We had some issues with resource attribute filter around v0.10.x The fix has been merged to 
develop
branch. It will be included in the next release. https://github.com/SigNoz/signoz/pull/1521
a

Alexei Zenin

08/17/2022, 10:38 PM
Ah excellent, yeah also noticed services that stop sending data also showing up still in service list. Ill wait for the fix and then upgrade đź‘Ť
Found out my issue! Turns out my otel-collector-metrics was misconfigured and was never scraping properly thus not populating the DB/External calls metrics and looks like it also breaks the filter functionality. Once I got the scraping working again i could do the filtering by the dimensions.
One thing I noticed though is when filtering it doesn’t actually remove the services from the list and just sets all their metrics to 0.00
p

Prashant Shahi

08/18/2022, 6:19 PM
sets all their metrics to 0.00
That is fixed in 
develop
otel-collector-metrics was misconfigured and was never scraping properly thus not populating the DB/External calls metrics
Was it misconfiguration from yourself with overwrite data or something else?
Powered by