You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If logs are thought of as living event streams that are meant to be processed in near-realtime, things get interesting. Rich data flows out of your app and on to various processors that take care of actions such as long term archival to S3 or populating search indexes in elasticsearch.
If you adopt a key=value convention like below, they can be more easily parsed by machines and filtered by tools like grep:
Lean on Chef recipes or Puppet manifests to describe your application. If you are here, you are doing awesome. The most clear downside is almost the system's strength: everything is coupled to the configuration management system and is therefore limited by it. It's a monolith.
When your customers want to run an application on your platform, they have to use a DSL and write recipes or manifests as well as corresponding templates.
I recently scrapped by blog (then powered by the excellent Jekyll) in favor of a simple index that links to gists. With the advent of the new Gist release one has about all that is needed to maintain and publish technical notes.
check_http: A Small Part of the Modern Monitoring Pipeline
[note: this was originally published on 08/27/2012. Other writing can be found here.]
Monitoring tooling has been a fascination of mine since I began hacking on computing systems. Every ops engineer wants to write their own. I get that. I'm one of those guys, too.
However, these endeavours always end up spitting out large, monolithic applications that just aren't as good as the already existing (and somewhat crappy) monolithic applications. I'd prefer to avoid that approach, if only to make it a point that the monitoring story can never be finalized. We will never reach an end state, but the more flexible our tooling the better.
Traditional Unix philsophy gives us something to go on here. What if, instead of writing large applications, we just wrote a bunch of tiny tools. AND - rather than writing each of these tiny tools as sexy network daemons (which
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters