Skip to content

Provide guidance for consistent instrumentation name #1035

Open
@codeboten

Description

@codeboten

Currently just about every instrumentation library uses __name__ as its instrumentation name. It would be good to provide guidance in the contributing documentation around what parameter should be used here.

Are we recommending a single name for all the modules/classes in an instrumentation or are we ok with different instrumentation names for different modules within the same instrumentation library?

This is to clarify: #1012 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions