New on LowEndTalk? Please Register and read our Community Rules.
ServerStatus! Suggestion Time!
As many of you know, I am that loser that rebuilt ServerStatus. This simple web based status monitor is self hosted, and I was wondering if any of you lovely low end users would like to push some suggestions to improve your experience with it.
You can see it in action here: https://uptime.munroenet.com/index.php
- Change config format for easier usage.
- Delete outages page, as seriously who uses that?
- Slimming of code!
- Making it uses another API/Query method for info.
- Just saying fuck it all, and it is good as it gets.
- Just start a new project, which is what I likely should do.
Thanked by 1raynor
Let me give this a try and see where it leads me to
maybe a function that can list CPU / RAM / HDD usage from less to more and reverse ?
Do you cache the data or can it be used for fancy reflection attacks?
I challenge you to get rid of PHP...
What language would you recommend? Before we get rid of php.
Php is ok really. But writing it using js would be great. Also some feedback
Login functionality so people can choose which ines to show publicly
Keep the outage page and add some sort of spoiler on each server that you can expand/collapse to check on outage information
More info on resource usage to be added as spoiler.
Basic auth on api
Very minor, the UI can be much much more beautiful with some css work
This was more of a joke, as PHP works fine for what you're doing. Most analytical stacks are moving towards java, with distributed databases on the back for retaining data points.
Back in the day, PHP + SQL = win, but those times have changed with the limited ability of single threads.
Good enough for simple and public monitoring
I like the version where you can expand the details, not just percents (sometimes I don't remember my ram/disk details).
Maybe modify this loser's stuff, no php needed:
Disclosure: I may or may not be an acquaintance of this person
You request the status from each server like so:
I'd suggest you request them per server individually ... like SERVER1.munroenet.com/.... All subdomains can still point to the same A-Record.
Because this way the concurrent connections are not limited by per host rule in browsers.
We could also enter 2017 and use http2
So MySQL is not single threaded - and if you build your application in such a way that it only uses one PHP process - then it's your own fault.
PHP scales perfectly fine, if you know what you're actually doing.
Perhaps being able to disable certain options from being viewed publicly? HDD, Load etc.
Only ~ 60% of all browsers support http/2 yet. So no, thats no option.
Where did you get that strange number? And why would it be a trouble anyway?
Not really defending http2, just trying to grasp different point of view.
PHP works fine, if you know how, you can split tasks in php into multiple threads, like I do in Night-Sky to keep up the 10s interval.
Same for MySQL, as long you are not doing tons of table scans.
Uhm - 83.18% of supported browser versions.
Not sure what stats you're looking at - but if I take stats based on billions of requests, remove bots and crawlers (since we don't care about those anyway), then of https enabled sites - the http2 traffic is about 94%
So sure - 60% :') LOL
Get better stats mate.
You can enable http 1.1 and http 2 at the same time, so I do not see the point of the discussion.
Depends on the site actually. I'm running sites with visitors even lower with 60% http2 enabled. Also i got a site where http2 is a must-have. So yea, my comment wasnt ment to be final but more like "Not everyone has it - yet".
Oh my! I will read through all of these this weekend, and get back to everyone.
This might be possible, but might be changing quite a lot. Would you mind your screen shuffling the data a lot?
Yes, my serverstatus has a cache using either APC first, and secondly a flat-file store.
Thank you! I don't think I will do login functionality as that is too much for the goals of this project. LibreNMS or Observium already do those things, and far better. However, the rest I think I can easily do.
CSS is totally not my specialty, though.
This is already happening, it checks every 10 seconds on my default config.
I am confused by this request. I know of the browser limitation, but are you suggesting I have everything go to a completely separate domain for each server?