Hi support, I still have a lot of duplicate data d...
# support
m
Hi support, I still have a lot of duplicate data due to the PromQL dot to underscore migration. How should this be resolved in the future?
Copy code
┌─metric_name───────────────────────────────────────────────┬─sample_count─┐
│ datastore_time_customer_rate                              │      4742473 │
│ datastore_time_customer:rate                              │      4386560 │
│ datastore_time_customer_seconds_bucket                    │      4376946 │
│ nginx_ingress_controller_request_duration_seconds_bucket  │      2759941 │
│ nginx_ingress_controller_request_duration_seconds.bucket  │      2739037 │
│ customer_adrequest_seconds_bucket_rate                    │      2626712 │
│ nginx_ingress_controller_response_size_bucket             │      2531205 │
│ nginx_ingress_controller_request_size_bucket              │      2529700 │
│ nginx_ingress_controller_request_size.bucket              │      2510255 │
│ nginx_ingress_controller_response_size.bucket             │      2509547 │
│ customer:adrequest_seconds_bucket:rate                    │      2439399 │
│ customer_user_check_count_total_rate                      │      2357282 │
│ customer:user_check_count_total:rate                      │      2229869 │
│ nginx_ingress_controller_response_duration_seconds_bucket │      2010263 │
│ nginx_ingress_controller_response_duration_seconds.bucket │      1994099 │
│ nginx_ingress_controller_connect_duration_seconds_bucket  │      1963446 │
│ nginx_ingress_controller_connect_duration_seconds.bucket  │      1947365 │
│ nginx_ingress_controller_bytes_sent_bucket                │      1840603 │
│ nginx_ingress_controller_bytes_sent.bucket                │      1825860 │
│ nginx_ingress_controller_header_duration_seconds_bucket   │      1764742 │
│ nginx_ingress_controller_header_duration_seconds.bucket   │      1750758 │
n
@Srikanth Chekuri, could you please check this out?
s
Hi @Matti, we expect to publish the docs for completing the migration next week as we are still figuring out some details.
m
Good to hear @Srikanth Chekuri, we have been quite a heavy SigNoz user since for quite some time now. I think this will reduce some load on our collectors eventually.
(these were metrics from the last hour, we get billions of metrics in total 🙂)
s
Correct, it is also expected to reduce the load on the clickhouse as we are doing the clean up of inefficient stuff lurking around.