Re: [che-dev] Che-operator and Prometheus && Grafana configuration

[Anatolii Bazko <abazko@xxxxxxxxxx>]

Hello.

I have some concern about putting a json file into the operator container. I am not sure if it is a good approach.
Should we consider something like metadata container and the files in question there?

On Thu, Apr 23, 2020 at 12:37 PM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:

Hello
I would like to discuss different  opportunities
of the way how we can implement the ability of a che-operator to configure Prometheus and Grafana [1].


To be able to do so we need to embed somehow quite a big file that representing Grafana dashboard json
at this moment this is a single YAML/json ~250kb. But in the close future, we are going to split it to multiple (7-9) dashboards ~50k.

I see such ways to do that:
1. Put jsons to https://github.com/eclipse/che-operator and embed jsons directly to executable. Something like https://awesome-go.com/#resource-embedding
2. Put jsons to https://github.com/eclipse/che-operator and later put it to operator image during the docker build phase.

    After that: configure the operator with the environment variable that points to the folder with jsons.

At this moment I think 2 is better.



[1] https://github.com/eclipse/che/issues/15211 [che-operator] - create ServiceMonitor and GrafanaDashboard when CRDs available and monitoring enabled
[2] https://github.com/eclipse/che/issues/16641 [Monitoring] ConfigMap "che-grafana-dashboards" become too big.

--

Sergii Kabashniuk

Principal Software Engineer, DevTools 

Red Hat

skabashniuk@xxxxxxxxxx    

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev

--

ANATOLII BAZKO

PRINCIPAL DEVELOPER

Red Hat Ukraine