Welcome to grizzly Discussions!

[malcolmholmes]

👋 Welcome!

Grizzly is a tool in which we are exploring ideas about how to interact with various observability resources, "from code".

⚠️ Grizzly is currently alpha code - the APIs etc that it exposes can, and likely will change.

This Discussion board is here to allow you to ask questions and explore possible usages and features. We can also use it to share new features.

[DamGameHero]

Hello !

What do you think about using the provisioning the folder structure from filesystem to Grafana via a grr export ?

Currently with grr export in last release (v 0.1.0), dashboards are created in:

my-provisioning-dir/Dashboard/dashboard.json

Dashboard folder is a value that can't be changed. Line here, I guess:

grizzly/pkg/grizzly/workflow.go

Line 387 in b719359

dir := fmt.Sprintf("%s/%s", exportDir, resource.Kind())

However, to take advantage of the folder structure, it would be preferable to build the path like this:

my-provisioning-dir/grafanaDashboardFolder/dashboard.json

With grafanaDashboardFolder given like in the mydash.libsonnet example or in another way .

I had done this feature, but it was on the previous version. This has evolved since and I would like to know your opinion on this point.

[malcolmholmes]

Hi, firstly, welcome! Secondly, if poss, it is better to create a seperate thread. Will help others find this in future.

To answer your question, I am working on a next version, and your feedback is very useful. I want to make Grizzly able to pull from Grafana, so pull raw json and write it (likely as yaml manifests) to disk. For this I need a way to specify a directory structure. This fits well with your need.

It is also useful to be reminded that file system provisioning requires raw unwrapped json blobs, which is slightly different to the route I was going.

I hope to make some PRs this weekend, and would appreciate comment. I don't expect the PRs to get merged immediately, they will be more about exploring APIs etc.

[DamGameHero]

Ok thanks for the reply. Seperate thread: #106