Cherry-pick #19125 to 7.x: Add support for cloudfoundry logs collection using consumer v1 API#19212
Conversation
…lastic#19125) 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. (cherry picked from commit 3ebceec)
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
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: v2to the configuration, v1 is used by default as is in principle more reliable.versionis ignored by now by Metricbeat, that continues usingv2. Support forv1in 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.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
versionoption:versionoption (what would usev1)version: v1.version: v2.versionit should fail to start.Related issues