Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(pyroscope): allow slashes in application name #2172

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

marcsanmi
Copy link
Contributor

@marcsanmi marcsanmi commented Nov 27, 2024

PR Description

The change extends tag name validation to allow slashes, enabling hierarchical service naming patterns.

Which issue(s) this PR fixes

Closes #2158

Relates to:

Notes to the Reviewer

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Tests updated
  • Config converters updated

@marcsanmi marcsanmi force-pushed the marcsanmi/allow-service-name-slashes branch from 9657657 to 92c85ab Compare November 27, 2024 15:29
@marcsanmi marcsanmi marked this pull request as ready for review November 27, 2024 16:02
@marcsanmi marcsanmi requested review from a team as code owners November 27, 2024 16:02
@marcsanmi marcsanmi requested a review from aleks-p November 27, 2024 16:03
@marcsanmi marcsanmi force-pushed the marcsanmi/allow-service-name-slashes branch from 92c85ab to a2d40b9 Compare November 27, 2024 16:04
@marcsanmi marcsanmi changed the title fix(pyroscope): allow slashes in tag name fix(pyroscope): allow slashes in application name Nov 27, 2024
Copy link

@kolesnikovae kolesnikovae left a comment

Choose a reason for hiding this comment

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

LGTM

@marcsanmi marcsanmi requested a review from a team December 2, 2024 08:35
@marcsanmi marcsanmi merged commit 2b16ff0 into main Dec 2, 2024
18 checks passed
@marcsanmi marcsanmi deleted the marcsanmi/allow-service-name-slashes branch December 2, 2024 08:50
ptodev added a commit that referenced this pull request Dec 3, 2024
* Fixed an issue in the `otlp.exporter.prometheus` component (#2102)

* Fixed an issue in the `otlp.exporter.prometheus` component

* Fixed an issue in the `otlp.exporter.prometheus` component

* Fix potential deadlock in import statements (#2129)

* Fix potential deadlock in import statements

* change

* typo

* fix: race condition UI remotecfg (#2160)

* Refactor ui remtoecfg components to avoid race condition

* Fix accidental cast to pointer that should have been struct

* Update changelog

* fix: fully prevent panic in remotecfg ui (#2164)

* Fully prevent panic in remotecfg ui

* Address PR feedback

* Fix deadlock due to infinite retry (#2174)

* Fix deadlock due to infinite retry

* changelog

* Update ckit to fix memberlist logging issues (#2186)

* Upgrade ckit and changelog

* go mod tidy

* `loki.source.podlogs`: Fix issue which disables clustering unintentionally. (#2187)

* Fix issue which disables clustering unintentionally.

* prometheus.operator.*: allow setting informer_sync_timeout (#2161)

* prometheus.operator.*: allow setting informer_sync_timeout

* default to 1m

* docs

* fix(pyroscope): allow slashes in tag name (#2172)

* loki.source.podlogs: For clustering only take into account some labels (#2190)

* Only take into account some labels

* Reword docs

* fix: crash when updating import.http config (#2204)

* fix: crash when updating import.http config

* fix key/pattern logic for the attribute processor (#2124)

* fix: Update postgres exporter (#2019)

* Update postgres exporter

* Update changelog

* Use postgres exporter branch that implements exporter package

* Add TODO for future maintainers

* Update VERSION file

* Add missing changelog entry

* Fix pyroscope.write issues with pyroscope.receive_http (#2201)

* Fix pyroscope.write issues with pyroscope.receive_http

The nodejs Pyroscope SDK sends profiles with a `Connection: close` header.
This header was copied to the upstream request, causing connection churn
towards Pyroscope, which can be quite bad on the CPU when using TLS. Do not
copy the `Connection` header from the incoming request to fix this issue.

Additionally, `pyroscope.write` had a single `http.Client` used for
forwarding data from `pyroscope.receive_http`, which may not work if
multiple endpoints are configured with different options. To fix this,
store a `http.Client` for each endpoint.

---------

Co-authored-by: YusifAghalar <41161340+YusifAghalar@users.noreply.github.com>
Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com>
Co-authored-by: Sam DeHaan <sam.dehaan@grafana.com>
Co-authored-by: Craig Peterson <192540+captncraig@users.noreply.github.com>
Co-authored-by: Marc Sanmiquel <marcsanmiquel@gmail.com>
Co-authored-by: Sergei Nikolaev <kinolaev@gmail.com>
Co-authored-by: William Dumont <william.dumont@grafana.com>
Co-authored-by: Sam DeHaan <dehaansa@gmail.com>
Co-authored-by: Gergely Madarász <gergely.madarasz@tulip.co>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pyroscope: allowed service_name incosistent between pyroscope.scrape and pyroscope.receive_http
3 participants