Benjamin Huo

> > My thinking was we could have a generic config section that supports key-value pairs and just applies them into the config rather than having named keys we have...

Processing logs is the advantage of fluentbit and I don't think OpenTelemetry collector can be better. So supporting OTLP logs via fluentbit is exciting just like collecting OTLP metrics and...

> CRD updates for using OTEL output though might be a good thing @benjaminhuo which I think was the original request here (apologies for taking things off at a tangent)....

An issue for adding the OpenTelemetry plugin has been created https://github.com/fluent/fluent-operator/issues/325

@patrick-stephens @frankgreco @wenchajun @wenchajun @zhu733756 @mangoGoForward I am think adding customplugin crd like this: ```yaml apiVersion: fluentbit.fluent.io/v1alpha2 kind: ClusterCustomPlugin metadata: name: splunk-output labels: type: output # or input, filter, parser...

> [PLUGINS] > path /a/path/libplugin1.so > path /b/path/libplugin2.so Where should these plugin paths be added? FluentBit itself has a separate configuration mechanism for this?

> I made some changes. Except for the plugin name and plugin type, other parameters are placed under plugin.config. Is this ok? @benjaminhuo That's ok.

I think we can change it a little bit like: @Gentleelephant ```yaml apiVersion: fluentbit.fluent.io/v1alpha2 kind: ClusterInput metadata: namespace: fluent name: cpu-input labels: fluentbit.fluent.io/enabled: "true" fluentbit.fluent.io/mode: "fluentbit-only" spec: customPlugin: Config: |...

Thanks to @Gentleelephant , the custom plugin is supported now: https://github.com/fluent/fluent-operator/pull/377 https://github.com/fluent/fluent-operator/blob/master/docs/best-practice/custom-plugin.md

autoscaling might not work for stateful set