For 2 9s (99%) and 3 9s (99.9%) scenario, a single region setup is enough.
| SHELL=/bin/bash | |
| # to see all colors, run | |
| # bash -c 'for c in {0..255}; do tput setaf $c; tput setaf $c | cat -v; echo =$c; done' | |
| # the first 15 entries are the 8-bit colors | |
| # define standard colors | |
| ifneq (,$(findstring xterm,${TERM})) | |
| BLACK := $(shell tput -Txterm setaf 0) | |
| RED := $(shell tput -Txterm setaf 1) |
| #!/usr/bin/env ruby | |
| require 'rubocop' | |
| require 'english' | |
| ADDED_OR_MODIFIED = /A|AM|^M/ | |
| # to prevent code injection: system is a dangerous call | |
| def raise_single_quote_error | |
| raise ArgumentError, 'Single quotes are not allowed in filenames here.' |
| { | |
| "handlers": { | |
| "example_handler": { | |
| "type": "pipe", | |
| "command": "notify_somebody.rb", | |
| "timeout": 30, | |
| "filter": "filter_weekly_maintenance" | |
| } | |
| } | |
| } |
UPDATE (2017-10-20): it has recently been brought to my attention that this gist has been circulated amongst Sensu users as a sort of best practice or "guide". This gist was never meant to be adopted as a long-term solution, but rather an alternative/temporary solution while many changes regarding Sensu event filtering were "in-flight". Many more words regarding changes to event filtering have been captured on the Sensu blog since the writing of this gist: https://blog.sensuapp.org/deprecating-event-filtering-in-sensu-plugin-b60c7c500be3. The TL;DR here is: use the new built-in occurrence filtering that has been available in Sensu Core since version 0.26.0 (release notes).
Hi friends.
There has been a lot of confusion over the past few months about how the Sensu check definition attributes occurrences and refresh actually work. The attributes occurrences and refresh are not (currently) a part of the Sensu [check definitio
| require 'net/http' | |
| require 'uri' | |
| require 'json' | |
| module NewRelic | |
| module Insights | |
| class Query | |
| attr_reader :key, :account_id | |
| def initialize(key, account_id) |
| class Dashing.NumberStatusService extends Dashing.Widget | |
| @accessor 'current', Dashing.AnimatedValue | |
| @accessor 'difference', -> | |
| if @get('last') | |
| last = parseInt(@get('last')) | |
| current = parseInt(@get('current')) | |
| if last != 0 | |
| diff = Math.abs(Math.round((current - last) / last * 100)) | |
| "#{diff}%" |
| #!/bin/bash | |
| instanceID=$1 | |
| date=$(date +%Y%m%d) | |
| function downloadLog () { | |
| local log=$1 | |
| aws rds download-db-log-file-portion \ | |
| --output text \ |
This documentation aims at being a quick-straight-to-the-point-hands-on AWS resources manipulation with [boto3][0].
First of all, you'll need to install [boto3][0]. Installing it along with [awscli][1] is probably a good idea as
IFrame plugin for dashing
Dashing widget to display an iframe with specified src
Create the folder iframe in the /widgets/ directory. Put the files iframe.coffee, iframe.html and iframe.scss in that folder.
