Cherry-pick #20440 to 7.x: [Filebeat][ATP Module]Setting user agent field required by the API#20446
Merged
adriansr merged 1 commit intoelastic:7.xfrom Aug 5, 2020
Merged
Conversation
…lastic#20440) Setting user-agent field required by ATP API for monitoring purposes (cherry picked from commit 6a9a20e)
Contributor
|
Pinging @elastic/siem (Team:SIEM) |
Contributor
kvch
approved these changes
Aug 5, 2020
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
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 #20440 to 7.x branch. Original message:
What does this PR do?
Vendor modules are required to include a header for tracking purposes
Why is it important?
The header set is a requirement to use the ATP/MTP API.
Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.