-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Meta] Cloud Foundry Support #16520
Labels
Filebeat
Filebeat
meta
Metricbeat
Metricbeat
Team:Platforms
Label for the Integrations - Platforms team
v7.11.0
Comments
blakerouse
added
Filebeat
Filebeat
Metricbeat
Metricbeat
Team:Platforms
Label for the Integrations - Platforms team
labels
Feb 24, 2020
3 tasks
This was referenced Feb 25, 2020
andresrc
added
[zube]: Inbox
[zube]: In Progress
and removed
[zube]: In Progress
[zube]: Inbox
labels
Mar 9, 2020
This was referenced Mar 27, 2020
This was referenced Jun 11, 2020
This was referenced Jun 18, 2020
When will the dashboards be ready? @jsoriano |
6 tasks
This was referenced Sep 18, 2020
This was referenced Nov 20, 2020
Merged
Closing as we only have #17539 and #21532 left that will be scheduled later. |
This was referenced Feb 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Filebeat
Filebeat
meta
Metricbeat
Metricbeat
Team:Platforms
Label for the Integrations - Platforms team
v7.11.0
Overview
Cloud Foundry loggregator provides a gRPC stream to receive a combined logs and metrics about the applications running inside of Cloud Foundry. Loggregator provides selectors on connection to gRPC to split up the logs vs metrics.
Filebeat and metricbeat can use the gRPC stream with selectors to split up the events to process the appropriate events respectively as inputs to send to elasticsearch.
Libbeat work to complete
add_cloudfoundry_metadata
to add application metadata to events shared between metricbeat and filebeat.Filebeat work to complete
cloudfoundry
input to filebeat.cloudfoundry
input.Test log files exist for the grok patterns(Logs come from gRPC protocol buffer events)Generated output for at least 1 log file existsMetricbeat work to complete
cloudfoundry
module.cloudfoundry
module.data.json
existsand an automated way to generate it exists ((Currently no way to autogenerate)go test -data
)Test environment in Docker exist for integration tests(Cannot run Cloud Foundry in Docker)Usage work to complete
The text was updated successfully, but these errors were encountered: