New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Is this technically cgi? I mean, does it have built-in web server?
I think it is just what's mentioned on GitHub:
From how I read it, if you don't care about:
Then running it as a container is probably fine. I'm not sure what @lukast__ meant by "initial configuration is limited", besides the default admin password?
Small update: I've received multiple bug reports, and the server (v1.2) should now also work with Caddy as reverse proxy (because Caddy, unlike nginx, sometimes sends the request in multiple writes).
And sorry for the late responses, I wanted to release the new version as fast as possible (while still testing it beforehand, of course).
No, it's basically just a web server that needs a reverse proxy for TLS termination.
Yes, basically this, Docker has four main disadvantages for LTstats:
Of course it can still be used, a friend of mine does that because he prefers the extra isolation over the lower disk usage, but a manual migration/conversion may be necessary for a future release.
It's really cool. Thank you for your great work!
@lukast__ you trst the application yourself?
Talk about it.
I always have customers/ clients live test for me
LTStats its really great, I love it.
https://stats.neoon.net
Nice job! Looks great!
Cools I must try this
Have you considered adding a "bar" option? As I see, the default option is to get a single point of data every 60 seconds (I only skimmed the code). But this is not really representative of the actual performance over that minute. You could check say once a second and save the min, max, and average for that minute or check even more frequently. I don't think this would be a complex addition, but it'd provide a lot more insight.
So you're still sending your data only once every 60 seconds, but it'd just have 3 datapoints instead of 1 (min, max, avg).
Nice, I will give it a try now.
Thank you
looks clean.. nice work
First of all: thanks for the suggestion, I certainly appreciate it.
I don't know if you saw that, but currently it saves the averages for each minute for CPU usage, disk IO and network traffic (and not only a snapshot at one point in time). Only for the RAM/swap/disk usage that isn't easily possible.
However, TBH, I don't think that a one-second CPU usage spike is that meaningful, and just theoretically, if I were to add min/max for each minute, it would increase the CPU usage for the data collection part of the agent significantly, the storage usage would triple, and drastic changes would be necessary for the agent, the server, and the frontend, and all that for an IMHO rather small improvement.
Also, the sampling interval can be decreased rather easily (
CONFIG_MEASURE_EVERY_N_SECONDSinconfig.h) (this isn't what you suggested; it then uploads the data more often, just thought it's related a bit).Given those things, sorry, I don't think this will get implemented.
And also thanks to all who reported a bug, asked me questions or suggested things that could be improved.
Nice tool! Been using it but one feature I would like to suggest is to be able to add Windows as client
Easy to modify the agent, so it also includes additional drives in the stats, which is nice.
https://stats.neoon.net/monitor/d2aaee63eb955988bbeca1ba49696f69
You just include the mount point and you done.
great work !
Absolutely fabulous! I have to run it on a $7 "baby".
Nice job!!! check this
https://github.com/komari-monitor/komari