parca: some profiles fail scraping
conprof-0 conprof level=debug ts=2020-04-28T04:21:13.165040571Z caller=scrape.go:370 component=scrape-manager scrape_pool=conprof msg="scraping profile" url=http://10.200.2.38:8080/debug/pprof/trace
conprof-0 conprof level=debug ts=2020-04-28T04:21:14.18123509Z caller=scrape.go:505 component=scrape-manager scrape_pool=conprof target=http://10.200.2.38:8080/debug/pprof/trace msg="Scrape failed" err="failed to parse target's pprof profile: parsing profile: unrecognized profile format"
Same for cmdline profile:
conprof-0 conprof level=debug ts=2020-04-28T04:23:02.305811774Z caller=scrape.go:370 component=scrape-manager scrape_pool=conprof msg="scraping profile" url=http://10.200.0.177:8080/debug/pprof/cmdline
conprof-0 conprof level=debug ts=2020-04-28T04:23:02.310718078Z caller=scrape.go:505 component=scrape-manager scrape_pool=conprof target=http://10.200.0.177:8080/debug/pprof/cmdline msg="Scrape failed" err="failed to parse target's pprof profile: parsing profile: unrecognized profile format"
Might be a consequence of running on arm
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (7 by maintainers)
Commits related to this issue
- Merge pull request #46 from parca-dev/split-pprof *: Split pprof into individual profiles by sample index — committed to parca-dev/parca by brancz 3 years ago
As Add Profile Type got merged, we can now scrape traces, so closing this. I’ve opened a seperate issue for UI https://github.com/conprof/conprof/issues/61
I think I like the ergonomics of the profile type/name being the entrypiont for querying. I think we’re going to have to adjust the query language/API for this slightly.
In an attempt to not duplicate work, I opened a WIP for the remote read work I had laying around as that also did the internal manual vendoring: https://github.com/conprof/conprof/pull/54