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

chore(phlare/pyroscope): rename phlare to pyroscope #4013

Merged
merged 3 commits into from
May 31, 2023

Conversation

korniltsev
Copy link
Contributor

@korniltsev korniltsev commented May 30, 2023

PR Description

As part of phlare and pyroscope merging we are removing references to phlare, keeping it pyroscope.

  • renamed component/phlare package to component/pyroscope
  • renamed documentation

Which issue(s) this PR fixes

https://github.com/grafana/pyroscope-squad/issues/20

Notes to the Reviewer

Should we update upgrade guide?

PR Checklist

  • CHANGELOG updated
  • Documentation added
  • Tests updated

@korniltsev korniltsev requested review from a team and clayton-cornell as code owners May 30, 2023 14:44
Copy link
Member

@rfratto rfratto left a comment

Choose a reason for hiding this comment

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

LGTM but I'd like to check with @cyriltovena that we're ready for the components to be renamed.

@@ -19,6 +19,8 @@ Main (unreleased)
- Upgrade the embedded windows_exporter to commit 79781c6. (@jkroepke)

- Prometheus exporters in Flow mode now set the `instance` label to a value similar to the one they used to have in Static mode (<hostname> by default, customized by some integrations). (@jcreixell)

- `phlare.scrape` and `phlare.write` have been renamed to `pyroscope.scrape` and `pyroscope.scrape`. (@korniltsev)
Copy link
Member

Choose a reason for hiding this comment

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

This would be a breaking change, so we'd need to list it as such in a breaking change category listed before new features:

https://github.com/grafana/agent/blob/main/docs/developer/contributing.md#updating-the-changelog

Copy link
Member

Choose a reason for hiding this comment

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

(Breaking changes also would need to be documented in the upgrade guide: https://github.com/grafana/agent/blob/main/docs/sources/flow/upgrade-guide.md)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This item seems to be under "Breaking changes" section, so it is everything correct here? right?

I will update upgrade guide

Copy link
Member

Choose a reason for hiding this comment

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

This item seems to be under "Breaking changes" section, so it is everything correct here? right?

Yes, sorry, I got confused by some of the other items 🤦 The only thing to do here is to update the upgrade guide.

Copy link
Contributor

@clayton-cornell clayton-cornell left a comment

Choose a reason for hiding this comment

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

From the docs side it looks OK.

Copy link
Member

@rfratto rfratto left a comment

Choose a reason for hiding this comment

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

LGTM, thank you!

@rfratto rfratto merged commit 6675ff5 into grafana:main May 31, 2023
@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Feb 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants