OpenTelemetry plugin, support for resource attributes

[viktorgagaleski]

Hello Artillery team,

We are evaluating Artillery in combination with Playwrigth in order to do UI performance testing. The PoC is going great and I am really positively surprised on what it can be achieved, especially if teams already have Playwight setup with pages, components etc.

We also want to leverage the oTel plugin and send the results of the runs to our oTel backbone. We managed to do this successfully but there are some issues that we observed. Our oTel collector expects the attributes to be inside of the resources -> attributes child, which at the moment doesn't seem to happen. All of the attributes are added in the metric -> attributes. We need this as that is how we filter our logs and metrics, and then decide on retention period etc.

This is the config that we use:

  plugins:
    publish-metrics:
      - type: open-telemetry
        serviceName: artillery-performance
        metrics:
          exporter: 'otlp-grpc'
          endpoint: '<URL>'
          attributes:
            service.namespace: 'test'
            team: 'e2e'

oTel example:

  "resourceMetrics": [
    {
      "resource": {
        "attributes": [
          {
            "key": "service.name",
            "value": {
              "stringValue": "my.service"
            }
          }
        ]
      },
      "scopeMetrics": [
        {
          "scope": {
            "name": "my.library",
            "version": "1.0.0",
            "attributes": [
              {
                "key": "my.scope.attribute",
                "value": {
                  "stringValue": "some scope attribute"
                }
              }
            ]
          },
          "metrics": [
            {
              "name": "my.counter",
              "unit": "1",
              "description": "I'm a Counter",
              "sum": {
                "aggregationTemporality": 1,
                "isMonotonic": true,
                "dataPoints": [
                  {
                    "asDouble": 5,
                    "startTimeUnixNano": 1544712660300000000,
                    "timeUnixNano": 1544712660300000000,
                    "attributes": [
                      {
                        "key": "my.counter.attr",
                        "value": {
                          "stringValue": "some value"
                        }
                      }
                    ]
                  }
                ]
              }
            }
          ]
        }
      ]
    }
  ]
}

We would like to add attributes here:

"resource": { "attributes": [ { "key": "service.name", "value": { "stringValue": "my.service" } } ] },

Is there any way on how we can add resource attributes via the yml configuration?

[hassy]

hi @viktorgagaleski 👋 will need to check, it might need a change to the OTel integration, but shouldn't be too difficult.

very happy to hear the PoC is going well!

[viktorgagaleski]

Hello @hassy, yes this will help for our case as those are the attributes that we would like to update. The attributes for metric and traces will remain as well right? I think it is good for Artillery to be flexible and allow both :)
Thanks!

[hassy]

@viktorgagaleski Yep, you'd still be able to set metric/trace-only attributes. This new setting would be used only to add Resource-level attributes.

[hassy]

PR here: #3335 will be released as part of the next Artillery release

[viktorgagaleski]

Thanks a lot, this is great improvement and will definitely help us a lot with our Artillery adoption! Kudos for the fast response as well 🥇

[hassy]

thanks for the suggestion @viktorgagaleski! turned out to be very easy to add and will benefit everyone sending Artillery metrics to an OTel backend!