-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show up/downtime with name only when less than 1day (Default view) #111
Comments
I would definite say that having an option to show X hours or days because it would quickly highlight those that have changed. On my small 21" monitor, I can see 16 x 8 devices so that's quite a few in one go with the time being displayed. |
For now I just hardcoded out whole uptime/downtime variable from monitor.php file. When there is a change I get Cacti reboot raport on my mail so it isn't so necessary for me - but would be great to show this in UI for these devices. |
I would prefer a dropdown to say: Down for < 1 Hour Comments? |
It's ok. |
It seems that this issue was resolved. @interduo - could we close this issue? |
@xmacan could You show me the commit that resolves this issue? |
@interduo could you show me any screenshot of your problem? I cannot see problem in default view with actual version. Maybe I only don't understand where the problem is ;-) |
Uuuu I saw that I made this issue 5Y ago time is going really fast... i will test it again on newest version. BTW cacti got a demo portal somewhere? |
We haven't any demo portal. Maybe it isn't bad idea @TheWitness |
Well, that could be a lot of work. We would need to containerize it from a running system and host it somewhere on demand for each new session. |
The time nearby icons below names takes too much space in default view.
It would be better if:
We show only time when is down or less than XX hours for example 2 hours (it should be configurable) or just option "don't show up/down time".
Now the information isn't usefull - You can always point to mouse and see uptime.
The text was updated successfully, but these errors were encountered: