Closed ethercrow closed 2 years ago
Thank you for opening the issue @ethercrow!
Pyroscope inherited almost all scraping features of Prometheus, and is almost 100% compatible with the Prometheus configuration (please notice that we use kebab-yaml-style instead of snake_case).
The following configuration should do the trick:
---
scrape-configs:
- job-name: testing
scheme: https
authorization:
type: Bearer
credentials: <bearer-token>
static-configs:
- application: acme
targets:
- acme-service
Also, the secret can be read from a file specified in the authorization.credentials-file
parameter.
Thank you so much, works great!
For the curious people who found this issue (probably including myself from the future), here's my current config:
Makefile:
.PHONY: pyroscope
pyroscope:
generate-acme-token > token.tmp
pyroscope server --config pyroscope.yml
pyroscope.yml:
---
log-level: debug
scrape-configs:
- job-name: prod
scheme: https
authorization:
type: Bearer
credentials-file: token.tmp
static-configs:
- application: acme
targets:
- "acme-service:443"
I'm able to get pprof data by doing
Is it possible to configure pyroscope to also pass this header?