Cherry-pick #19125 to 7.x: Add support for cloudfoundry logs collection using consumer v1 API #19212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #19125 to 7.x branch. Original message:
What does this PR do?
Add support for collection of logs from cloud foundry using consumer v1 API. v1 API uses doppler/trafficcontrol to get events from the firehose, v2 API uses the reverse log proxy (RLP).
v2 API is still supported, and can be selected by adding
version: v2
to the configuration, v1 is used by default as is in principle more reliable.version
is ignored by now by Metricbeat, that continues usingv2
. Support forv1
in Metricbeat will be implemented in a future change.This change adds some additional dependencies for the doppler consumer (noaa).
Why is it important?
We already support the v2 API, but we saw that this API is not reliable enough (see #18202).
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
version
option:version
option (what would usev1
)version: v1
.version: v2
.version
it should fail to start.Related issues