search

fluent / fluent-operator

Operate Fluent Bit and Fluentd in the Kubernetes way - Previously known as FluentBit Operator
Apache License 2.0
587 stars 250 forks source link

bug: Allows to render net properties for outputs #1298

Closed dex4er closed 3 months ago

dex4er commented 3 months ago

What this PR does / why we need it:

It renders attributes from networking field and fixes DNSResolver.

Which issue(s) this PR fixes:

Fixes #1297

Does this PR introduced a user-facing change?

No

Additional documentation, usage docs, etc.:

dex4er commented 3 months ago

You can test with image public.ecr.aws/dex4er/fluent-operator:pr-1298

The configuration renders now to:

[Output]
    Name    opensearch
    Match    *
    Host    redacted
    Port    443
    Buffer_Size    10M
    Type    _doc
    Logstash_Format    true
    Logstash_Prefix    redacted
    Logstash_DateFormat    %Y%m%d
    Time_Key    @timestamp
    Time_Key_Format    %Y-%m-%dT%H:%M:%S
    Time_Key_Nanos    false
    Include_Tag_Key    true
    Tag_Key    log_name
    Generate_ID    false
    Write_Operation    create
    Replace_Dots    true
    Trace_Output    false
    Trace_Error    true
    Current_Time_Index    false
    Suppress_Type_Name    true
    tls    On
    net.dns.resolver    LEGACY

and fluent-bit actually starts as expected and I see logs in OpenSearch index.