Support dynamic datasource and job name in grafana dashboard

[samui-aug]

System information

• Scylla version (you are using): 2025.1.5
• Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
I'm working on importing the scylla monitoring dashboard into our Internal Jsonnet Mixins using ./generate-dashboards.sh and found out we are unable to select Datasource and job name for some panel is hardcoded as job=scylla which is not feasible in our use cases because we distinct different scylla cluster by job name

Who will benefit with this feature?
People integrating scylla-monitoring into existing and different pattern than the one provided in scylla-monitoring

Any Other info.

[amnonh]

There are a few metric we need to filter by job name, specifically to identify that a scylla node is unreahable.
How would you think you'll be using this dynamic option? how would you specifiy the relevant job name?
Maybe we can instead using a regular expression for the scylla jobs (i.e. as long as it's start with scylla but does not coflict with scylla_manager, we can probably have something)

Can you describe the scenario you need to choose a datasource?

[samui-aug]

Turn out job name don't need any change to it after I tried using the dashboard with multiple different scylla cluster, the dashboard are able to distinct between each cluster correctly using cluster

As for the need to choose a datasource is because there are such cases where having Scylladb in different cluster thus different prometheus datasource that connected to 1 Grafana instance or even have 1 datasource that named differently than prometheus could cause the generated dashboard to not working when importing

But I did some work around for datasource in our setup and It's working fine and not breaking anything

[amnonh]

@samui-aug is there anything left are can we close this?