Skip to content

S3 instrumentation does not contain s3 in destination.service.resource name #2849

@AlexanderWert

Description

@AlexanderWert

All backends should have a name pattern of type/name (where name is recommended but not mandatory).
The current S3 instrumentation sets the destination.service.recourse.name field to the bucket name (without the s3/ prefix).

The consequence is that in the dependencies view in the UI it's not clear at all what type of service it is:
image

Note: This potentially requires a spec change and changes in other agents as well.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions