News for hackers. Stuff that matters.

degio

Re:Grafana 4.0 with alerting is released on Wednesday November 30, 2016 @01:00AM (#13068798)
Re:Vizceral Open Source on Wednesday August 03, 2016 @11:12AM (#12218508)
It's not Open Source, but the sysdig cloud dynamic topology map does pretty much what you describe https://sysdig.com/product/.

(Disclosure: I work at sysdig)

Re:50 Shades of System Calls on Wednesday July 20, 2016 @11:03AM (#12129537)
author here. Please take a look at the solution proposed in this issue https://github.com/draios/sysdig/issues/599. If it doesn't work for you, feel free to comment in the issue.
(one of the authors here)

Yes, this currently emits to file or syslog and you need to take care of the alerting. Of course, this is the very initial release and we plan to improve it. If you have a specific need or idea, feel free to open an issue or let us know on the mailing list.

Re:Lessons Learned from 30 Years of MINIX on Sunday March 06, 2016 @06:56PM (#11236255)
off topic but I think interesting: Andy Tanenbaum is also the creator and maintainer of http://www.electoral-vote.com/, which I find to be one of best resources on american elections.
Re:50 Shades of System Calls on Tuesday February 23, 2016 @06:16PM (#11163167)
Blog post author here.

Yes, when you drill down using the mouse you will get the relevant system calls, including the buffers if they are I/O reads and writes.

Also, sysdig and csysdig have pretty advanced system call capture and filtering functionality. See this link for an introduction https://github.com/draios/sysdig/wiki/Sysdig%20User%20Guide

Re:Moving on from Picasa on Friday February 12, 2016 @09:00PM (#11092061)
by the way, I can find a million alternative cloud based photo services, all with comparable features. On the other hand, there are very few desktop picture managers, especially on windows and linux.
One of the tool authors here. The answer is "it depends". We absolutely designed sysdig and csysdig to work on production systems. They both work by capturing system events, so their cpu usage depends on the number of system calls in the system. On machines with average workloads, I would expect csysdig's CPU usage to be comparable or slighly lower than htop. On machines that do a lot I/O, the CPU will probably be higher. Memeory usage is typically some tens of megabytes.
Re:Visualizing AWS Storage with Real-Time Latency Spectrograms on Wednesday January 28, 2015 @02:17AM (#8958552)
Yes, I did pre-warm the volumes before using them.

And yes, there are several interesting workloads that I didn't test, including read only and read+write. It's potential material for another blog post.

Re:Visualizing AWS Storage with Real-Time Latency Spectrograms on Tuesday January 27, 2015 @05:18PM (#8956455)
OP here. Unfortunately the ansi palette is pretty limited so I didn't have a lot of flexibility in the color choice. That said, this can definitely be improved. I can work on it if people find it useful.

In the meantime, it's very easy to tune the colors your own: just modify this line https://github.com/draios/sysdig/blob/master/userspace/sysdi... in your local version of the script, using this as a reference http://misc.flogisoft.com/_media/bash/colors_format/256_colo....

Older »