Operations | Monitoring | ITSM | DevOps | Cloud

2018 has been a momentous year at PagerDuty. We spent the past six months accelerating the development of many new PagerDuty product innovations, and have released a variety of updates and enhancements across our digital operations management platform and mobile applications.

Businesses and organizations shouldn’t simply rely on monitoring tools for security management. Such tools don’t provide redundancies, time-stamped audit trails and other elements needed for incident resolution. Also, security threats are rampant and tend to go unchecked even with the most reliable monitoring service. That’s why companies require critical alerting to become aware of security incidents and immediately solve them for business continuity.

We started out the year strong, and the trend continues! Earnings for the second quarter of 2018 surpassed Q2 2017 by 24%!

For decades Development and Operations teams worked in silos. As a result, innovation stalled and gaining a competitive edge in the marketplace grew difficult. Too much red tape slowed product development to a crawl.

You work on your software’s performance. But let’s face it: production is where the rubber meets the road. If your application is slow or it fails, then nothing else matters. Are you monitoring your applications in production? Do you see errors and performance problems as they happen? Or do you only see them after users complain? Worse yet, do you never hear about them? What tools do you have in place for tracking performance issues? Can you follow them back to their source?

In part 1, we looked at an overview of auditing servers. In this blog, we’ll discuss which events you need to audit in your databases and file servers where sensitive data is stored. New data protection regulations and large-scale global attacks have made this more important than ever before. The main goal is to not only ensure that the accesses and modifications to sensitive data in your network are authorized, but also that file and column integrity are maintained.

We want to begin this post by thanking our long-time Uptime.com members for bearing with us through the transition to our new user interface. You have no doubt noticed the changes. The adjustments to the UI are small, but some important features are now in a different place. Our intent was a more intuitive design. Today, we’ll walk you through some of our most important decisions in this post. First, we’ll document some changes to be aware of.