torn about adopting something from a “competing” product Especially traditional vendor prefer to support official standards Richard Hartmann, RichiH@{freenode,OFTC,IRCnet}, richih@{fosdem,debian,richih} RFC currently blocked on me finding time Prometheus: experimental support since 2.5.0 Python client library: experimental support since 0.4.0 Test your own OM output: robustperception.io/checking-o @TwitchiH OpenMetrics Introduction Quick intro OpenMetrics Outro Plans Next steps Full OpenMetrics support in Prometheus, InfluxDB, OpenCensus, M3DB, etc Spreading the word CNCF sandbox to incubating Richard

authorization currently need to be handled via reverse proxies We will be changing Prometheus to support security out-of-the-box Richard Hartmann & Frederic Branczyk @TwitchiH & @fredbrancz Prometheus are writing code in Prometheus and the Python client library https://github.com/OpenObservability/OpenMetrics Prometheus 2.5 has experimental OpenMetrics support Richard Hartmann & Frederic Branczyk event Especially useful if you emit one trace id per histogram bucket Some integrations already support this concept, e.g. OpenCensus Ingestors are free to discard this optional data, e.g. Prometheus

data sources Modern UI Allows for complex data manipulation and visualization Native Prometheus support New feature: Interactive exploration of Prometheus data Richard Hartmann & Frederic Branczyk @TwitchiH