[MAP] Worst state order, acknowledge, planned maintenance
Hello all,
We started using MAP (new web version in 23.04).
However, we notice behaviors that we wish to change.
1) ack and planned maintenance :
Our maps do not consider acks (and probably planned maintenance) although validated in Centreon. All these ack alerts appear as current alarms in MAP by coloring the objects for alarms even if they are ack.
This is annoying, this is not what we want. Even more annoying when it comes to groups of hosts or services.
We want to modify this behavior by considering ack and planned maintenance.
2) Worst state order :
By default, the priority given to the "Unknown(gray)" service status does not suit us.
All of our equipment has at least one service in "Unknown(gray)" status (but generally ack) which makes all of our equipment appear gray.
This is annoying, this is not what we want. Even more annoying when it comes to groups of hosts or services.
We want to be able to ignore this "Unknown(gray)" status in MAP or place it in a lower priority than Ok/Up(green).
Current worst state order in MAP :
Service Critical (red)
Host Down (red)
Service Warning(orange)
Unknown(gray)
Unreachable(gray)
Ok(green)
Up(green)
Pending(blue)
our state order we wish ( editable )
Service Critical (red)
Host Down (red)
Service Warning(orange)
Unreachable(gray)
Pending(blue)
Ok(green)
Up(green)
Unknown(gray)
PS : Also the gray color is "invisible" in the (zoomed) geo-maps.
Thank you very much for all and best regards.
Page 1 / 1
New→Discussion ongoing
to illustrate the problem :
Here we have a little diagram of 5 network devices.
The whole map is considered orange whereas it should be green since everything is acknowledged.
4 devices are colored in gray while all "unknown" services are acknowledged in Centreon. We notice the little yellow-man on the device which means that there is an acknowledgment but we cannot know what it refers to. it's annoying.
A device is colored orange while the service linked to it is also acknowledged in Centreon. it's annoying
By pointing the mouse at the orange equipment, the output pop-up lists several services in "unknown" (again all already acknowledged like we see the yellow-mans next to the gray "U" ) but without even prioritizing the service which has the orange problem...
By clicking on the device (the container) the sub-page displays all the services including the only one in orange, this one (seem prioritized first being at the top left), except that unfortunately no indication mentions that it is already acknowledged.
while in Centreon this service is already acknowledged.
At the end, the device, the device group, the service group and even the entire map are orange for 1 service already acknowledged when everything is fine and everything should be green so that no one is worried unnecessarily and waste time on.
We hope that the maps can take into account acknowledged status and we hope that the priority of "unknown" can be redefined since a service in status unknown is not a problem.
unknown is just garbage status that should not disturbe the green status.
Thanks a lot
Hello all,
With regard to scheduled maintenance and MAP, I note that MAP clearly provides false information.
As you see in this red diagram (which should be green since everything is ack) a device has the maintenance logo
By pointing the mouse at the device, the device status appears UP with a maintenance logo.
It is possible to find the description of this scheduled maintenance to later view its status.
When entering in the sub-page of the device (the container), no service displays a maintenance logo. (but the gray services should have an acknowledged logo).
But the service status also display this scheduled maintenance logo in reference to that recorded entry on 2023/10/16 14:38:19.
Although this maintenance has been finished for several days
Indeed, in Centreon neither the host or the services are in maintenance and the old programmed maintenance "Etape 04" is also completed.
in conclusion, the scheduled maintenance displayed here by MAP are false and the acknowledged status are not taken into account.
It is necessary that these points be quickly improved, the MAPs do not correspond to what they must show.
My users cannot properly use MAP as is.
We cannot trust the status displayed by MAP, all alarms and status need to be rechecked which wastes time and worries for nothing.
Thanks a lot.
Hello Centreon,
here is a new demonstration that MAP is not sufficiently synchronized with Centreon.
I created demo maps for internal use, with the aim of integrating up to 8000 hosts into MAP. But for the demo including some fictional hosts.
The fictitious up hosts (loopaback) are up and the same for the down ones (false ip), everything is ok for the moment.
BUT, as soon as I deactivated all these hosts, they remained visible in the MAP with the last status up or down while Centreon no longer monitors them since they are all deactivated.
However, by deleting a host in Centreon it correctly disappears from the map.
Unfortunately illustration screenshots cannot be uploaded, the-watch error when uploading png files.
Thanks a lot.
Discussion ongoing→In Backlog
Dear @rchauvel ,
I allow myself to return for news about this idea.
These small improvements/corrections of the behavior of MAP requested here become extremely urgent.
Do you want me to split into 2 new ideas the 2 subjects of this one and you transfer all the votes ?
Thanks a lot for your feedback
Hello @jstager,
Let me re-check all of your issues, I will soon come back to you with feedback on each point you mentioned.
