otelcol.connector.servicegraph debug_metrics block enabled , but not able to view the detailed metrics

[sindhupanchanam]

Issue 1:
We have enabled the debug_metrics block in our otelcol.connector.servicegraph configuration, setting disable_high_cardinality_metrics to true and deployed it. However, we are not seeing detailed metric information.

otelcol.connector.servicegraph "default" {
  dimensions = ["service.name", "http.method", "http.request.method", "http.response.status_code", "http.status_code", "http.route", "http.target", "service.version","service.namespace","k8s.namespace.name","deployment.environment"]
  latency_histogram_buckets = ["0.1s", "0.2s", "0.4s", "0.8s", "1.6s", "3.2s", "6.4s", "12.8s"]
  store{
    max_items = 200000
  }
  debug_metrics {
    disable_high_cardinality_metrics = true
    level = "detailed"
  }
  output {
    metrics = [otelcol.exporter.prometheus.service_graph.input]
  }
}

collecting and processing trace data into service graph metrics? How can we ensure that all metrics are being sent to Mimir from the service graph component? We are checking the OTEL receiver count, which matches. Apart from this, is there any other clear proof to confirm that all data is being pushed to Mimir without any drop?"

Issue 2:
the traces_service_graph_dropped_spans_total metric is not appearing from the service graph component. Is it correct to assume that this metric will only appear if there are dropped spans during the generation of the service graph, and it might not be generated if there are no dropped spans?"