I’ve been running into a logging challenge at work of late. The usual issue. Lots of logs, in lots of places, retention policies, governance issues, reporting and (in my humble opinion the most important) support/debugging. After some searching I found logg.ly and Papertrail which offered what I wanted as a service. Very sweet. Unfortunately I cannot use them in this implementation so I am pursuing Graylog2 and logstash (another blogpost on that later). Right now I’m plugging Papertrail into our demo system to see how it goes and how it fits with our workflow. I just wanted to cover off some first impressions with Papertrail.
Recently the team was working on some stuff in EC2. This is a bit new for us so we’re figuring many things out as we go. One thing work sharing is integrating a PHP web app running in EC2 to Amazon’s Simple Email Service. Following the guides gets you 90% of the way but the last mile had a snag. Full disclosure, none of us is email experts.
We implemented the PHP - Postfix - Stunnel - SES approach advocated by AWS. The older option used perl and worked for us. However, we did want to go after the best practice approach and it’s outlined with the postfix setup and the stunnel setup.
The snag we hit was as follows: using the perl tools we could queue an email in SES. Note, when in sandbox mode you can only send to and from the verified email addresses. Do yourself a solid and setup two addresses. Otherwise reading the mail.log file will blow your mind. When we tried to queue an email from our PHP app through postfix across the stunnel to SES the to and from fields were, in a word, effed up. Turns out setting the MyDestination parameter in the main.cf file of the postfix config was the culprit. Also, in our PHP.ini file we ensure that we were starting sendmail with the suggested unix flags but that’s a red herring for this issue. Our solution was to unset the MyDestination parm and pow. Up and running. We think. Here’s to a great push by @ericchernuka, @dannydotellis, and @swinglinetrade to solve a stinker.
So I’ve switched to Octopress. I am quite impressed with it and markdown. Elegantly simple. This might even encourage me blog more.
post rescued from my wordpress blog
A little over a year ago one of the Systems Engineers on my team (@rhettdickson) suggested I look into DevOps and maybe start adopting some of the practices. What a prophetic suggestion. Presently the Ops team at Calgary Scientific is in the midst of implementing many great DevOps ideas and practices. I wanted to share some of the key things I have learned about getting started with DevOps. This post is heavy on the links, twitter, blogs and opinions but I hope you find it interesting.