Add support for cloudfoundry logs collection using consumer v1 API#19125
Merged
jsoriano merged 18 commits intoelastic:masterfrom Jun 16, 2020
Merged
Add support for cloudfoundry logs collection using consumer v1 API#19125jsoriano merged 18 commits intoelastic:masterfrom
jsoriano merged 18 commits intoelastic:masterfrom
Conversation
dca9da5 to
5271fcc
Compare
18 tasks
Contributor
💔 Build Failed
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
blakerouse
approved these changes
Jun 12, 2020
Contributor
blakerouse
left a comment
There was a problem hiding this comment.
Looks good, like the ability to switch between v1 and v2.
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Jun 16, 2020
…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)
jsoriano
added a commit
that referenced
this pull request
Jun 16, 2020
…19125) (#19212) 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)
6 tasks
6 tasks
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
…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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
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