Server and domain monitoring tool I made

[nixstats]

For the past months i've been working on a website and server monitoring tool. I'm trying to keep it as simple to use as possible. Adding a server to your dashboard is as simple as running a single command (no need to add the server on the site, it's one code for all your servers). For website monitoring the only thing you need to submit is the domain name.

Everything on the panel is of course only accessible to your but there is an option to create a public status page or even multiple status pages (status page X with server A and B, status page Y with server C and D). Here's an example of a public status page

I'm currently running a private beta and looking for some more beta testers, if you have any domains and/or servers that need monitoring send me a PM and i'll send you an invite code.

Here are some more screenshots; https://nixstats.com/sc1.html https://nixstats.com/sc2.html https://nixstats.com/sc3.html

 

[drmike]

Wowzers, that looks nice!

 

[Nett]

Sounds interesting, will this be available as a self hosted solution?

 

[Enterprisevpssolutions]

Looks good, how far back can you look at the stats?

 

[robbyhicks]

You've got a PM!  This looks cool

 

[k0nsl]

I'd be interested in this project. At a glance, I found it quite clean and immediately gives one a clear overview of the essential/s - just as it is supposed to do. Good luck with the project.

Could you perhaps tell us more about the specifics of it? Nothing too detailed, but a somewhat specific run-down of the ins-and-outs, what it is written in and if you're using any framework. Et cetera.

Details are always interesting.

Again, good luck. It looks promising!

 

[nixstats]

Wowzers, that looks nice!

Thanks

Sounds interesting, will this be available as a self hosted solution?

Probably not. I'm trying to make it as simple as possible, it's currently setup with php, mongodb, node.js, and some shell scripts. Unless I get a lot of requests for self hosted version.

Looks good, how far back can you look at the stats?

Stats are not pruned so for now I'll keep them forever, this was a problem before but since mongodb 3 which has compression it's much easier to keep a lot of stats online.

You've got a PM!  This looks cool

Send you a message with the invite code etc.

 

[rmlhhd]

I'd like to request a self hosted version (willing to pay a small amount), looks good.

 

[That IT guy]

Looks awesome but https://nixstats.com/sc1.htmldoes not seem to work.

 

[nixstats]

I'd be interested in this project. At a glance, I found it quite clean and immediately gives one a clear overview of the essential/s - just as it is supposed to do. Good luck with the project.

Could you perhaps tell us more about the specifics of it? Nothing too detailed, but a somewhat specific run-down of the ins-and-outs, what it is written in and if you're using any framework. Et cetera.

Details are always interesting.

Again, good luck. It looks promising!

Thanks! The app runs on php5, mongodb some node.js and shell scripts. Currently not using a framework, probably will be using laravel for the next version. 

I'd like to request a self hosted version (willing to pay a small amount), looks good.

Sorry for now there will not be a self hosted version.

Looks awesome but https://nixstats.com/sc1.htmldoes not seem to work.

Should work but the image is large, will take a while to load on slower connection.

Anyways I decided to make one invite code for vpsboard.com, you can sign up at https://nixstats.comwith the invitation code VPSBOARD

I'm wondering why is everyone so interested to have this as a self hosted solution? Aren't you better of having someone else host it and taking care of notifications etc? Is it a privacy issue? In a few weeks i'll also have a non root monitoring agent.

 

[Nett]

I'm wondering why is everyone so interested to have this as a self hosted solution? Aren't you better of having someone else host it and taking care of notifications etc? Is it a privacy issue? In a few weeks i'll also have a non root monitoring agent.

Why would you give your server data to someone else? What if the database leaks?

 

[comXyz]

Why would you give your server data to someone else? What if the database leaks?

I think what he is making is similar to NodeQuery, there will be simple install script, you can open the script and see what info the monitor agent sends out.

Awesome UI @nixstats

 

[nixstats]

Why would you give your server data to someone else? What if the database leaks?

Privacy and security are just as important to me as they are to you. I give you the option to either monitor your own domains and servers or let me help you doing so.

I think what he is making is similar to NodeQuery, there will be simple install script, you can open the script and see what info the monitor agent sends out.


Awesome UI @nixstats

Thanks! Yes it is similar to nodequery, the agent is open source. Currently the agent/installer are hosted on nixstats.com but will be moved to github later.

There are still some issues/bugs with the agent (depending on your servers os) that will be resolved this week.

 

[joepie91]

I'd not recommend using MongoDB. is why.

 

[nixstats]

I'd not recommend using MongoDB. is why.

You should never run mongodb on a 32 bit os in production. As for data integrity, i have read about that but it mostly came down to people not running it in the right setup (read the manual . MongoDB did used to write/update silently/blindly but since about a year it does (before you had to use writeconcern).

I wouldn't say it being non-relational is a "problem". I guess you could store all in a relational matter but that doesn't mean that's always the ideal way to do things.

 

[joepie91]

You should never run mongodb on a 32 bit os in production. As for data integrity, i have read about that but it mostly came down to people not running it in the right setup (read the manual . MongoDB did used to write/update silently/blindly but since about a year it does (before you had to use writeconcern).

I wouldn't say it being non-relational is a "problem". I guess you could store all in a relational matter but that doesn't mean that's always the ideal way to do things.

The 32-bits limit is dumb and purely a result of the design decisions made by the MongoDB developers (for "performance" - which as of yet is a completely unproven claim, as far as I am aware). Data loss was primarily because of poor default behaviour, and if the disregard for data integrity has been so bad in the past, I don't see why it would suddenly be better now - it's still the same developers with the same mindset. Not to mention that if you actually use MongoDB for its advertised purpose - a sharded, multi-system setup - it's not only a pain to maintain but will also very easily lose data, something that is described at length in one of the articles I linked. It being non-relational is a problem if your data is relational - which almost all data is.

All this on top of the fact that there is nothing that MongoDB is particularly good at, not even its commonly advertised features.

No, MongoDB is not a good choice. Some things are just objectively poorly engineered, and MongoDB is one of them.

 

[nixstats]

The 32-bits limit is dumb and purely a result of the design decisions made by the MongoDB developers (for "performance" - which as of yet is a completely unproven claim, as far as I am aware). Data loss was primarily because of poor default behaviour, and if the disregard for data integrity has been so bad in the past, I don't see why it would suddenly be better now - it's still the same developers with the same mindset. Not to mention that if you actually use MongoDB for its advertised purpose - a sharded, multi-system setup - it's not only a pain to maintain but will also very easily lose data, something that is described at length in one of the articles I linked. It being non-relational is a problem if your data is relational - which almost all data is.

All this on top of the fact that there is nothing that MongoDB is particularly good at, not even its commonly advertised features.

No, MongoDB is not a good choice. Some things are just objectively poorly engineered, and MongoDB is one of them.

mongodb has improved a lot and 3.0 has huge performance increases, also setting up a sharded cluster is a lot easier when using MMS. I suppose you're a postgresql fan their seems to be a lot of heat coming from the postgresql crowd

choosing a database is also a personal choise, some programmers prefer postgresql others prefer mongodb, all depends on your way of thinking/solving problems.

 

[joepie91]

mongodb has improved a lot and 3.0 has huge performance increases, also setting up a sharded cluster is a lot easier when using MMS. I suppose you're a postgresql fan their seems to be a lot of heat coming from the postgresql crowd

Benchmarks please.

choosing a database is also a personal choise, some programmers prefer postgresql others prefer mongodb, all depends on your way of thinking/solving problems.

If you consider choosing a database a "personal choice" rather than a technical decision, then that's a problem.

 

[Amitz]

Don't listen to joepie91. He's a bad boy who brushes his teeth only every second day and hangs around with dubious people outside in the dark. ;-)

 

[nixstats]

Aah I see well time to get back on-topic then ;-)