We’ve all been there — you’re on-call, fast asleep at 3 AM when suddenly, in comes the alerts–in overdrive. Your system is notifying you of some sort of abnormal behavior, but with all the alerts and data coming through, its difficult to figure out what your system is trying to tell you. Is there potential malicious behavior? Did someone write faulty code? Is it an important issue or can it wait? Is it nothing at all?
Every single app — large or small, open source or not — has room for improvement when it comes to performance. This is why we created Skylight for Open Source to give open source contributors the tools they need to find these issues. Over the next week, we'll show you three different open source apps running on Skylight, each with their own unique performance challenges, varying in complexity.
We’re glad to announce that StackStorm Vagrant box and Community OVA are available for general use and included as installation method in StackStorm Docs.
In addition to our weekly roundup of Grafana-related articles and upcoming events, we’re pleased to announce Grafana v5.1.3 has been released!
Having worked closely with software developers for almost a decade, I’ve noticed some common traits amongst them. Technically minded people think about problems in different ways. I’m often stunned how I could miss such an obvious data point or edge case when discussing product changes with people who have a far greater technical mind than myself.
For as long as I can remember, I have loved building businesses. Ideas have always come naturally to me, and over the years I have honed my skills at actually making those ideas a reality. I recall one of my first businesses at about 12 or 13 years old, designing nicer looking versions of property data sheets for real estate agents to give out to prospective buyers. My most recent profitable business is StatusGator, a status page monitoring and alerting service.
Before the philosophy of DevOps, developers would build products, services, and infrastructures , but the responsibility for maintaining them would shift to operators, aka system or IT admins. The DevOps philosophy removes the boundary between Operations and Development teams, making system reliability a shared responsibility of all parties.
Logs contain some of the most valuable data available to developers, DevOps practitioners, Site Reliability Engineers (SREs) and security teams, particularly when troubleshooting an incident. It’s not always easy to extract and use, though. One common challenge is that many log entries are blobs of unstructured text, making it difficult to extract the relevant information when you need it.
On October 21, 2016 at approximately 4am PST, the internet broke. OK, we know the internet doesn’t “break.” But hundreds of important services powering our modern web infrastructure had outages – all stemming from a DDoS targeting Dyn, one of the largest DNS providers on the internet.
While Jay-Z taught me about bringing DevOps into Marketing, it was Shakespeare who really grounded me in the customer experience. I remember learning in school about how Shakespeare’s plays were lauded for two main reasons.
