Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick #19125 to 7.x: Add support for cloudfoundry logs collection using consumer v1 API #19212

Merged
merged 1 commit into from
Jun 16, 2020

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Jun 16, 2020

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 using v2. Support for v1 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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • Review FIXMEs in code.
  • Test with PCF

How to test this PR locally

  • Run filebeat with the cloudfoundry input and check that it collects events. Try these combinations of the version option:
    • No version option (what would use v1)
    • version: v1.
    • version: v2.
    • For other values of version it should fail to start.

Related issues

…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 jsoriano added [zube]: In Review backport Team:Platforms Label for the Integrations - Platforms team labels Jun 16, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-platforms (Team:Platforms)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jun 16, 2020
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #19212 opened]

  • Start Time: 2020-06-16T08:09:53.674+0000

  • Duration: 83 min 44 sec

Test stats 🧪

Test Results
Failed 0
Passed 6694
Skipped 1069
Total 7763

Steps errors

Expand to view the steps failures

  • Name: Report to Codecov

    • Description: curl -sSLo codecov https://codecov.io/bash for i in auditbeat filebeat heartbeat libbeat metricbeat packetbeat winlogbeat journalbeat do FILE="${i}/build/coverage/full.cov" if [ -f "${FILE}" ]; then bash codecov -f "${FILE}" fi done

    • Duration: 2 min 22 sec

    • Start Time: 2020-06-16T08:45:25.718+0000

    • log

  • Name: Report to Codecov

    • Description: curl -sSLo codecov https://codecov.io/bash for i in auditbeat filebeat heartbeat libbeat metricbeat packetbeat winlogbeat journalbeat do FILE="${i}/build/coverage/full.cov" if [ -f "${FILE}" ]; then bash codecov -f "${FILE}" fi done

    • Duration: 2 min 22 sec

    • Start Time: 2020-06-16T09:29:42.790+0000

    • log

Copy link
Member

@ChrsMark ChrsMark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jsoriano how about fixing #19213 here to avoid having an extra backport PR?
nah, this PR seems to not have any lint issues? 🤔

@jsoriano
Copy link
Member Author

@jsoriano how about fixing #19213 here to avoid having an extra backport PR?
nah, this PR seems to not have any lint issues? 🤔

#19213 seems to be needed in combination with #19135.

@jsoriano jsoriano merged commit e8aa16e into elastic:7.x Jun 16, 2020
@jsoriano jsoriano deleted the backport_19125_7.x branch June 16, 2020 10:41
@zube zube bot removed the [zube]: Done label Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Platforms Label for the Integrations - Platforms team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants