# Fluent Bit config: tail vgi-rpc access logs and ship to Google Cloud Storage.
#
# Fluent Bit does not have a first-party GCS object-storage output as of this
# writing.  Two practical options:
#   1. Use the `stackdriver` output to send records to Cloud Logging, then
#      configure a Cloud Logging sink that exports to a GCS bucket.  This is
#      the recommended path on GKE / Cloud Run because authentication is
#      handled automatically by the workload identity.
#   2. Use the `http` output to push directly to a GCS-hosted ingestion endpoint
#      (e.g. a Cloud Function or Cloud Run service that writes to GCS).
#
# This file shows option (1).

[SERVICE]
    Flush         5
    Log_Level     info
    Parsers_File  parsers.conf

[INPUT]
    Name              tail
    Path              /var/log/vgi-rpc/access-*.jsonl
    Path_Key          source_path
    Parser            json
    Tag               vgi_rpc.access
    Refresh_Interval  5
    Rotate_Wait       30
    DB                /var/lib/fluent-bit/vgi-rpc-access.db
    Buffer_Max_Size   1MB

[OUTPUT]
    Name        stackdriver
    Match       vgi_rpc.access
    resource    global