You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[receiver/prometheus] Add fallback_scrape_protocol when using target allocator (open-telemetry#39672)
This applies a similar fix as 72b834b,
when using TargetAllocator.
#### Description
For the same reason as we already add a `fallback_scrape_protocol` to
the config, this PR add the same behavior when using the Target
Allocator.
It's important for me, as even the `fallbackScrapeProtocol` from the
Prometheus CRD is ignored (I guess it's because the allocator advertise
itself as version 2.55.1, which does not support (nor require)
`fallback_scrape_protocol`).
Maybe it's a change that should be done on the target-allocator side,
but I kind of like the symmetry with what we're already doing with
provided configuration.
#### Link to tracking issue
Same issue as open-telemetry#37902, but when using a target allocator
---------
Signed-off-by: MATILLAT Quentin <[email protected]>
Co-authored-by: George Krajcsovits <[email protected]>
Co-authored-by: Arthur Silva Sens <[email protected]>
0 commit comments