From Zenoss Wiki
Revision as of 17:41, 1 June 2015 by Cgilchrist (Talk | contribs) (change four to five and minor edits)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Issue 8, June, 2015

Published on 2015/06/02

Welcome to the June 2015 Zenoss Community Newsletter! Herein we find five new articles!
Bulbgraph.png Note: Zenoss will be at SELF Andrew D Kirch the Zenoss Community Manager, and author of many of these articles, is speaking at SELF in Charlotte, NC. SELF will be held at the Sheraton Charlotte Airport June 12-14, 2015.
We want you to participate! Got a cool Zenoss Core blog article or a howto? Please reach out to the Zenoss Community Manager.

Introducing Our Newest Zenoss Master!

Superhero wiki.jpg
Here at Zenoss, we are very pleased to introduce you to our newest Zenoss Master!

Making Docker more Versatile with Zenoss Control Center

Zenoss has released our open source Control Center product that will change how you think about Docker, both in terms of deploying and monitoring the applications. In this article we’ll start with a simple ElasticSearch Dockerfile, explain how Control Center takes Docker to the limit, and create a Control Center service template. With your new template, and Control Center, you can leverage nearly unlimited power and control of your applications.

Why is it Hard to Write a Postfix ZenPack?

Postfix logo.gif
After an account on one of my mail servers was compromised, and was used to send spam, I found there were lots of Nagios plugins for Postfix. I wasn’t impressed with any of them, so I wrote a ZenPack to fix the problem. It quickly became apparent as I did this that the problem wasn’t Nagios, and wasn’t the plugin authors, it was Postfix itself. I’ll discuss the issues I found, and how they should be fixed. Of course, I’ll also provide a link and guide for setting up the ZenPack.

If You Can't Take the DevOps Heat, Stay Out of the Kitchen

Devops wiki.jpg
IT Operations staff have been turned into virtual plumbers, ensuring all the bits of underlying infrastructure are connected together properly, and don’t leak. This is tedious work, and one mistake dooms the next rollout to failure, and an unplanned outage. Utilizing the test suite in Chef can save you from having Zenoss wake you up at 3AM.

Zenoss 5 Performance Data System

Performance data wiki.jpg
Perhaps the most visibly new feature in Zenoss 5 is the new graphing system. You’ll immediately notice that graphs are slicker and shinier than RRDtool, rendered in HTML5, and interactive to boot. That would be enough of a reason to migrate, but the real difference is invisible, hiding under the hood.