Cherry-pick #20775 to 7.x: Add a persistent cache for cloudfoundry metadata based on badger#21551
Conversation
…stic#20775) Cache on disk is used by add_cloudfoundry_metadata. Cache is written into the beats data directory. Objects in cache are serialized using CBOR encoding. Badger DB is added as dependency. (cherry picked from commit 76905a2)
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
|
Pinging @elastic/integrations-services (Team:Services) |
|
This pull request doesn't have a |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
Failing filebeat tests will be fixed by #21526 |
Cherry-pick of PR #20775 to 7.x branch. Original message:
What does this PR do?
Add a persistent cache on disk for Cloudfoundry metadata, based on badger.
Why is it important?
Improve restart of beats when monitoring very big Cloudfoundry deployments.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
Add settings to make it optional?add_cloudfoundry_metadata.How to test this PR locally
add_cloudfoundry_metadatawith Filebeat or Metricbeat.Related issues