Ha yeah - we opened up a port in iptables for this so we don't have to ssh tunnel in to see stats. Obviously, if you're concerned about exposing numbers, you can view via an ssh tunnel instead of opening a port.
Not these guys, but doing realtime viz of signals.
We've switched over to a minimalist canvas renderer--if you don't need interactivity or styling, and instead just "draw me as much as you can as fast as you can, damnit.", we hope it's the way to go.
I've been playing around (http://yield.io) with Flot, which uses canvas and rendering speed seems pretty good, but resizing gets a bit wonky when there are multiple canvas elements on a page.
Yeah, we started with Flotr2...too many graphs on a page (with thousands of datapoints per graph) brings Chrome to its knees, even with auto margins and whatnot turned off.
@angersock That's a good point on the number of points. If I downsampled the yield history to monthly yields, that would probably help the performance.
2.6.32 is one of the longterm maintenance releases; it's still supported and new security patches are backported. If you rent a freshly imaged RHEL/CentOS server today, that's the kernel you'll be getting. Pretty much all the software packages those distro's come with are older, longterm/stable releases, never bleeding edge.
The use of man in this context is androgynous. It's merely an abbreviated use of "mankind," which is an abbreviated use of "humankind." I'm sorry if you're upset by this wording, but it's not inappropriate.
Note how all of the results are all about men and manliness, which is fine for gendered products and clothing, but doesn't really make sense for a piece of server monitoring software.
i think whats interesting is that people who use sentences such as "for the modern man" don't think about man as male at all and don't intend to offend anybody.
It's only picked out by the ones who feel oppressed by gender issues (which are often males defending females - in fact, genetics also makes us behave that way, ironically.)
Of course they don't think about, and obviously they don't want to offend, and that is why some good people point this out, so that people think about it and pay attention. Sometimes biases are so entrenched that we don't feel them. They feel natural, and therefore neutral. But, if you want to make a change, than it's precisely those seemingly natural things that you need to change.
You can keep using "man" or not, but I think it's helpful to pay attention.
Frankly, i think some people just like to complain about gender issues when there isn't much going on.
In some languages (ex: french), everything defaults to male-centric. Nobody cares or feels offended by it, and females have exactly the same rights as males.
Feminism isn't just about not offending people or giving women the same "rights" as men. You can make the (true) claim that blacks in America have the same rights as whites. But does that mean that there's no more racism? And even without the judgmental word "racism", does that mean blacks have the same opportunities as whites? I don't think so.
Feminism is about making sure women have the same opportunities as men not only by virtue of the law, but "on the ground"; that society doesn't gently (or not so gently) steer them in directions where they end up with less power than men; that they're no longer objectified and that female politicians are not called by their first names.
I'm not saying language can fix all that, or that it even matters all that much. It certainly matters less in cultures where feminism has had greater success. But it is a good place to point out how, perhaps inadvertently, we keep falling into the same gender traps. If you start thinking about your choice of words, language becomes less natural, so you stop treating it, and the culture it articulates, as "nature", and start treating it as the malleable social construct that it actually is.
No, you're right... it's not inappropriate. But really, something like "for the modern admin" is more appropriate and should be used. There is no need for the "modern man", so it should be left out.
The phrase of "modern man" was meant to contrast with old-school admins. For me, it brought up images of classic admins in server rooms either your straight-laced IBM types or your Berkeley Unix neckbeards. Take your pick, but they were both predominantly men.
> It's merely an abbreviated use of "mankind," which is an abbreviated use of "humankind."
"Humankind", "Mankind" (and "man" when used in a sense that is semantically-equivalent to the other two) are mass nouns that do not take articles ("the" or "a"). In the case of "humankind" or "mankind", using an article is just plain incorrect (consider, "one giant leap for the mankind" vs. "one giant leap for mankind"), whereas for "man" the use of an article can distinguish between the sense of "an individual adult male human" and "humankind" (consider "the story of man" vs. "the story of a man".)
So, no, in "for the modern man", "man" doesn't work as a shortened form of "mankind".
Only reason I didn't file a PR myself was I wasn't sure what the best replacement would be (dev? sysadmin?), but this should be easy enough to fix if they're amenable.
I agree with this. I know "for the modern man" is an idiom, but I think it's better to be overly conscious about this stuff. Would you lose anything by saying "for the modern dev"?
Have you thought of writing the metrics collection part (and eventually the whole thing) in Go? You would get the stand-alone distribution right away and would keep people from installing any extra dependencies.
We've clocked the CPU usage of the scout_realtime daemon at 1% on an Intel Xeon 2.40GHz CPU. Memory usage is around 22 MB. If you turn off the metric collection (by clicking the pause button on the web page), CPU usage will effectively drop to 0%, and you'll still be able to visit the web page and re-enable metrics at any time.
The word "manhole" is not a fair comparison. In that case they were dealing with an inanimate object. In this case, we're labeling any developer who would need this tool. Hence the inappropriate use of gender.
I'm assuming you're going to disregard their comment because of their gender? What does it matter what gender the parent comment poster is? They should have a voice too...
Ok, it's too late for me to edit, so please forgive my hastily aggressive response. What I meant by it is that it is easy to dismiss complaints about "one-sidedness" if things are tilted in your favour.
Look, I'm all for encouraging more girls in STEM, and all that.
My EE class mostly guys, and I'm sure we lost some diversity of viewpoints because of that.
However, let's just ask nicely once - and then leave it at that.
I would hate this to turn into another silly bike shedding flamewars on HN, where all the Social Justice Warriors come out of the woodwork, for their weekly feel-good topup.
That's the first thing I thought. Please, please change it. Things are difficult enough for women in technology without things like that. I don't care what the rational is. It looks awful, and I'd be embarrassed to show that to women at work.
Just change it to "modern woman" and shut everyone up.
That's the thing now right? Where the english language has left us with lack of a non-awkward sounding gender neutral term we just the feminine version and it's ok. I know, I know, everyone is going to chime in with their version of a 'non-awkward sounding alternative. But the person who wrote this, wrote it, it didn't go to the committee of HN, and that person wasn't out to offend anyone, so ya know, let it go, let live, all that... No? I tried.
ps. My photo-editing skills suck bigtime otherwise I'd do it.
EDIT: Doesn't seem to work properly under FreeBSD-10. No data is displayed. Apparently (as expected) uses Linux ProcFS structure to get data. So FreeBSD for now is not supported, keep the icon for later :-)
This is cool. It looks like the developers are reading the comments so I'll add a quick suggestion. Something that I found to be insanely helpful with my own product development was being able to track memory swapping.
I went to great lengths to tune my Java Virtual Machines so that they would work well in a minimum RAM environment. And being able to track swapping was critical for my decision making. Now I can run my product on a 512MB system with 1GB of swap space with no problem. Below is how I'm tracking swapping in real-time.
Since your solution is focused on capturing a period of time, you'll be able to provide a better view than I am.
With SSD becoming more common for cloud hosting, using swap space in lieu of getting more RAM will probably become more common. And before anybody points out that SSD is still significantly slower than RAM, I know. Depending on your product, using swap on SSD may be practical. I know using swap on amazon's infrastructure wasn't.
I will add that if you keep it as two buttons, the colors should be switched. Right now, the active button is black and the other is gray. But gray buttons say to me that they are disabled, so it looks like I can only hit the play button when it's already playing.
It's always instantly clear when something like iTunes or a Chrome helper starts eating up 105% CPU, and provides quick access to force quitting it. :)
I've recently released a similar tool for Python. Definitely not as pretty but with a focus on providing a lot of details:
https://github.com/Jahaja/psdash
Did you roll your own SVG chart lib for this? If not, mind sharing which one you're using? It's very nice.
If you were to make it so I can open a socket or websocket to it (perhaps on a second, internal port) and publish whatever data I want, that'd be all kinds of nifty. That is, make it so I can just start spraying numbers at ws://myhost:5556/Really%20Awesome%20Data and with that a nice auto-scaled chart magically appears in the dashboard.
Edit: Oh, I see a github ribbon. Maybe you'll see a pull request sometime soon...
Edit 2: Anyone wondering about my original question - the charts are built using the D3 project.
It's not yet in a state for plug-and-play usage in other projects. If you're looking to rollout smooth-scrolling charts quickly, checkout http://smoothiecharts.org/.
Noob to Ruby here...any thoughts on why gem_original_require is screwing me up? Thanks for the cool looking tool!
/usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- json (LoadError)
from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `require'
from /var/lib/gems/1.8/gems/scout_realtime-1.0.1/lib/scout_realtime.rb:23
from /var/lib/gems/1.8/gems/scout_realtime-1.0.1/bin/scout_realtime:4:in `load'
from /var/lib/gems/1.8/gems/scout_realtime-1.0.1/bin/scout_realtime:4
from /usr/local/bin/scout_realtime:19:in `load'
from /usr/local/bin/scout_realtime:19
I think we're talking about the browser side of things. I haven't investigated why, but it pegs the cpu on my macbook pro in Chrome, Safari, and Firefox.
It is burning my CPU (browser side, not server side)
http://i.imgur.com/NgXi4LG.png
The author should provide configuration so it does not get data from stats.json every second.
And I should add that this thing is awesome! It wouldn't install for me unless I was root, but that might be a ruby configuration thing, since this is also the first ruby app that I've ever touched.
It would be nice to have an option to have scout_realtime only listen on 127.0.0.1, so (as someone else already mentioned) we could just proxy to it with another web server and then wrap controls around that.
With my 10 minutes of poking around in the scout_realtime source and a bit of googling, I think the option would go here, in main.rb:
server = WEBrick::HTTPServer.new(:Port => 5555, :AccessLog => [])
I just tried out the main product and while it's easy to setup i ran into snags with the plugins right away. Both redis and postgres (the first two i tried) failed to install and it took a bit of searching to figure out they had their own dependencies. When trying to install those dependencies i ran into issues with compatibility for a fresh ruby install.
Maybe you should concentrate on fixing your own dependency issues before you start pounding on Nagios (https://scoutapp.com/info/nagios_alternative) about the exact same issue.
This looks nice but that /s refresh it might cause issues, maybe add a setting so refresh can be set by user?
Shameless plug - If anyone is looking for a python/django alternative with refresh settings and remote access to the output data as json take a look at pyDash : https://github.com/k3oni/pydash .
Cool idea! The interface is a tad heavy (for me) though, the fans of my laptop spun up.
I noticed that by looking at the memory usage of the ssh daemon, one can determine how many people are connected with ssh. Every open connection (even if you're just idling at the login phase) adds around three to five mb to memory use. I wonder what other information might be unintentionally relayed through these metrics.
I'm glad to see the sparklines. I'm worried that the CPU sparklines in particular are likely to mislead due to the lack of a common vertical axis scale. I suspect Tufte might advise two graphs: one with a fixed 0…100 axis scale, one "zoomed". The former would help you compare CPU history between apps, and sport a shaded background region to indicate the range of the latter.
Regarding "What operating systems are supported?" and the answer of "scout_realtime relies heavily on the proc file system to fetch metrics. procfs is supported on most Linux-based distributions with the exception of OSX and Debian."
procfs is available on my Debian 7 servers, so scout_realtime just installed and runs fine on the few that I've tried it on.
Really nice looking monitoring, though. I think it's fun to see the stats scrolling by.