Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-18290

Unify and add more attributes for OpenTelemetry signals

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • 29.0.0.Final
    • Micrometer, OpenTelemetry
    • None
    • ---
    • ---

    Description

      Currently, WildFly's support for configuring instance-wide attributes (e.g. service name and instance ID) for OpenTelemetry signals in the WildFly config file is very limited:

      • The opentelemetry subsystem, which deals with traces, allows the service name to be set, but nothing else.
      • The micrometer subsystem, which deals with metrics, doesn't allow anything to be set.

      It would be helpful if:

      • The instance ID (service.instance.id in OTel's Resource Semantic Conventions) could be set. IMO it should default to jboss.node.name if not explicitly set.
      • Arbitrary attributes could be set. I don't have an exact use case in mind, but the flexibility could be useful.
      • All of these attributes could be set in one place, so they are guaranteed to be consistent across all types of signals.

      Attachments

        Activity

          People

            jaslee@redhat.com Jason Lee
            rdicroce Richard DiCroce (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: