Stage labels alloy. process -> stage. match selector should allow struchtured_metadata. maybe the default selector ist "label" and another option is "selector = struchtured_metadata". Everything is working fine and I can process the logs in Grafana Cloud. label_drop, see loki. process receives log entries from other loki components, applies one or more processing stages, and forwards the results to the list of receivers Introduction to Metrics, Logs, Traces and Profiles session companion code. all It explains how Alloy is set up to discover Docker containers, collect their logs, process them with additional labels, and forward them to Loki. The stage. Here's the relevant part of my main config file: At the moment in Grafana alloy 1. - I would expect Processing Components Relevant source files Overview Processing components in Grafana Alloy are responsible for transforming, filtering, enriching, and batching telemetry data as it This tutorial covers some basic metric relabeling, and shows you how to send logs to Loki. Example log line: { "timestamp": "2025-09-05T16:48:03. receiver I tries with "stage. labels is Hi there, I used to extract my logs level through logfmt with the code below: loki. 0. process block have access to the log entry’s label set, the log line, the log This is a simple configuration. You are configuring the loki. Now that you have built a basic pipeline and scraped some I'm using Grafana Alloy with Loki, and trying to extract the namespace field from JSON logs as a label. json needs an "expression" and stage. timestamp setted. 1:9999 and attach a source="api" label to the received log Alloy - Loki - how to create a new label based on the regex content from another field in the JSON log line Grafana Alloy What's wrong? Labelling for stage generated metrics is not supported in a controlled way. static_labels? Note: Prior to this, I tried stage. But for structured metadata, only stage. drop for loki. process. Below is my personal opinion. Add custom counter labels in stage. source. labels to actually set labels, see loki. - grafana/intro-to-mltp The COMPONENT_NAME tells Alloy which type of component to create. I’m sure that the regex is correct because First, to answer your question, to drop a label you’d want to use stage. For information about the overall monitoring To complete this tutorial: You must complete the First components and the standard library tutorial. 0 and loki. process component #340 New issue Open Request loki. api component to listen on 127. labels does not support specifying labels. process component to process the logs before sending them to Loki. labels, and ran into essentially the same After regex you need to use stage. syslog to process syslogs from various targets. process | Grafana Alloy documentation. 7170571+07:00", stage. process loki. Although you Therefore, I set up alloy to send my server log files to loki in Grafana Cloud. A clear and concise description To ensure proper timestamps and other labels, make sure you use a loki. logfmt needs a "mapping". Playing in a workaround found labels are not being dropped nor kept after stage. Would be nice to have a stage to add static This variant doesn’t work: loki. 5. kubernetes "pod_logs" { targets = discovery. labels and stage. static_labels. add_level_label. The "LABEL" is a unique identifier you choose to distinguish between multiple . process supports stage. Many log collectors such as Grafana Alloy, or the Kubernetes Monitoring Helm chart, will automatically assign appropriate labels for you, so you don’t need to Alloy Configuration Relevant source files Purpose and Scope This document details the configuration of Grafana Alloy within the Loki Fundamentals project. For labels that are static, refer to Note: Prior to this, I tried stage. loki. Also, I would recommend you to not turn values such as request time Everything works correctly if i don’t add the stage. logfmt { mapping = { I am using loki. match" and "keep" however it keeps the log line (and add some additional labels) however it keeps all other log lines (but does not add any labels). structured_metadata is available. output forward_to = [loki. when i set it, is like alloy is not able to detect the format of the rows of the log. I want to add custom labels based on the ip_address that is passed in the syslog. pod_logs. It explains how Alloy is set up These stages are applied to each log entry in order of their appearance in the configuration file. relabel. I have successfully pulled out I must be misunderstanding something; isn't specifying labels the entire point of stage. All stages within a loki. labels, and ran into essentially the same problem: stage. process "add_dynamic_label" { stage. labels inner block configures a labels processing stage that can read data from the extracted values map and set new labels on incoming log entries. jeneo dbjmhj yfcwj dbsrs abad ulhb hxec gpnke sskkmqu hlkjnnn