kgess-mirror/oneuptime
1
0
Fork 0
mirror of https://github.com/OneUptime/oneuptime.git synced 2026-01-11 19:56:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 16
oneuptime/FluentBit
History
Exact
Simon Larsen 1ac6e71f7e
chore(config,docker,ci,ui): rename IS_ENTERPRISE to IS_ENTERPRISE_EDITION across env, Dockerfiles, compose and workflows
2025-11-03 11:25:12 +00:00
..
etc feat: update FluentBit and OTelCollector configurations to include service name in headers and adjust logging level 2025-04-04 15:24:40 +01:00
Dockerfile.tpl chore(config,docker,ci,ui): rename IS_ENTERPRISE to IS_ENTERPRISE_EDITION across env, Dockerfiles, compose and workflows 2025-11-03 11:25:12 +00:00
README.md Add HTTP input to Fluent Bit configuration and expose port 8889 for telemetry ingestion 2024-12-05 14:43:39 +00:00

README.md

Fluentd

This guide will help you test fluent-bit logs with OneUptime.

Prerequisites

  • Filuentd docker container running on your system (essentially this folder should be running). You can run the container using the command npm run dev fluent-bit
  • OneUptime account
  • OneUptime project
  • Telemetry Ingestion Key (Create one from the OneUptime dashboard, Click on More -> Project Settings -> Telemetry Ingestion Key)

Configuration and Testing

  • Please make sure the correct token and url is in the configuration file located at FluentBut/etc/fluent-bit.yaml.
  • Build the docker image using the command npm run force-build fluent-bit
  • Run the docker image using the command npm run dev fluent-bit
  • Send logs to the Fluentd container using the curl command
curl -X POST -H "Content-Type: application/json" -d '{"log": "This is a test log message"}' http://localhost:8889

You should be able to see the logs in the OneUptime dashboard.