Fluentd

Open source data collector for unified logging layer that allows you to unify data collection and consumption for better use and understanding of data.

3 APIs 0 Features

Data CollectionLoggingOpen Source

APIs

Fluentd Plugin API

The Fluentd Plugin API allows developers to write custom input, output, filter, parser, formatter, and buffer plugins in Ruby. Plugins are distributed as RubyGems and integrate ...

Fluentd Forward Protocol

The Fluentd Forward Protocol is a binary protocol used to transport event streams between Fluentd nodes and compatible agents over TCP. It supports multiple transport modes incl...

Fluentd HTTP Input API

The Fluentd HTTP Input plugin exposes an HTTP endpoint that accepts log records posted as JSON or form-encoded data. It allows applications to send events to Fluentd over standa...

Collections

Fluentd HTTP Input API

OPEN

Pricing Plans

Fluentd Plans Pricing

3 plans

PLANS

Rate Limits

Fluentd Rate Limits

5 limits

RATE LIMITS

FinOps

Fluentd Finops

FINOPS

Event Specifications

Fluentd Forward Protocol

The Fluentd Forward Protocol is a binary MessagePack-based protocol used to transport event streams between Fluentd nodes, Fluent Bit agents, and compatible forwarders over TCP ...

ASYNCAPI

Semantic Vocabularies

Fluentd Context

0 classes · 7 properties

JSON-LD

Resources

GitHubOrganization

Sources

opencollection: 1.0.0
info:
  name: Fluentd HTTP Input API
  version: 1.0.0
items:
- info:
    name: Events
    type: folder
  items:
  - info:
      name: Fluentd Post a log event
      type: http
    http:
      method: POST
      url: http://localhost:8888/:tag
      params:
      - name: tag
        value: ''
        type: path
        description: The Fluentd tag for this event. Tags use dot-separated hierarchical notation (e.g., myapp.access, production.web.error)
          and are used by match directives to route events to outputs.
      body:
        type: json
        data: '{}'
    docs: Posts a single log event to Fluentd with the specified tag. The tag determines which Fluentd match rules route the
      event downstream. The request body can be JSON, MessagePack, or form-encoded. When sending JSON, the Content-Type must
      be application/json. The time field can be supplied in the body or omitted to use the server receive time.
  - info:
      name: Fluentd Post a log event with explicit format
      type: http
    http:
      method: POST
      url: http://localhost:8888/:tag.:format
      params:
      - name: tag
        value: ''
        type: path
        description: The Fluentd tag for this event. Tags use dot-separated hierarchical notation (e.g., myapp.access, production.web.error)
          and are used by match directives to route events to outputs.
      - name: format
        value: ''
        type: path
        description: Explicit format specifier for the request body. Accepted values are 'json' and 'msgpack'.
      body:
        type: json
        data: '{}'
    docs: Posts a single log event to Fluentd with both a tag and an explicit format specifier in the path. The format segment
      can be 'json' or 'msgpack' and overrides Content-Type-based format detection. This is useful for clients that cannot
      set Content-Type headers correctly.
bundled: true