Loki
Last updated
Was this helpful?
Last updated
Was this helpful?
is multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate.
The Fluent Bit loki built-in output plugin allows you to send your log or events to a Loki service.
It supports data enrichment with Kubernetes labels, custom label keys and Tenant ID within others.
Be aware there is a separate Golang output plugin provided by with different configuration options.
host
Loki hostname or IP address. Do not include the subpath, i.e. loki/api/v1/push, but just the base hostname/URL.
127.0.0.1
uri
Specify a custom HTTP URI. It must start with forward slash.
/loki/api/v1/push
port
Loki TCP port
3100
tls
Use TLS authentication
off
http_user
Set HTTP basic authentication user name
http_passwd
Set HTTP basic authentication password
bearer_token
Set bearer token authentication token value.
header
Add additional arbitrary HTTP header key/value pair. Multiple headers can be set.
tenant_id
Tenant ID used by default to push logs to Loki. If omitted or empty it assumes Loki is running in single-tenant mode and no X-Scope-OrgID header is sent.
labels
Stream labels for API request. It can be multiple comma separated of strings specifying key=value pairs. In addition to fixed parameters, it also allows to add custom record keys (similar to label_keys property). More details in the Labels section.
job=fluent-bit
label_keys
Optional list of record keys that will be placed as stream labels. This configuration property is for records key only. More details in the Labels section.
label_map_path
Specify the label map file path. The file defines how to extract labels from each record. More details in the Labels section.
structured_metadata
structured_metadata_map_keys
remove_keys
Optional list of keys to remove.
drop_single_key
If set to true and after extracting labels only a single key remains, the log line sent to Loki will be the value of that key in line_format. If set to raw and the log line is a string, the log line will be sent unquoted.
off
line_format
Format to use when flattening the record to a log line. Valid values are json or key_value. If set to json, the log line sent to Loki will be the Fluent Bit record dumped as JSON. If set to key_value, the log line will be each item in the record concatenated together (separated by a single space) in the format.
json
auto_kubernetes_labels
If set to true, it will add all Kubernetes labels to the Stream labels
off
tenant_id_key
Specify the name of the key from the original record that contains the Tenant ID. The value of the key is set as X-Scope-OrgID of HTTP header. It is useful to set Tenant ID dynamically.
compress
Set payload compression mechanism. The only available option is gzip. Default = "", which means no compression.
workers
0
Loki store the record logs inside Streams, a stream is defined by a set of labels, at least one label is required.
Fluent Bit implements a flexible mechanism to set labels by using fixed key/value pairs of text but also allowing to set as labels certain keys that exists as part of the records that are being processed. Consider the following JSON record (pretty printed for readability):
If you decide that your Loki Stream will be composed by two labels called job and the value of the record key called stream , your labels configuration properties might look as follows:
When processing above's configuration, internally the ending labels for the stream in question becomes:
Another feature of Labels management is the ability to provide custom key names, using the same record accessor pattern we can specify the key name manually and let the value to be populated automatically at runtime, e.g:
When processing that new configuration, the internal labels will be:
label_keys propertyThe additional configuration property called label_keys allow to specify multiple record keys that needs to be placed as part of the outgoing Stream Labels, yes, this is a similar feature than the one explained above in the labels property.
Consider this as another way to set a record key in the Stream, but with the limitation that you cannot use a custom name for the key value.
The following configuration examples generate the same Stream Labels:
the above configuration accomplish the same than this one:
both will generate the following Streams label:
label_map_path propertyThe configuration property label_map_path is to read a JSON file that defines how to extract labels from each record.
The file should contain a JSON object. Each keys define how to get label value from a nested record. Each values are used as label names.
The following configuration examples generate the same Stream Labels:
map.json:
The following configuration examples generate the same Stream Labels:
the above configuration accomplish the same than this one:
both will generate the following Streams label:
Note that if you are running in a Kubernetes environment, you might want to enable the option auto_kubernetes_labels which will auto-populate the streams with the Pod labels for you. Consider the following configuration:
Based in the JSON example provided above, the internal stream labels will be:
If there is only one key remaining after removing keys, you can use the drop_single_key property to send its value to Loki, rather than a single key=value pair.
Consider this simple JSON example:
If the value is a string, line_format is json, and drop_single_key is true, it will be sent as a quoted string.
The outputted line would show in Loki as:
If drop_single_key is raw, or line_format is key_value, it will show in Loki as:
If you want both structured JSON and plain-text logs in Loki, you should set drop_single_key to raw and line_format to json.
Loki does not interpret a quoted string as valid JSON, and so to remove the quotes without drop_single_key set to raw, you would need to use a query like this:
If drop_single_key is off, it will show in Loki as:
You can get the same behavior this flag provides in Loki with drop_single_key set to off with this query:
The following configuration:
Defines fixed values for the cluster and region labels.
Uses the record accessor pattern to set the namespace label to the namespace name as determined by the Kubernetes metadata filter (not shown).
Uses a structured metadata field to hold the Kubernetes pod name.
Other common uses for structured metadata include trace and span IDs, process and thread IDs, and log levels.
Structured metadata is officially supported starting with Loki 3.0, and shouldn't be used with Loki deployments prior to Loki 3.0.
In addition to the structured_metadata configuration parameter, a structured_metadata_map_keys is available, which can be used to dynamically populate structured metadata from map values in the log record. structured_metadata_map_keys can be set with a list of record accessors, where each one should reference map values in the log record. Record accessors which do not match a map value will simply be skipped.
The following configuration is similar to the above, except now all entries in the log record map value $kubernetes will be used as structured metadata entries.
Assuming the value $kubernetes is a map containing two entries namespace_name and pod_name, the above configuration is equivalent to:
This plugin inherit core Fluent Bit features to customize the network behavior and optionally enable TLS in the communication channel. For more details about the specific options available refer to the following articles:
Note that all options mentioned in the articles above must be enabled in the plugin configuration in question.
An example configuration - make sure to set the credentials and ensure the host URL matches the correct one for your deployment:
The following configuration example, will emit a dummy example record and ingest it on Loki .
Copy and paste the following content into a file called out_loki.conf:
run Fluent Bit with the new configuration file:
Fluent Bit output:
Optional comma-separated list of key=value strings specifying structured metadata for the log line. Like the labels parameter, values can reference record keys using record accessors. See for more information.
Optional comma-separated list of record key strings specifying record values of type map, used to dynamically populate structured metadata for the log line. Values can only reference record keys using record accessors, which should reference map values. Each entry from the referenced map will be used to add an entry to the structured metadata. See for more information.
The number of to perform flush operations for this output.
As you can see the label job has the value fluentbit and the second label is configured to access the nested map called sub targeting the value of the key stream .
Note that the second label name must starts with a $, that means that's a pattern so it provide you the ability to retrieve values from nested maps by using the key names.
lets you attach custom fields to individual log lines without embedding the
information in the content of the log line. This capability works well for high
cardinality data that isn't suited for using labels. While not a label, thestructured_metadata configuration parameter operates similarly to the labels
parameter. Both parameters are comma-delimited key=value lists, and both can use
record accessors to reference keys within the record being processed.
: timeouts, keepalive and source address
: all about TLS configuration and certificates
Fluent Bit supports sending logs (and metrics) to by providing the appropriate URL and ensuring TLS is enabled.