High resolution histograms by @_codesome is by far my most anticipated talk at #KubeConEU
Really mindblowing how the precision improved while maintaining good resource performance 🙂
I am speaking at @KubeCon_ EU this year. Majority of it is filled with demos📊📈👀 See you in-person or virtually!
Save this to your schedule here: sched.co/ytqF
[#KUBECON NEWS] #CNCF’s #KubeCon + #CloudNativeCon scholarship program will be named the Dan Kohn Diversity Scholarship.
Dan believed in a diverse community, and thanks to his leadership, CNCF has been able to offer 1,5k+ scholarships to date.
cncf.io/blog/2021/10/1…
Do you know that @OpenMetricsIO Exemplars support in Remote Write protocol (+ storage improvements) just got merged and will be released in @PrometheusIO v2.27.0 ?!
This is so exciting! 🚀💪🏾💜
Kudos to @CallumStyan and all reviewers to make this happen!
github.com/prometheus/pro…
Exemplars are a way to jump from metrics and logs to traces via an ID, and they make Grafana Tempo's high-scale distributed tracing so powerful. On the blog, @TwitchiH explains how they work and why they're part of cloud native observability at scale: grafana.com/blog/2021/03/3…
@MetricsVictoria Timestamps should be clear but it's impossible to give an exhaustive list here. All specifcations and reference code are available.
If your design choice is to neither follow Prometheus exposition format 0.0.4 nor OpenMetrics, please make that clear in your documentation.
@OpenMetricsIO We didn't encounter real-world case where this could result in incorrect parsing of Prometheus or OpenMetrics exposition format. It would be great if such case could be shared here.
VictoriaMetrics v1.48.0 has been released! It supports Prometheus-compatible Netflix Eureka service discovery aka eureka_sd_config among other new features. It also supports parsing OpenMetrics format.
github.com/VictoriaMetric…#eureka#prometheus#openmetrics
@MetricsVictoria Prometheus exposition format 0.0.4 and OpenMetrics are two closely related but different wire formats. You have one parser for both, which ends up parsing both incorrectly.
@OpenMetricsIO VictoriaMetrics v1.48.0 fixes parsing for OpenMetrics format - see bug fixes section at github.com/VictoriaMetric… .
As for content-type negotiation, it would be great to see practical cases when currently used negotiation could lead to bugs.
The backfilling tool for @PrometheusIO was just merged upstream as a part of promtool! It takes input in @OpenMetricsIO format. Nice work @atibhi_a!
You can either build it off of master or wait for v2.24.0. Docs coming soon.