This destination is for self hosted loki instances.

If you use grafana cloud managed loki, follow the instructions in the Grafana Cloud Loki page.

Configuring the Loki Destination

In order to add a new loki destination, insert the loki backend URL into Odigos UI.

Connection Settings

To send logs to Loki, you need to configure the Loki URL in the Odigos UI. This destination is for self hosted Loki instances, so you will need to have a Loki instance running and accessible from the k8s cluster running odigos.

The URL should be in the format http://<loki-host>:<loki-port>/loki/api/v1/push.

  • If scheme is not provided, it defaults to http.
  • If port is not provided, it defaults to 3100.
  • If path is not provided, it defaults to /loki/api/v1/push.

Loki Labels

Loki labels are used to “index” logs and allow efficent filtering in the Grafana UI. You can read more about them here.

You can configure your grafana cloud loki labels in the Labels multi-input config option in the destination page in the Odigos UI.

  • Labels should be names of opentelemetry resource attribute or log record attribute keys that you want to index, for example: "k8s.namespace.name".
  • To avoid performance issues, it is recommended to limit the number of labels to a reasonable amount.
  • Use only low cardinality values. e.g. use only opentelemetry attributes for which you expect a small number of unique values like http.response.status_code but not network.peer.address.
  • If the label is not present in a log record, it will be ignored.
  • The default labels if not set are: k8s.container.name, k8s.pod.name, k8s.namespace.name