Hi @alexandrearmand ! Sorry your answer somehow simply escaped my attention, and some days later I paddled into other waters. But now I noticed my absence.
Thanks for the detailed idea what is first time seemed a bit different as my planned use case, but on second time I noticed the potential of it as an idea.
Let me tell a very simple sample case:
We have a simple ‘load’ graphs/panels of any of our (usually ‘web’)servers. Nothing special, just the basics. There are lot of other panels with such and so data, integrated standalone, etc, but all of them shows me only any of the characteristics of the server and its services, but not our very own and in some sace scheduled activity. I mean I see nicely all basic services, as SQL, Apache, etc, but not some of specially, ‘manually’ handled processes like backup, virus scanning etc. These services basically not the strictly business required services what we already have on our dashboards but like ‘special solutions’ only for the operation background. Of course we could make scripts for all of them to show suach and so characteristics but as our main business is not the high level operation, we have no time, capacity, staff for it. The idea of the sceduled annotations came for me from those reasons. If I could simply configure them, I should not ask my developers to sophisticate all of our processes to the required level just because of the monitoring.
But what you showed me is a bit ‘thought-provoking’. I really like you Gants, but it simply flashed into my mind that with correct value mapping, and with almost just one very simply script we could ‘log’ all of our special and scheduled cyclical processes ‘into’ one normal graph, where the levels could show the corresponding services which could be translated by the Grafana config to real ‘service names’, and could show their time course, like your Gant charts. It could be really simple with ‘running’/‘not running’ states, where the running states could be different levels by the corresponding service.
If I just would like to check what could be the reason of any pike of the load, along with all the already available service data I could compare them with the mentioned ‘operational tasks’ graph.
It is really simply and easy, even me but my developers could prepare it’s background.
I have to compare 2 or more graphs as currently also what could beeasier with ‘integrated’ annotations, but not so bad, so basically acceptable.
Thanks for your answer which guided me to a very simply but acceptable direction!