Why are there additional "parsed fields" in Grafana Drilldown that I do not specified explicitly?

I am using Alloy to send Kubernetes log to Loki and Explore/Drilldown to visualize the log. Here is the Alloy config snippet that I use to specify the labels and structured metadata:

discovery.relabel "default_pod_logs" {

 	<omitted>

	rule {
		source_labels = ["__meta_kubernetes_namespace"]
		action        = "replace"
		target_label  = "namespace"
	}
	rule {
		source_labels = ["__meta_kubernetes_pod_name"]
		action        = "replace"
		target_label  = "pod"
	}
	rule {
		source_labels = ["__meta_kubernetes_pod_container_name"]
		action        = "replace"
		target_label  = "container"
	}
	rule {
		source_labels = ["__meta_kubernetes_pod_label_app_kubernetes_io_name"]
		action        = "replace"
		target_label  = "app"
	}

 	<omitted>

}

loki.process "java_pod_logs" {

 	<omitted>

	stage.structured_metadata {
		values = {
			java_service_name = "",
			level = "",
			primary_context = "",
			secondary_context = "",
			retention = "",
		}
	}

	<omitted>

	stage.output {
		source = "message"
	}

	<omitted>

}

and here is the details of the log as seen in Explore:

which is as I expected: the labels and structured metadata fields are what I specified with several auto-added label from Alloy’s discovery component.

But when seen in Drilldown, there are additional “parsed labels”:


I am guessing that there is a mechanism in somewhere that automatically detect the log format and parse it, maybe mistakenly as Logfmt.

My questions are

  1. Why is this happening?
  2. I don’t want the parsed labels to be shown at all in Drilldown, including in the Fields tab. Is it possible?

I am not aware of Loki doing this except for log level detection. What is your actual logql query?

LogQL in Explore:

{service_name="paycoreservice", pod="paycoreservice-f8dbd95cd-vbzzh"} |= `c66f7b891d444277a760de99e6ec702d` |= `statement_timeout`

Also here is the filters in Drilldown:

Sorry, I forget to include the version info. I am using Grafana v12.0.0, simple scalable deployment Loki v3.5.0 from Helm chart v6.3.0, and Alloy v1.9.0 as Deployment from Helm chart v1.1.0

I haven’t upgraded to Grafana 12, so I can’t say for sure, but I think that’s what the log drill down feature does. See What's new in Grafana v12.0 | Grafana documentation