Creating repeatable panels based on a variable with annotations

Monitoring and Observability Grafana
#1

Hello! One quick question because Google doesn’t help (probably due to my poor phrasing): I have a dashboard in Grafana with a repeatable panel that shows network traffic per switch based on a variable ($switch). This works fine but now I’m trying to add Loki logs as annotations on the same dashboard. For the love of whichever god, I cannot find the proper way to do this!

Now, if I hardcode a specific switch, this works fine. What I cannot make happen is somehow pass the Grafana variable in the LogQL query. Is there any way to do that?

#2

I did it like this ; {filename="/var/log/telegraf/telegraf.log",job=~.*${telegraf}$}

#3

Hmm, I don’t have telegraf in my stack but I have Loki as a direct data source instead. Unfortunately, if I’m not missing something, it seems that I cannot pass Grafana vars as ${variable}.

#4

Whats the full query you use with hardcoded variable?

#5

Aaah, just saw the backticks! What works (hardcoded) is this {host="10.25.251.1"}

#6

And these IP addresses ‘live’ under dashboard variable switch

#7

Host=~.*${switch}$
maybe this works then?

#8

So, if I’m translating correct from what you suggested, it should become something like this, {host=${switch}$}, right? Trying right now…

#9

https://stackoverflow.com/questions/64531912/grafana-loki-query-with-regex-interpolation-for-multiple-choice-variable

#10

That’s what I used as a reference when i made mine

#11

Yes, that’s exactly the case but I’m not quite there yet…

#12

{host=${switch}} should work according to the article you linked but it doesn’t for whatever reason

#13

This gives you nothing also? {host=~.*${switch}$}

#14

Well, it should be an exact match so I’d guess it doesn’t need the tilde. Nevertheless, I tried it too and still nada.

#15

What does the query inspector say?

#16

When I save the dashboard after changing the annotation query, I get this

#17

Same with or without tilde

#18

Strange, i haven’t seen that error on mine before

#19

Aaah, nevermind! I’ll pick it up again on Monday. A million thanks for your assistance though!!!

#20

No problem :slightly_smiling_face: