Skip to content

elasticapm/utils: match the specs better in build_name_with_http_meth…#2605

Draft
xrmx wants to merge 1 commit intoelastic:mainfrom
xrmx:review-build_name_with_http_method_prefix
Draft

elasticapm/utils: match the specs better in build_name_with_http_meth…#2605
xrmx wants to merge 1 commit intoelastic:mainfrom
xrmx:review-build_name_with_http_method_prefix

Conversation

@xrmx
Copy link
Copy Markdown
Member

@xrmx xrmx commented Apr 10, 2026

…od_prefix

In case the route name is not available we should use unknown route as route name.
While at it handle the case where the request does not have a method attribute. Mostly theorical since the current users, flask and django, requests have it.

Specs:
https://github.com/elastic/apm/blob/main/specs/agents/tracing-instrumentation-http.md

What does this pull request do?

Related issues

Closes #ISSUE

…od_prefix

In case the route name is not available we should use `unknown route` as
route name.
While at it handle the case where the request does not have a method
attribute. Mostly theorical since the current users, flask and django, requests have it.

Specs:
https://github.com/elastic/apm/blob/main/specs/agents/tracing-instrumentation-http.md
@github-actions
Copy link
Copy Markdown

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant