blog.hartshorne.net
In Search of Updates: March 2015
http://blog.hartshorne.net/2015_03_01_archive.html
In Search of Updates. Setting Nagios Downtime from a script. I don't know why I've never done this until now. Create a script "nagios downtime" or whathaveyou:. Then when you're taking an action (say a backup) and want to programmatically set downtime from within your backup script, just shell out to. Sudo -u nagios nagios downtime db5 check mysql replication 600 'downtime for backup'. For more information look at the Nagios External Command. Keywords: nagios service downtime command line.
blog.hartshorne.net
In Search of Updates: Better Latency Graphs
http://blog.hartshorne.net/2014/02/better-latency-graphs.html
In Search of Updates. Nearly all the systems I've worked with to graph metrics about a system focus on lines. If you want to know about the latency of your site, you often graph average, 50th percentile, and 90th percentile lines representing your load time. This gives you a good idea of what most people are experiencing. I want to see a system that lets me graph a histogram of page load times for every time slice. Here's that site's load time profile:. I would like to see a framework for capturing this ...
blog.hartshorne.net
In Search of Updates: March 2013
http://blog.hartshorne.net/2013_03_01_archive.html
In Search of Updates. Capistrano, nohup, and sleep. So a bunch of the random things that I deploy are not well-behaved services with init scripts and reload targets but random bits like a sinatra app or a hipchat bot. Being internal tools that are pretty stable, the easiest way to deploy these is to just nohup and background the command rather than setting everything up under monit or runit or something like that. But redirecting both stdout and stderr to /dev/null solves that one.
blog.hartshorne.net
In Search of Updates: September 2013
http://blog.hartshorne.net/2013_09_01_archive.html
In Search of Updates. Git lesson of the day (courtesy of Brad). Git rebase, reflog, and force push - the nice way to deal with your own branches and keep a clean git history. Don't do this on branches that other people are working on - the force push does nasty things. In that case, it's better to coordinate, collect changes, make a new branch, whatever. So you've been working on a branch (let's call it. And you're ready to squash a bunch of commits and push it back up to master. Squash all your commits.
blog.hartshorne.net
In Search of Updates: Bandwidth throttling in FreeNAS for external traffic
http://blog.hartshorne.net/2015/05/bandwidth-throttling-in-freenas-for.html
In Search of Updates. Bandwidth throttling in FreeNAS for external traffic. I have a FreeNAS box running in my home. It is the target for my laptop to backup, it has some files I share with Christy, it stores all my photos, and so on. All in all it's great. I recently set up the s3cmd plugin to back up stuff to S3. Despite having redundant disks it's always good to have a backup. It takes days to upload all my photos to S3 but that's fine - it doesn't impact regular use of the NAS. The FreeNAS folks argu...
blog.hartshorne.net
In Search of Updates: Ganglia Web UI Performance Improvement for Large Clusters
http://blog.hartshorne.net/2014/02/ganglia-web-ui-performance-improvement.html
In Search of Updates. Ganglia Web UI Performance Improvement for Large Clusters. There are many transitions people tend to make over time as their Ganglia. Cluster grows in order to maintain performance. Many of them have been covered in other blogs, but here is a brief summary of the scaling steps I usually take, from the initial cluster up through thousands of hosts and hundreds of thousands of metrics. All of these steps successfully scale the ganglia core very well. With redundant gmond processes...
blog.hartshorne.net
In Search of Updates: June 2011
http://blog.hartshorne.net/2011_06_01_archive.html
In Search of Updates. Why I'm running ethernet in my home. 64 bytes from 128.32.136.9: icmp seq=30 ttl=51 time=86.784 ms. 64 bytes from 128.32.136.9: icmp seq=31 ttl=51 time=115.341 ms. 64 bytes from 128.32.136.9: icmp seq=32 ttl=51 time=104.645 ms. 64 bytes from 128.32.136.9: icmp seq=33 ttl=51 time=81.736 ms. 64 bytes from 128.32.136.9: icmp seq=34 ttl=51 time=90.551 ms. 64 bytes from 128.32.136.9: icmp seq=35 ttl=51 time=71.943 ms. Really, though, the latency and consistency are what I appreciate.).
blog.hartshorne.net
In Search of Updates: Removing Accidental Chef Attributes
http://blog.hartshorne.net/2015/03/removing-accidental-chef-attributes.html
In Search of Updates. Removing Accidental Chef Attributes. If you've accidentally set attributes on a bunch of nodes in a way that breaks your system, you want to delete them. This can happen when you accidentally include a cookbook you didn't mean to and have some attributes set in the attributes/default.rb file. Here's how to fix it:. Note: replace the nested array format with underscores. In other words. My bad attribute name. Subscribe to: Post Comments (Atom). Setting Nagios Downtime from a script.
blog.hartshorne.net
In Search of Updates: February 2014
http://blog.hartshorne.net/2014_02_01_archive.html
In Search of Updates. Ganglia Web UI Performance Improvement for Large Clusters. There are many transitions people tend to make over time as their Ganglia. Cluster grows in order to maintain performance. Many of them have been covered in other blogs, but here is a brief summary of the scaling steps I usually take, from the initial cluster up through thousands of hosts and hundreds of thousands of metrics. All of these steps successfully scale the ganglia core very well. With redundant gmond processes...
SOCIAL ENGAGEMENT