grimoirelab-sirmordred
grimoirelab-sirmordred copied to clipboard
chaoss
Create a kibiter section in mordred.cfg
When #80 is merged, we will have two separate kinds of information in the panels section: information about the dashboard (such as the default index pattern, or the default time period for the dashboard), and about the infrastructure supporting it (Kibiter url, for example).
I propose to split that into two sections: panels and kibiter. The first one about stuff which is directly related to the dashboard, and the second one stuff which would reflect details of the infrastructure, related to Kibiter, that could change in different deployments of the same dashboard, not affecting the dashboard itself.
For now, the new parameters introduced in #80 would come under kibiter.
With some delay, I like the idea! In addition, this can open the door to a better management of the panels (archimedes). @sduenas wdyt?
even if we use ODFE, Kibiter (adapted to ODFE) would always exist or I'm missing something?
Let me clarify my view. If I want to run GrimoireLab without "Kibiter", but with a vanilla Kibana from ODFE or Elastic, what do I need Kibiter related actions (like menu set up) for?
AFAIU the kibiter section should contain just the infra info (url of the instance, default index pattern). Both things are not kibiter-specific, but provided by kibana. Panels info should go to another section (panels).
Let me clarify my view. If I want to run GrimoireLab without "Kibiter", but with a vanilla Kibana from ODFE or Elastic, what do I need Kibiter related actions (like menu set up) for?
A couple of questions @jsmanrique
What does ODFE stand for?
I understand you would like to disable the menu and to enable just the upload/publication of the Kibana dashboards. Is that right?
ODFE = Open Distro for Elasticsearch
That's it. Thank you @GeorgLink
AFAIK, Elasticsearch is a TM owned by Elastic, so I am trying to save words and since Elastic is suing AWS for using the name, I think it might be wise to use the acronym until the situation gets clear.
Regarding your other question @sanacl, yes, I am foreseeing a scenario where you have GrimoireLab to collect data and produce ES indexes, and potentially some reference Kibana dashboards or panels, and instead of using Kibiter container I would use my own Kibana flavor (let's say ODFE). To make it work nowadays I need to set panels phase to false, so there is no menu upload, but there is no index pattern set up neither. So, I need to go index by index creating its index pattern.
To make it more clear, I would like GrimoireLab becoming just a data generator, with the data stored in ES. But able to use other visualization tools like Kibana, Kibiter, Graphana, etc. easily.
What do you think?
To make it more clear, I would like GrimoireLab becoming just a data generator, with the data stored in ES. But able to use other visualization tools like Kibana, Kibiter, Graphana, etc. easily.
What do you think?
The task of allowing Mordred to have different jobs to do what you want is simple. The aim of using different visualizations tools is a wise move I think.
So, in order to do what is requested in this ticket we could:
- split kibiter and panels phase as @jgbarah requested
- add the menu parameters to a new section or at least move it to panels section. In both scenarios a parameter to disable it must be added