Process and process runtime resources

Status: Experimental

Process

type: process

Description: An operating system process.

Additional attribute requirements: At least one of the following sets of attributes is required:

• process.executable.name
• process.executable.path
• process.command
• process.command_line
• process.command_args

Between process.command_args and process.command_line, usually process.command_args should be preferred. On Windows and other systems where the native format of process commands is a single string, process.command_line can additionally (or instead) be used.

For backwards compatibility with older versions of this semantic convention, it is possible but deprecated to use an array as type for process.command_line. In that case it MUST be interpreted as if it was process.command_args.

Process runtimes

type: process.runtime

Description: The single (language) runtime instance which is monitored.

How to set these attributes for particular runtime kinds is described in the following subsections.

In addition to these attributes, telemetry.sdk.language can be used to determine the general kind of runtime used.

Erlang Runtimes

• process.runtime.name - The name of the Erlang VM being used, i.e., erlang:system_info(machine).
• process.runtime.version - The version of the runtime (ERTS - Erlang Runtime System), i.e., erlang:system_info(version).
• process.runtime.description - string | An additional description about the runtime made by combining the OTP version, i.e., erlang:system_info(otp_release), and ERTS version.

Example:

Go Runtimes

Go Runtimes should fill in the as follows:

• process.runtime.name - Fill in an interpretation of Go’s runtime.Compiler constant, according to the following rule: If the value is gc, fill in go. Otherwise, fill in the exact value of runtime.Compiler.

  This can be implemented with the following Go snippet:

  import "runtime"
  
  func getRuntimeName() string {
    if runtime.Compiler == "gc" {
      return "go"
    }
    return runtime.Compiler
  }
  

• process.runtime.version - Fill in the exact value returned by runtime.Version(), i.e. go1.17.

• process.runtime.description - Use of this field is not recommended.

Examples for some Go compilers/runtimes:

Java runtimes

Java instrumentation should fill in the values by copying from system properties.

• process.runtime.name - Fill in the value of java.runtime.name as is
• process.runtime.version - Fill in the value of java.runtime.version as is
• process.runtime.description - Fill in the values of java.vm.vendor, java.vm.name, java.vm.version in that order, separated by spaces.

Examples for some Java runtimes

JavaScript runtimes

JavaScript instrumentation should fill in the values by copying from built-in runtime constants.

• process.runtime.name:
  • When the runtime is Node.js, fill in the constant value nodejs.
  • When the runtime is Web Browser, fill in the constant value browser.
• process.runtime.version:
  • When the runtime is Node.js, fill in the value of process.versions.node.
  • When the runtime is Web Browser, fill in the value of navigator.userAgent.

Examples for some JavaScript runtimes

.NET Runtimes

TODO(https://github.com/open-telemetry/opentelemetry-dotnet/issues/1281): Confirm the contents here

Python Runtimes

Python instrumentation should fill in the values as follows:

• process.runtime.name - Fill in the value of sys.implementation.name

• process.runtime.version - Fill in the sys.implementation.version values separated by dots. Leave out the release level and serial if the release level equals final and the serial equals zero (leave out either both or none).

  This can be implemented with the following Python snippet:

  vinfo = sys.implementation.version
  result =  ".".join(map(
      str,
      vinfo[:3]
      if vinfo.releaselevel == "final" and not vinfo.serial
      else vinfo
  ))
  

• process.runtime.description - Fill in the value of sys.version as-is.

Examples for some Python runtimes:

Note that on Linux, there is an actual newline in the sys.version string, and the CPython string had a trailing space in the first line.

Pypy provided a CPython-compatible version in sys.implementation.version instead of the actual implementation version which is available in sys.version.

Ruby Runtimes

Ruby instrumentation should fill in the values by copying from built-in runtime constants.

• process.runtime.name - Fill in the value of RUBY_ENGINE as is
• process.runtime.version - Fill in the value of RUBY_VERSION as is
• process.runtime.description - Fill in the value of RUBY_DESCRIPTION as is

Examples for some Ruby runtimes