Skip to content

Add known_methods property to .instrumentation.general.http.(client|server)#527

Open
trask wants to merge 1 commit intoopen-telemetry:mainfrom
trask:known_methods
Open

Add known_methods property to .instrumentation.general.http.(client|server)#527
trask wants to merge 1 commit intoopen-telemetry:mainfrom
trask:known_methods

Conversation

@trask
Copy link
Member

@trask trask commented Feb 5, 2026

@trask trask marked this pull request as ready for review February 5, 2026 19:38
@trask trask requested a review from a team as a code owner February 5, 2026 19:38
propertyOverrides: []
propertyOverrides:
- property: known_methods
status: not_implemented
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related to this PR per say, but its a bit odd for language implementations to report the status of entries in the .instrumentation/development block. The reality is that whether a particular property is implemented is very contextual, depending on what / if an auto instrumentation solution is used and the instrumentation in question.

I should probably update the language status tooling to skip types nested under .instrumentation/development.

"items": {
"type": "string"
},
"description": "Override the default list of known HTTP methods.\nThis is a full override of the default known methods, not a list of known methods in addition to the defaults.\nIf omitted, HTTP methods GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH are known.\n"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does case matter here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants