Metrics
Prometheus
Flipt exposes Prometheus metrics by default at the/metrics
HTTP endpoint. To see which metrics are currently supported, point your browser
to FLIPT_HOST/metrics
(ex: localhost:8080/metrics
).
You should see a bunch of metrics being recorded such as:
You can disable the Prometheus metrics collection by setting the
metrics.enabled
configuration option to false
.OTLP
Flipt supports sending metrics to an OTLP collector. OTLP supports additional configuration such as specifying the protocol to use (gRPC or HTTP) as well as providing custom headers to send with the request. Custom headers can be used to provide authentication information to the collector which may be required if you are using a hosted collector such as NewRelic, DataDog, or Honeycomb. These can be configured via themetrics.otlp
configuration section.
Dashboards

Logging
Flipt writes logs to STDOUT in two formats: The format can be configured via thelog.encoding
configuration option.
JSON
Log Key Descriptions
L
: Level (log level). Possible values include: debug, info, warn, error, fatal, and panic.T
: Timestamp. The timestamp is in ISO 8601 format, widely used for representing date and time. It includes the date, time, and time zone information. For example, “2024-01-20T21:59:49-05:00” represents the date and time in the Eastern Time Zone (UTC-5).M
: Message. The message describes the log event. It can include information about the operation, errors encountered, or other relevant details.
Console
Tracing
Flipt supports distributed tracing via the OpenTelemetry project. Currently, we support the following tracing backends: Enable tracing via the values described in the Tracing configuration and point Flipt to your configured collector to record spans. Examples showing how to set up Flipt with each of the supported tracing backends can be found in the main GitHub repository .OTLP

tracing.otlp
configuration section.
Environment Variables
Flipt supports OTLP specific resource environment variables that are part of the OTLP spec. The following environment variables are supported:OTEL_SERVICE_NAME
- Sets the value of theservice.name
resource attribute (default:flipt
)OTEL_RESOURCE_ATTRIBUTES
- Key-value pairs to be used as resource attributes.