Add support for cloudfoundry metrics collection using consumer v1 API #19268
Conversation
This file contains 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
botelastic
bot
added
the
needs_team
jsoriano
added
[zube]: In Progress
in progress
botelastic
bot
removed
the
needs_team
zube
bot
added
[zube]: Inbox
[zube]: In Progress
and removed
[zube]: In Progress
[zube]: Inbox
labels
zube
bot
added
[zube]: Inbox
[zube]: In Progress
and removed
[zube]: In Progress
[zube]: Inbox
labels
zube
bot
added
[zube]: Inbox
[zube]: In Progress
and removed
[zube]: Inbox
[zube]: In Progress
labels
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
jsoriano
added
needs_backport
18 tasks
exekias
approved these changes
Jun 24, 2020
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Jun 24, 2020
…elastic#19268) As previously done for the Filebeat input, add support for metrics collection in the Metricbeat module using the consumer v1 API. It reuses the same Doppler consumer used in Filebeat. 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. (cherry picked from commit 5645491)
6 tasks
jsoriano
removed
the
needs_backport
jsoriano
added a commit
that referenced
this pull request
Jun 25, 2020
…#19268) (#19372) As previously done for the Filebeat input, add support for metrics collection in the Metricbeat module using the consumer v1 API. It reuses the same Doppler consumer used in Filebeat. 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. (cherry picked from commit 5645491)
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
…elastic#19268) As previously done for the Filebeat input, add support for metrics collection in the Metricbeat module using the consumer v1 API. It reuses the same Doppler consumer used in Filebeat. 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Continues with #19125 to add support to Cloud Foundry consumer v1 API in Metricbeat too.
versioncan be used to select ifv1orv2version should be used.Why is it important?
We already support the v2 API, but we saw that this API is not reliable enough (see #18202 and #18282).
Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
versionoption:versionoption (what would usev1)version: v1.version: v2.versionit should fail to start.Related issues