Apica Docs
Ask or search…

Fluent Bit

Fluent Bit configuration

HTTP output plugin allows flushing your records into an HTTP endpoint. The HTTP output plugin allows to provide interoperability between compatible systems, Apica Ascent being one.
The below code block defines the minimal changes to be added to the fluent-bit configuration using the HTTP plugin to start sending log events to flash.The below config supports storage persistence.
Flush 1
Parsers_File /etc/td-agent-bit/parsers.conf
Log_Level error
Storage.type filesystem
Storage.path /var/log/flb_storage_
Buffer storage.sync normal
Storage.checksum On
Storage.backlog.mem_limit 700kb
Storage.metrics On
Name tail
Path /var/log/*.log
Path_Key filename
Tag logiq
Buffer_Max_Size 1024k
Read_from_Head On
Mem_Buf_Limit 1MB
Refresh_Interval 5
Storage.type filesystem
Name record_modifier
Match logiq
Record cluster_id flash
Name record_modifier
Match logiq
Record namespace xyz
Name record_modifier
Match logiq
Record app_name system_logs
Name throttle
Match *
Rate 700
Window 300
Interval 1s
Name http
Match *
Host lq5955.logiq.ai
Port 80
URI /v1/json_batch
Format json
tls off
tls.verify off
net.keepalive off
compress gzip
Header Authorization Bearer ${LOGIQ_TOKEN}

Fluent Bit for Windows

You can use Fluent Bit to ship Windows logs to Apica Ascent by leveraging the following Fluent Bit configuration.
The instruction to install fluent-bit for windows is available at the following git repository - https://github.com/logiqai/logiq-installation/tree/main/fluent-bit/windows
The folder in the git repository includes a PowerShell script to set up the windows fluent-bit agent. The PowerShell script downloads the fluent-bit agent and installs the agent as a service. Continue below to see how to set up an example fluent conf and start service on windows.
NOTE: You will need to finalize the fluent configuration and then restart the service. Below is an example of fluent configuration
Flush 1
Daemon yes
Log_Level info
Name record_modifier
Match *
Record namespace Windows
Name modify
Match *
Rename SourceName AppName
Rename ComputerName Hostname
Name winlog
Channels Setup,Windows PowerShell,Security
Tag Windows-events
Interval_Sec 5
name http
match *
host Logiq-Hostname
port 443
URI /v1/json_batch
Format json
tls on
tls.verify off
net.keepalive off
compress gzip
Header Authorization Bearer <token>
To forward Windows logs to Apica Ascent using Fluent Bit, do the following.
  1. 1.
    Copy the configuration provided above and save it locally in a temporary folder.
  2. 2.
    Edit the fields in the [OUTPUT] section of the configuration file to match your Apica Ascent instance.
  3. 3.
    Clone the Apica Ascent installation GitHub repository locally and navigate to the windows folder.
  4. 4.
    Copy and paste the fluent-install.ps1 script into the folder where you saved the Fluent Bit configuration file.
  5. 5.
    Since Windows does not allow you to execute scripts due to default PowerShell script execution policies, you should update the set execution policy by running:
    Set-ExecutionPolicy unrestricted
  6. 6.
    Navigate to Windows > PowerShell and run it in Administrator mode.
  7. 7.
    Execute the fluent-install.ps1 script, as shown in the following example:
    PS D:\test> .\fluentbit-install.ps1
    [SC] CreateService SUCCESS
    The fluent-bit service is starting.
    The fluent-bit service was started successfully.
  8. 8.
    Navigate to Windows > Run.
  9. 9.
    Type services.msc and hit Enter.
You'll now see a Fluent Bit service running on your Windows machine.
OR You can also run the .\status.ps1 helper scripts present at https://github.com/logiqai/logiq-installation/tree/main/fluent-bit/windows/helper-scripts
We have scripts to:
  • Restart Fluent-Bit service.
  • Start Fluent-Bit service.
  • Status of fluent-Bit service.
  • Stop Fluent-Bit service.
  • Uninstall Fluent-Bit service.