Any post about analytics, using metrics to improve IT performance, increasing transparency across channels, etc.
Whether we practice more traditional operations processes with a 24x7 NOC and well-documented processes, or we’re embracing DevOps-styles with cross-functional teams and highly iterative methodologies, one problem we all face is the growing disconnect between our monitoring systems, the alerts they fire off, and the processes we’re using to handle operational issues. We log incidents in a ticket, but are the folks working on that ticket aware of the real-time status of the underlying incident?
Earlier this month at BigPanda we released our new Sharing feature, which allows NOC teams to quickly share active and critical incidents with the right teams and subject-matter experts. BigPanda already helps NOC teams today by giving them instant visibility into incoming related alerts so that they don’t have to sift through dozens of emails and web pages with every outage or disruption. They can also attach playbooks and timeseries graphs directly to BigPanda, which means no more navigating around, combing through bookmarks, trying to find the right wiki page for that memory issue, or the right Graphite link for that misbehaving database host.
We're excited to announce the release of a major new feature in BigPanda called Sharing! As you know BigPanda intelligently clusters your noisy alerts into high-level incidents. With our new Sharing feature, it's now easy to notify and collaborate with anyone on your team about critical incidents.
Last week was an exciting week. BigPanda announced $7 Million in funding from Sequoia Capital and Mayfield. We are super excited that these two firms share our vision for changing the way that IT and DevOps teams manage and respond to the thousands of IT issues they face every day. Last week, we also launched our offering into general availability. Check out some of the highlights from last week’s coverage on BigPanda from TechCrunch, GigaOm, Computerworld, 451 Research and more.
It’s well known in IT operations that things don't break on their own. Close to 80% of production outages occur because of changes made by developers or someone in IT. However, this fact often eludes us when it comes to actually resolving production issues.