Supported agents

Quickwit is compatible with the following agents:

OpenTelemetry agent

Before using an OpenTelemetry collector, check that Quickwit OpenTelemetry service is enabled. Once started, Quickwit is then ready to receive and ingest OpenTelemetry gRPC requests.

Here is a configuration example of an OpenTelemetry agent that sends logs into Quickwit:

mode: daemonset
presets:
  logsCollection:
    enabled: true
  kubernetesAttributes:
    enabled: true
config:
  exporters:
    otlp:
      # Replace quickwit-host with the hostname of your Quickwit node/service.
      # On k8s, it should be of the form `{quickwit-indexer-service-name}.{namespace}.svc.cluster.local:7281
      endpoint: quickwit-host:7281
      tls:
        insecure: true
  service:
    pipelines:
      logs:
        exporters:
          - otlp

Find more configuration details on the OpenTelemetry documentation. You can also check out our tutorial to send logs with OTEL collector to Quickwit.

HTTP-based agents

It's also possible to use other agents that send HTTP requests to Quickwit Ingest API. Quickwit also partially supports Elasticseardch _bulk API. Thus, there is a good chance that your agent is already compatible with Quickwit. Currently, we have tested the following HTTP-based agents:

• Vector
• Fluentbit
• FluentD (tutorial coming soon)
• Logstash: Quickwit does not support the Elasticsearch output. However, it's possible to send logs with the HTTP output but with json format only.

Quickwit natively supports the OpenTelemetry Protocol (OTLP) and provides a gRPC endpoint to receive logs from an OpenTelemetry collector by default.

The logs received by this endpoint are indexed on the otel-logs-v0 index. This index will be automatically created if not present. The index doc mapping is described in this section.

You can also send your logs directly to this index by using the ingest API.

OpenTelemetry service

Quickwit natively supports the OpenTelemetry Protocol (OTLP) and provides a gRPC endpoint to receive spans from an OpenTelemetry collector. This endpoint is enabled by default.

When enabled, Quickwit will start the gRPC service ready to receive spans from an OpenTelemetry collector. The spans are indexed in the otel-trace-v0_7 index by default, and this index will be automatically created if not present. The index doc mapping is described in the next section.

If for any reason, you want to disable this endpoint, you can:

• Set the QW_ENABLE_OTLP_ENDPOINT environment variable to false when starting Quickwit.
• Or configure the node config by setting the indexer setting enable_otlp_endpoint to false.

node-config.yaml

# ... Indexer configuration ...
indexer:
    enable_otlp_endpoint: false