From cf9452f3d9acb227a2a105d1e1d0489445c8e001 Mon Sep 17 00:00:00 2001 From: Dmitry Filimonov Date: Fri, 27 Oct 2023 11:52:03 -0700 Subject: [PATCH] pyroscope: fixes wrong memory profiling path See this conversation https://raintank-corp.slack.com/archives/C03NCLB4GG7/p1698431277146729 for more context --- docs/sources/flow/reference/components/pyroscope.scrape.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/flow/reference/components/pyroscope.scrape.md b/docs/sources/flow/reference/components/pyroscope.scrape.md index c8609a1d5148..37a90ef89cc8 100644 --- a/docs/sources/flow/reference/components/pyroscope.scrape.md +++ b/docs/sources/flow/reference/components/pyroscope.scrape.md @@ -156,7 +156,7 @@ It accepts the following arguments: Name | Type | Description | Default | Required ---- | ---- | ----------- | ------- | -------- `enabled` | `boolean` | Enable this profile type to be scraped. | `true` | no -`path` | `string` | The path to the profile type on the target. | `"/debug/pprof/memory"` | no +`path` | `string` | The path to the profile type on the target. | `"/debug/pprof/allocs"` | no `delta` | `boolean` | Whether to scrape the profile as a delta. | `false` | no When the `delta` argument is `true`, a `seconds` query parameter is