Opentelemetry metrics release candidate

author ：Morgan McLean

OpenTelemetry The indicator function of can now be used as a candidate version , stay Java,.NET, also Python Use ！ This means that the specification 、API、SDK, And creation 、 Capture 、 Other components that handle and otherwise interact with metrics , Now have a complete OpenTelemetry Indicator feature set , And ready to use . These candidate versions will be officially released in the next few weeks .

Indicators 1.0 Versions include the following ：

• OpenTelemetry Language specific API Indicator functions included in , It provides language specific interfaces , Indicators can be created and operated , And associate metadata and attributes to each indicator . These are useful for ：
  • Developers of shared libraries distributed to end users , So that these end users can natively use OpenTelemetry Capture metrics from these libraries . for example ,gRPC Use these API For each... On a given service RPC Method generation delay 、 Throughput and error rate metrics .
  • Create and maintain web The developer of a service or client application , This allows them to generate custom metrics or interact with existing metrics . for example , An e-commerce company can use API To track purchases over time .
• Java、.NET、Python and JS（ Released next week ） OpenTelemetry SDK Indicator functions included in , They come from API Capture metrics and perform some processing . Indicator support for other languages is still under development . These are useful for ：
  • Developers of applications used by other organizations , Such as a database 、 Message queuing, etc , They will pass OTLP（ or Prometheus） Exposure indicators , So that their own end users can monitor the performance of these applications . These applications can be open source or closed source .
  • Application developers in technology organizations , They want to capture... In their applications OpenTelemetry API Generated metrics , These metrics can be generated by their own developers , They can also come from shared libraries that their applications depend on . These indicators can be obtained through OTLP export , Or through any other OpenTelemetry Exporter exports .
• The collector's support for metrics includes the collector from various data sources （ Such as host metrics or prepackaged applications ） Ability to capture metrics in . The collector also provides the ability to receive metrics from data sources using a variety of data protocols , For example, the original OpenTelemetry agreement （OTLP） And compatible OpenMetrics The agreement , for example Prometheus. It also supports configuration driven indicator processing and native OTLP、Prometheus And custom exporter , So that the observability indicators can be sent to the cloud and internal monitoring system of your choice . This feature set is very useful for ：
  • Anything that wants to get from its host （Linux virtual machine 、Windows、 virtual machine 、Kubernetes etc. ） Or prepackaged applications （ database 、 Message queuing, etc ） People who get indicators .
  • Any hope from OTLP（ from OpenTelemetry SDK、 Prepackaged applications, etc ）、Prometheus, Or someone who gets metrics from other existing sources .
  • Anything you want to deal with / People who modify indicators and indicator metadata obtained from these sources .
  • Anyone who wants to convert metrics from one format to another . for example , The collector can be accessed from OTLP and Prometheus Capture metrics in a mix of sources , And then use OTLP（ standards-of-use OpenTelemetry Semantic conventions ）、Prometheus Or any other exporter sends all this to a destination .
• complete OTLP Support , Efficient serialization and transfer of metrics between systems .
• The index part of the specification , It defines different types of indicators 、 Their shape 、 How to deal with them and semantic conventions . This is mainly for OpenTelemetry Contributors use , But also for the creation of indicators or metadata OpenTelemetry Users provide guidance .

All these functions are right OpenTelemetry Complements existing tracking support , Both signal types share the same metadata and semantic conventions . As of this release , The following languages have released candidate versions of the metrics ：

• Java
• .NET
• Python

JS The candidate version of is scheduled to be released next week , Over the next few months , There will be more language release indicator candidate versions . After we receive feedback from users , Each version will be officially released .

Getting started

If you've mixed it up OpenTelemetry API、SDK、 Agents and collectors , Then you can pass OpenTelemetry The workpiece is updated to the latest version to obtain the candidate version indicator function . We are currently updating the indicator capabilities for each artifact official OpenTelemetry file [1]. Examples and supplementary documentation are also added to the corresponding... For each artifact GitHub Warehouse .

OpenTelemetry Next step

When we're in 2019 Europe Kubecon Announce OpenTelemetry The core commitment of , Distributed tracking and metrics are two parts of it . With the widespread availability of indicators , We have produced the functionality we originally intended to create , This means that we can shift our focus to further investing in the robustness and ease of use of each component 、OpenTelemetry Number of data sources from which telemetry data can be captured （ adopt OpenTelemetry API、OTLP Or in any other way ）, And new functions and signal types .

The log is the most obvious , We are moving at full speed . I look forward to hearing more about our progress in journaling in the past year （ Logs already have a stable data model and OTLP Support ）, Anyone who is interested in this field is welcome to join our Sunday blog SIG Conference . In addition to the log , Major new projects also include formalizing and implementing client-side tools to , And the eBPF The investigation of . With the completion of the indicators , We can also turn our attention to more signal types .

Reference material

[1]

official OpenTelemetry file : https://opentelemetry.io/docs/

---

CNCF (Cloud Native Computing Foundation) Founded on 2015 year 12 month , Affiliated to the Linux Foundation, It's a non-profit organization .

CNCF（ Cloud native Computing Foundation ） Committed to fostering and maintaining a vendor neutral open source ecosystem , To promote cloud native technology . By democratizing the most cutting-edge model , Let these innovations be used by the public .