adding filter processor in receiver and collector

[Shashankft9]

fixes #8

[DelusionalOptimist]

@Shashankft9 Thank you for the PR! 🚀
Though this method to filter logs will work however it shouldn't be handled this way ideally. It's because there is logic for filtering already present in Kubearmor.

Kubearmor emits separate streams for logs (generic events) and alerts (policy events). So a good place to investigate will be why the adapter can't subscribe to just a single stream based on the configuration passed.
The relevant code -

otel-adapter/stanza_input_operator/input_operator.go

Line 131 in 9f702ef

if logfilter == "all" || logfilter == "policy" {

[DelusionalOptimist]

cc @Chinwendu20

[Chinwendu20]

Hello thanks for the PR but the receiver has a config for getting the required kubearmor logs. We will fix anything wrong in the code instead of adding extra components to the collector distro.

[DelusionalOptimist]

@Shashankft9 PTAL at the changes introduced by PR: #11
You can set the configuration in the receiver's manifest according to this.