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

[pull] main from pyroscope-io:main #12

Open
wants to merge 4,176 commits into
base: main
Choose a base branch
from
Open

[pull] main from pyroscope-io:main #12

wants to merge 4,176 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Jun 23, 2021

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.1)

Can you help keep this open source service alive? 💖 Please sponsor : )

simonswine and others added 7 commits August 21, 2024 15:25
…3428)

* feat: Embed a grafana instance into pyroscope

This provides an optional target `embedded-grafana` to
download/configure/run a dedicated Grafana instance with Explore
Profiles deployed.

This is meant not to be used as production, but useful to quickly
discover profiles.

After this PR merges a user can run this:

```
$ docker run -p 4040:4040 -p 4041:4041 grafana/pyroscope --target all,embedded-grafana
```

And on localhost:4040 there will the classic pyroscope and on :4041,
there will be Grafana with Explore Profiles.

* Update explore profiles to v0.1.5

* Update contribution guide to mention embedded Grafana
I think it is a nice to have this appreciation, but we haven't updated
in a while, as the nodejs of the old tools no longer maintained.

Just threw some go together quickly.
* Push is using wrong credentials

* Also skip ci on the subsequent commit
This also updates grafana/eslint for compatability with node 20
* Newline after contributors

* Use the PAT for pushing changes correctly

Using action/checkout with token is broken for our usecase, implemented
a workaround from:

actions/checkout#664 (comment)
pyroscopebot and others added 30 commits January 5, 2025 00:27
* feat(v2): add metadata label query interface

* implement clients

* improve error handling

* implement metadata label query service

* implement metadata label querier

* test and fix metadata label querier

* refactor metadata label compaction

* introduce block/metadata package

* avoid sending stubs in GetTenantStats

* document metadata entry
* Restructure Pyroscope documentation and share content

* Fix typo

* Fix heading match for profile types

* Restructure for configure server

* Apply suggestions from code review

Co-authored-by: Taylor C <[email protected]>

* Apply suggestions from code review

* Apply suggestions from code review

Co-authored-by: Aleksandar Petrov <[email protected]>

* Apply suggestions from code review

Co-authored-by: Aleksandar Petrov <[email protected]>

---------

Co-authored-by: Taylor C <[email protected]>
Co-authored-by: Aleksandar Petrov <[email protected]>
* feat: configurable symbols partitioning

* fix fixtures

* add CLI docs
* Added bucket-lookup-type field to s3 config

* Review fixes: validation & deprecation warning

* Update reference docs

* Formatted code

---------

Co-authored-by: Christian Simon <[email protected]>
* Update `make docs` procedure

* Update `make docs` procedure

---------

Co-authored-by: grafanabot <[email protected]>
We seem to have not linked up the validation for a few components.
* docs: Add v1.12 release notes

* Also add documentation in changelog
In order to be able to parse the labelset in the classic ingest
endpoints in Grafana Alloy, I am refactoring this bit of the OG code
into the api package so I can use this within Grafana Alloy.
* fix(otel): compressed metric

* fix TestDifferentServiceNames
* Add a metastore client admin test page

* Improve page

* Workaround for the mismatched server identifiers

* Improve logging

* Fix error on startup

* Fix test

* Switch metastore client retries to dskit backoff
* chore(v2): improve error handling in compaction-worker

* chore(v2): add some more safety checks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.