“Ad hoc filters” variable works great for Loki labels and fields, but not with structured metadata. I can transform queries only in the following way (these do not work because company_id is in structured metadata): {app="main-app"} → {app="main-app", company_id="123"} {app="main-app"} | json → {a…

[image] FriendlyCraft: {app="main-app"} | json | company_id="123" That indicates that company_id is not medata, but it is a field in the JSON formatted logs. Make sure that your log pipeline ingest company_id as a structured metadata, when you want to use it in that way. [image] Wha…

Thank you for the response. I am pretty sure company_id is part of structured_metadata. I can query it if I do {app="main-app"} | company_id="123". What I am trying to do is the same with Ad hoc filters, but there it can only filter as a label or field

I understand that this is my exact problem. I am trying to build optional filters for structured metadata. Doesn’t have to use Ad hoc filters, can be variable, or whatever. Basically if I have query like this {app="main-app"} and then I specify company_id:123, I want to transform my query to {app="m…

You can use the dashboard variable (e.g. text type, name filter), where the user can write that filter (part of it, e.g. only company id) and use it in the panel query e.g. {app="main-app"} | company_id="${filter:raw}"

Ok, but then if the filter is not provided, the query turns into {app="main-app"} | company_id="", which is not going to match anything. I could specify .+, but then, I am filtering with no filter, degrading the query performance. The idea is that the filter only exists when the variable has a defi…

Yeah, be clever and specify the variable for your case, e.g. there must be a full filter value, not just id, and then you can use panel query: {app="main-app"} ${filter:raw} And yes, there are billions and billions ™ “buts”: but the user can write invalid filter but user doesn’t know ids … Why …

Unfortunately, I can’t use labels since they have quite high cardinality, and indexing them will make Loki unqueriable. {app="main-app"} ${filter:raw} seems the most promising thing I can do, the problem is this will not have a good UX for the average dashboard user, who might not even know what Lok…

I figured out this very unpleasant workaround that fits my use case. I used a random MySQL datasource to template a filter variable based on the values of other variables (company_id, user_id, and session_id). Here is how the template logic looks: SELECT CASE WHEN '${company_id}' <> '' THEN …

Ad hoc filters variable for Loki structured_metadata

Grafana

jangaraj May 29, 2025, 1:39pm 4

OK, so if this is working, then it is metadata. Ad hoc filters work with labels only, not with metadata.

Topic		Replies	Views
Loki query variable filtered by structured meta data Dashboards	0	276	May 21, 2024
Loki query variable - list of structured metadata variables? Grafana dashboard-variables	1	742	May 23, 2024
structuredMetadata vs label escaping Grafana Loki loki , query-help , logql	3	127	January 29, 2026
Using Loki based variable Grafana Loki loki	3	10183	April 21, 2021
Ad hoc filters variable appended to stream label, not to the label filtering section Configuration templating , dashboard-variables	1	54	November 14, 2025

Ad hoc filters variable for Loki structured_metadata

Related topics