THIS FORUM IS NO LONGER ACTIVE. Join us on CNCF Slack: https://cloud-native.slack.com/archives/CJFCJHG4Q.
I'm using JaegerExporter for .Net and all my telemetry is reporting as "OpenTelemetry Exporter" as you may see on this picture on jaeger UI.
What should be set on the telemetry reports or the exporter in order to have the proper service name there?
Thanks!
Just found it, thanks!
Hello,
I was curious as per the standard, are labels meant to be per value or per metric?
As a concrete example, I want all HTTP requests sent from an application to be exposed as two metrics - requests count(as Counter) and latency(as ValueRecorder). The application is sending requests to a verity of 3rd party systems, I want the metric to contain a way to group the request based on DNS name, response code, path and others. Is labels the correct abstraction to allow such grouping or there is something else, better suited?
P.S If this is not the correct place to ask this question, could somebody point me to the correct one?
The @opentelemetry Metrics Workshop happens tomorrow at 9:30 PST at https://zoom.us/j/8203130519
9:30 - 9:45am PST: Opening remarks, organization of the day, how we got here, and the many streams of work. We have an API, language SDKs, a Protocol, a Collector, Receivers, Exporters, Semantic Conventions, and a connection to Tracing [organizer: OTel Committee]
9:45-10:15am PST: Community building: @opentelemetry has first-class @OpenMetricsIO support, and @PrometheusIO users are first-class users. These projects are meant to get along, and committed to it. [organizer: Alolita Sharma]
10:15 - 11:00am PST: @opentelemetry Collector deployment models (e.g., Daemonset vs. Statefulset), Agents, Sidecars, and first-class support for Prometheus Remote-Write [organizer: Jaana Dogan]
11:30 - 12:15pm The Metrics API and Data Model, how we integrated the @opencensusio feature set (Tracing and Metrics, combined!) with the @OpenMetricsIO and StatsD data models. Presenting the six @opentelemetry metric instruments [organizer: Bogdan Drutu]
12:15 - 13:00pm Histograms! How we’ll support high-resolution and variable-boundary histograms and the connection to sampling metric events [organizers: Josh MacDonald, Michael Gerstenhaber]
13:30 - 15:00pm Questions and answers
Hello everyone I had a problem when installing OTEL with istio
I had set b3-propagator as here https://www.npmjs.com/package/@opentelemetry/propagator-b3
and it works but I get a warning in all my spans " invalid parent span IDs "?
Hi, I have trouble setting up prometheus kubelet/node scraping with otel-collector. I have this config:
- job_name: k8s/kubelet
scheme: https
tls_config:
ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
insecure_skip_verify: true
bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
kubernetes_sd_configs:
- role: node
relabel_configs:
- action: labelmap
regex: __meta_kubernetes_node_label_(.+)
This is what I see in logs:
2021-01-21T21:43:21.433Z warn internal/metricsbuilder.go:104 Failed to scrape Prometheus endpoint {"component_kind": "receiver", "component_type": "prometheus", "component_name": "prometheus", "scrape_timestamp": 1611265401788, "target_labels": "map[beta_kubernetes_io_arch:amd64 beta_kubernetes_io_instance_type:k3s beta_kubernetes_io_os:linux instance:k3d-dev-server-0 job:k8s/kubelet k3s_io_hostname:k3d-dev-server-0 k3s_io_internal_ip:172.20.0.3 kubernetes_io_arch:amd64 kubernetes_io_hostname:k3d-dev-server-0 kubernetes_io_os:linux node_kubernetes_io_instance_type:k3s node_role_kubernetes_io_master:true]"}
Hi, I have trouble setting up prometheus kubelet/node scraping with otel-collector. I have this config:
- job_name: k8s/kubelet scheme: https tls_config: ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt insecure_skip_verify: true bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token kubernetes_sd_configs: - role: node relabel_configs: - action: labelmap regex: __meta_kubernetes_node_label_(.+)
This is what I see in logs:
2021-01-21T21:43:21.433Z warn internal/metricsbuilder.go:104 Failed to scrape Prometheus endpoint {"component_kind": "receiver", "component_type": "prometheus", "component_name": "prometheus", "scrape_timestamp": 1611265401788, "target_labels": "map[beta_kubernetes_io_arch:amd64 beta_kubernetes_io_instance_type:k3s beta_kubernetes_io_os:linux instance:k3d-dev-server-0 job:k8s/kubelet k3s_io_hostname:k3d-dev-server-0 k3s_io_internal_ip:172.20.0.3 kubernetes_io_arch:amd64 kubernetes_io_hostname:k3d-dev-server-0 kubernetes_io_os:linux node_kubernetes_io_instance_type:k3s node_role_kubernetes_io_master:true]"}
Had to enable debug logging to see that the error is actually forbidden, my role was missing the node endpoint
FYI all, I've updated all Zoom meetings to require a password: 77777. This is now embedded into our calendar and meeting notes links, and is referenced on the community GitHub README.md.
We had to do this after one of the meetings got Zoom bombed! If you access the meetings via the calendar, you won't notice any changes.