This release comes with a couple of big changes (plus bug fixes):
Base URL
This allows you to provision pyroscope under some subdirectory behind a reverse proxy (e.g https://internal-portal.example.com/pyroscope). Technically this is more of a bug fix, as we already had support for this. But the old implementation didn't work in some cases, and thanks to help from community members @jonathanza, @dannykopping and @geoah we were able to debug and refactor it to make this feature work much more reliably. BaseURL can now be specified as a full URL (https://internal-portal.example.com/pyroscope) or as just a path to pyroscope instance (/pyroscope).
You can pass it as an environment variable (PYROSCOPE_BASE_URL=/pyroscope) or a flag (-base-url /pyroscope) or as an entry the config file (base-url: "/pyroscope").
New Sidebar
Although a purely cosmetic change, this gets us closer to the big release of adhoc mode. Currently adhoc mode is hidden under a feature-flag, but you can test it out if you run pyroscope server with PYROSCOPE_ENABLE_EXPERIMENTAL_ADHOC_UI=true environment variable. Do you like the new sidebar? Let us know in our slack.
Installation
For instructions on how to install pyroscope visit our Getting Started guide.
Source code
Linux binary builds
pyroscope-0.5.0-linux-amd64.tar.gz
pyroscope-0.5.0-linux-arm64.tar.gz
Ubuntu / Debian (.deb) builds
pyroscope_0.5.0_amd64.deb
pyroscope_0.5.0_arm64.deb
RHEL / CentOS (.rpm) builds
pyroscope-0.5.0-1-x86_64.rpm
pyroscope-0.5.0-1-aarch64.rpm
Windows (.msi) builds
pyroscope_agent_0.5.0_amd64.msi
Changes:
Bug Fixes
- assets handling when using base-url argument (#611) (97a6002)
- avoid converting args to double dash and disable flag parsing for adhoc. (#609) (f41906d)
- integrations: start upstream in clib. (#602) (0be03c3)