We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While parca is mostly configured like prometheus, I could not find documentation about profiling_config.
This was needed to configure Parca for prometheus' prombench, which requires prefixes.
scrape_configs: - job_name: "pr" scrape_interval: "3s" scrape_timeout: "2s" scheme: https profiling_config: pprof_config: memory_total: enabled: true path: /10543/prometheus-pr/debug/pprof/allocs block_total: enabled: true path: /10543/prometheus-pr/debug/pprof/block goroutine_total: enabled: true path: /10543/prometheus-pr/debug/pprof/goroutine mutex_total: enabled: true path: /10543/prometheus-pr/debug/pprof/mutex process_cpu: enabled: true path: /10543/prometheus-pr/debug/pprof/profile delta: true tls_config: insecure_skip_verify: true static_configs: - targets: [ 'prombench.prometheus.io' ]
The text was updated successfully, but these errors were encountered:
Can I take this up?
Sorry, something went wrong.
Yes, totally. Go for it! ☺️
Some work has been done in parca-dev/docs#140, going to close in favor of parca-dev/docs#137
No branches or pull requests
While parca is mostly configured like prometheus, I could not find documentation about profiling_config.
This was needed to configure Parca for prometheus' prombench, which requires prefixes.
The text was updated successfully, but these errors were encountered: