fluent-bit: Official Windows build for 1.6.1 does not support built-in HTTP server

Bug Report

Describe the bug HTTP_Server On has no effect using Windows official build of Fluent Bit 1.6.1

To Reproduce Use this config file and start Fluent Bit:

[SERVICE]
    HTTP_Server   On

[INPUT]
    Name         winlog
    Channels     System,Application,ThreatStack
    DB           winlog.db

[OUTPUT]
    Name            es
    Match           *
    Host            <REDACTED>
    Port            80
    Retry_Limit     5

The log indicates that the HTTP server is not started:

PS C:\FluentBit> .\fluent-bit.exe -c .\fluent-bit.conf
Fluent Bit v1.6.1
* Copyright (C) 2019-2020 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2020/10/17 07:44:11] [ info] [engine] started (pid=6324)
[2020/10/17 07:44:11] [ info] [storage] version=1.0.6, initializing...
[2020/10/17 07:44:11] [ info] [storage] in-memory
[2020/10/17 07:44:11] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2020/10/17 07:44:12] [ info] [sp] stream processor started
[2020/10/17 07:44:41] [engine] caught signal (SIGINT)
[2020/10/17 07:44:41] [ info] [input] pausing winlog.0
[2[2020/10/17 07:44:41] [error] [C:\projects\fluent-bit-2e87g\src\flb_utils.c:339 errno=0] No error
020/10/17 07:44:41] [ info] [input] pausing tail.1
[2020/10/17 07:44:41] [error] [C:\projects\fluent-bit-2e87g\src\flb_utils.c:339 errno=0] No error
[2020/10/17 07:44:41] [ warn] [engine] service will stop in 5 seconds
[2020/10/17 07:44:46] [ info] [engine] service stopped

Expected behavior HTTP server works

Your Environment “Windows_Server-2019-English-Full-ContainersLatest-2020.04.15” AMI on AWS

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

Thanks for the info! In the meantime you may want to update the docs to indicate HTTP monitoring is not available on Windows - it nah save people time

@qingling128 I’m currently planning to work on this task in the next v1.8 dev cycle.