netdata 1.5 released - big update!
-
How do I see my servers taht are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them? The purpose of a central console is so that I have one place, one secured place, to go view them. If each machine has its own dashboard, I have to get every one of them out on the Internet so that I can view them?
-
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
-
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So that acts like a proxy server? What does its interface look like?
-
@scottalanmiller said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So that acts like a proxy server? What does its interface look like?
that's not the way I read it. The central registry appears to just be a list of what other machines you can 'surf' to.
-
@Dashrender thats correct
-
@aaronstuder said in netdata 1.5 released - big update!:
@Dashrender thats correct
But this doesn't answer Scott's question - If I'm at home, how do I access servers I won't want published to the internet?
-
@Dashrender said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@Dashrender thats correct
But this doesn't answer Scott's question - If I'm at home, how do I access servers I won't want published to the internet?
SSH jumpbox?
-
@dafyre said in netdata 1.5 released - big update!:
@Dashrender said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@Dashrender thats correct
But this doesn't answer Scott's question - If I'm at home, how do I access servers I won't want published to the internet?
SSH jumpbox?
sure, but that's outside the scope of the product/project, making the project just that much harder and less worth while.
As scott said, if you're already managing a central stat server, you gain your secure access to it, and it shows you everything for all servers, so what does this project do for you?
tracking those thousands of collection points is probably not needed in most production environments - if it was, then the company would probably have already solved that issue.
-
@aaronstuder said in netdata 1.5 released - big update!:
@Dashrender thats correct
So they would be blocked, right?
-
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers taht are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them? The purpose of a central console is so that I have one place, one secured place, to go view them. If each machine has its own dashboard, I have to get every one of them out on the Internet so that I can view them?
I can't even think of 1 server (that I have) where I would this level and speed of real time data let alone 1,000. I know they are out there but I know I don't have any. SNMP and collectors give me way more info than I can use and allow for central monitoring. This seems like a super niche product that could have security implications.
-
@stacksofplates said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers taht are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them? The purpose of a central console is so that I have one place, one secured place, to go view them. If each machine has its own dashboard, I have to get every one of them out on the Internet so that I can view them?
I can't even think of 1 server (that I have) where I would this level and speed of real time data let alone 1,000. I know they are out there but I know I don't have any. SNMP and collectors give me way more info than I can use and allow for central monitoring. This seems like a super niche product that could have security implications.
On Wall St. we needed this from time to time, but we wouldn't want it running or exposed normally. Very rare, even there, though. Only .1% of servers, literally. For normal needs, what we need is roughly:
- Centralized viewing
- Security
- Data collection away from the source device
- Historical viewing
-
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So can anyone see my data? This is the point I don't get. Why would I want my servers uploading data to a "Dashboard" anyone can see.
I want to monitor my servers ..... just me.
-
@scottalanmiller said in netdata 1.5 released - big update!:
- Historical viewing
I think this is the big one where it fails (excluding security). It's only real time data, and no history. So you need two separate monitoring solutions.
-
@hobbit666 said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So can anyone see my data? This is the point I don't get. Why would I want my servers uploading data to a "Dashboard" anyone can see.
I want to monitor my servers ..... just me.
I think the central registry in this case is something you build, something you control - but I could be wrong.
and if I am wrong - holy cats - you're right and that's crazy!! -
@Dashrender said in netdata 1.5 released - big update!:
@hobbit666 said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So can anyone see my data? This is the point I don't get. Why would I want my servers uploading data to a "Dashboard" anyone can see.
I want to monitor my servers ..... just me.
I think the central registry in this case is something you build, something you control - but I could be wrong.
and if I am wrong - holy cats - you're right and that's crazy!!So yeah I like the look of it but without knowing where the data goes as well is a NO from me.
-
@Dashrender said in netdata 1.5 released - big update!:
@hobbit666 said in netdata 1.5 released - big update!:
@aaronstuder said in netdata 1.5 released - big update!:
@scottalanmiller said in netdata 1.5 released - big update!:
How do I see my servers that are not on the Internet, for example? Let's say I have 1,000 servers, how do I view them?
From the central registry.
So can anyone see my data? This is the point I don't get. Why would I want my servers uploading data to a "Dashboard" anyone can see.
I want to monitor my servers ..... just me.
I think the central registry in this case is something you build, something you control - but I could be wrong.
and if I am wrong - holy cats - you're right and that's crazy!!Yes, appears to be just wide open and requires each node to be wide open. So a massive security nightmare. You can, of course, always layer security on top yourself, but who wants to manage that mess?
-
Security:
Yes netdata listens on whatever interface has network connectivity, but it does not access anything outside your network to transmit data, and does not forward any ports to itself using UPNP or NAT-PNP. The only way this would be open to the world is if you set up a port forward. It is not "open to the world" if you install it on a public facing server unless you have no firewall set up on the machine. That would be your own problem, and not one for Netdata to solve.
"netdata keeps all the data on the server they are collected." from their Wiki since nobody here read it.
Centralization:
There are already a ton of products out there that harvest monitoring data from agents and put it in a database on a central server. If you like that model, then go use it. This is not that, and was never designed to be that. It uses cookies and other stuff in your browser to see what other Netdata servers you have accessed (with that browser). That data (stored in your own browser) is used by the netdata dashboard on any of the servers to build a jumplist so you can jump to those machines from within the WebUI. If you REALLY want a centralized place to dump data from all machines, you will have to use the features from this latest release to ship data to Grafana, or some other visualization stack. If you bothered to read the release you would know about the Backends they support:
"netdata supports data archiving to backend databases:
Graphite
OpenTSDB
Prometheus
and of course all the compatible ones (KairosDB, InfluxDB, Blueflood, etc)" - from the wikiAgain, this is all information that can be gathered by reading the release, and the front page of the Wiki. I have only used Netdata on one machine so I am no expert so don't ask me to explain things in more detail. Shit, this post was probably too long for you so I'll make a TL;DR for those who have the attention span of a doorknob.
TL;DR RTFM and stop crying.
-
lol
-
or go here and start reading.
https://www.reddit.com/r/sysadmin/comments/5pvg5n/netdata_the_opensource_realtime_performance/ -
@cgunzelman said in netdata 1.5 released - big update!:
TL;DR RTFM and stop crying.
No one is crying, we are trying to figure out the good use case for it, especially as its security model goes against modern LANless design and explicitly goes against the normal security approach of the OP, so we are all very confused as to why he likes it and why he would use it and what the benefit is. We've definitely read the manual, and that just solidified our confusion. We were aware that you can collect it into something else, but most of those tools already have their own collection. It's from reading the manual that we are left unsure what the benefits are outside of super low latency monitoring environments that you would not find in most environments.
It seems like an itch without a scratch. But as someone who uses it, what is the use case for distributed, non-centralized monitoring and how are you tackling the security implications of having it be wide open and does that mean you are relying on LAN security alone and not attempting to use this in a hosted environment?
