allow to use hash and convert on attribute values (also if retrieved from env var)

[cforce]

Component(s)

processor/attributes

Is your feature request related to a problem? Please describe.

1.) I read and env var as attribute value and want to apply the attribute processor hash or convert method on it.
2.) I want to apply hash/convert on value(env var ) and use this new value inside a array element value of an attribute value

Describe the solution you'd like

1.)

  attributes:
    actions:
      - key: "env"
        value: "${env:DEVICEID}" 
        action: hash,upsert

2.) ${attribute:deviceid} allows to read data from attribute's namespace (even if converted or hased before) and reuse it in any substring of another value

  attributes:
    actions:
      - key: "deviceid"
        value: "${env:DEVICEID}" 
        action: hash
      - key: tags
         value: ["deviceid:${attribute:deviceid}", xxx:YYYY]
         action: upsert

Describe alternatives you've considered

None. Open for alternatives ideas

Additional context

No response

[github-actions]

Pinging code owners:

• processor/attributes: @boostchicken

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[crobert-1]

Hello @cforce, apologies for the delayed response. I'm a bit unsure what your specific request is. I believe step 1 is already possible, so is your request simply to be able to add a key:value pair to an attribute whose type is a list? Am I missing something?

[cforce]

I want to hash the attribute deviceid and then use the hashed attribute value of deviceid inline in another attribute tags as array element

 attributes:
    actions:
      - key: "deviceid"
        value: "${env:DEVICEID}" 
        action: hash
      - key: tags
         value: ["deviceid:${attribute:deviceid}", xxx:YYYY]
         action: upsert

[crobert-1]

You can do this using the transform processor. If you're doing this on metrics you can use the datapoint context to have access to attributes (this works for traces and logs too, you just have to use the right context). The processor uses OTTL which has a hash function. You could then use an OTTL function like set or concat to add the value to your preferred destination. More information on those functions can be found here.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• processor/attributes: @boostchicken

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.