elastic / elastic/beats

Investigate disable event normalization processing in Cloudfoundry input

Open
#34,407 1 comment 0 reactions 1 assignee Claimed by @MichaelKatsoulis View on GitHub
investigate Team:Cloudnative-Monitoring
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 15m
Merged PRs (30d)
385

Description

In this issue we will evaluate the benefits in cpu utilisation of filebeat cloud foundry input if we disable event normalization to reduce allocations when processing events.
This was made possible due to [this PR](https://github.com/elastic/beats/pull/33657).

The tests are performed with latest Elasticsearch 8.6 deployed on Elastic Cloud.
The https://apps.sys.giz-2.cf-obs.elastic.dev PCF cluster will be used and traffic will be generated using a log-generator app, each instance of which generates 100K events per minute.
There will be a comparison of cpu usage between a filebeat that disables event normalization and the default filebeat.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.