When PagerDuty’s VP of Product Management Rachel Obstler announced the beta version of our new Slack integration in April in her “Anticipating, Monitoring, and Managing Incidents via Slack” panel at Slack Frontiers, we expected significant interest in the integration among our customers.
I was reminiscing about an incident that happened at a past job with an old co-worker. You know the one, the one where you installed a library that makes some task of yours simple, only to reveal the library makes things worse. This incident in particular involved the way that images served out of our Ruby on Rails application, and the library that made it possible to “easily resize before serving” them.
Software that treats the container as the first-class unit of infrastructure.
When you need to troubleshoot an issue in your Node.js application, logs provide information about the severity of the problem, as well as insights into its root cause. You can use logs to capture stack traces and other types of activity, and trace them back to specific session IDs, user IDs, request endpoints—anything that will help you efficiently monitor your application.
Chrome 77 dropped last week, and our 209 checkpoint locations are in the process of updating or are already using the newest version of Chrome to monitor your website. That means your Web Application Monitoring and Full Page Check performance monitors are in sync with your users with the latest and greatest Chrome browser. Is your website monitoring service current?
This past month was a hot one for outages. The Facebook family of apps continues to struggle with multiple outages, the London Stock Exchange had to open late one day this past month, and banks across the world experienced issues. Here’s your August outage report, including insights from our own monitoring at the Uptime.com HQ.
