Skip to content

fix(tracing): allow 256 chars in path tag#6492

Merged
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
douglas-reid:trace-path-fix
Apr 6, 2019
Merged

fix(tracing): allow 256 chars in path tag#6492
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
douglas-reid:trace-path-fix

Conversation

@douglas-reid
Copy link
Contributor

Description:

Increases the max_path_length for the :path tag in tracing to 256. This returns the length to the capacity that was supported before #444 . The issue of truncating the path has been raised in a few places recently, most notably in: istio/istio#12561.

I inquired as to the reasoning behind the switch to 128 from 256, but did not receive an answer. If there are valid reasons to keep 128, I would appreciate feedback there.

Risk Level: Low
Testing: Unit testing
Docs Changes: N/A
Release Notes: N/A

cc: @Stono @objectiser

Signed-off-by: Douglas Reid douglas-reid@users.noreply.github.com

Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>
@mattklein123 mattklein123 self-assigned this Apr 5, 2019
Copy link
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

I don't recall the history here but seems fine. @objectiser any objections?

@objectiser
Copy link
Contributor

No objections

@lambdai
Copy link
Contributor

lambdai commented Apr 5, 2019

As you are changing this code, could you change to constexpr? Theoretically it could enable optimization when accessing the value.

@mattklein123
Copy link
Member

As you are changing this code, could you change to constexpr? Theoretically it could enable optimization when accessing the value.

I'm pretty sure the optimizer will do the same thing either way.

@mattklein123 mattklein123 merged commit c398e4e into envoyproxy:master Apr 6, 2019
mpuncel added a commit to mpuncel/envoy that referenced this pull request Apr 8, 2019
* master: (137 commits)
  test: router upstream log to v2 config stubs (envoyproxy#6499)
  remove idle timeout validation (envoyproxy#6500)
  build: Change namespace of chromium_url. (envoyproxy#6506)
  coverage: exclude chromium_url (envoyproxy#6498)
  fix(tracing): allow 256 chars in path tag (envoyproxy#6492)
  Common: Introduce StopAllIteration filter status for decoding and encoding filters (envoyproxy#5954)
  build: update PGV url (envoyproxy#6495)
  subset lb: avoid partitioning host lists on worker threads (envoyproxy#6302)
  ci: Make envoy_select_quiche no-op. (envoyproxy#6393)
  watcher: notify when watched files are modified (envoyproxy#6215)
  stat: Add counterFromStatName(), gaugeFromStatName(), and histogramFromStatName() (envoyproxy#6475)
  bump to 1.11.0-dev (envoyproxy#6490)
  release: bump to 1.10.0 (envoyproxy#6489)
  hcm: path normalization. (#1)
  build: import manually minified Chrome URL lib. (envoyproxy#3)
  codec: reject embedded NUL in headers. (envoyproxy#2)
  Added veryfication if path contains query params and add them to path header (envoyproxy#6466)
  redis: basic integration test for redis_proxy (envoyproxy#6450)
  stats: report sample count as an integer to prevent loss of precision (envoyproxy#6274)
  Added VHDS protobuf message and updated RouteConfig to include it. (envoyproxy#6418)
  ...

Signed-off-by: Michael Puncel <mpuncel@squareup.com>
@douglas-reid douglas-reid deleted the trace-path-fix branch April 19, 2021 22:53
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.

4 participants