David Ashpole

@Gbotttt the metrics you list at the top are part of the metrics from the kubelet, and do not come from kube-state-metrics. /assign @dgrisonnet /triage accepted

/assign @dgrisonnet /triage accepted

Can you try enabling `report_extra_scrape_metrics`? IIRC, that has information about metrics rejected because of the scrape limits. You should also be able to see that the scrape failed using the...

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/prometheusreceiver#getting-started

You can see documentation for the scrape_* metrics here: https://prometheus.io/docs/concepts/jobs_instances/#automatically-generated-labels-and-time-series

e.g. by using `up`, and comparing `scrape_series_limit` to `scrape_series_scraped`, you can see if the scrape failed, and see that it failed because the number of series exceeded the limit.

Can you enable debug logging in the collector? I think adding this should work. It will make the log include the reason why the scrape failed. ```yaml service: telemetry: logs:...

These are the other semantic conventions referenced: * service.name * service.namespace * service.instance.id * k8s.pod.name * k8s.pod.uid * k8s.container.name * k8s.node.name * k8s.replicaset.name * k8s.daemonset.name * k8s.statefulset.name * k8s.job.name *...

@TylerHelmuth this is no longer a breaking change. It unconditionally adds the new semconv, and adds a feature gate, `receiver.prometheusreceiver.RemoveLegacyResourceAttributes`, which removes the old semconv. Since it is disabled by...

Fixing presubmit: https://github.com/census-instrumentation/opencensus-go/pull/1288