Operations | Monitoring | ITSM | DevOps | Cloud

PagerDuty is proud to announce our latest release, which provides a new set of product capabilities and enhancements that further enable you and your teams to securely work in real time—anytime and from anywhere. With this release, we continue to respond to our customers’ needs to build a better platform to help them best manage their digital operations. Enhancements include new innovations for our mobile app and increased platform security by adding email domain restrictions.

In this release 738, mass alerts have been incorporated into policies to make their creation process easier. In addition, different visual consoles have been added in this update, which will appear by default and can be customized according to the user’s needs. Several bugs concerning Metaconsole events and agents have been fixed – we remind you that it is available from 2 000 devices and for the Enterprise version.

Does your organization have an on-call rotation? Several members of the Honeycomb engineering team recently hosted a live webcast about why they never feel alone when on-call at Honeycomb.

We live in a containerized world, and traditional monitoring and logging are being forever changed. The dynamic and ephemeral nature of containers creates new logging challenges. Docker addresses these in some ways. Docker Engine provides various logging drivers that determine where logs are sent or written to. The default driver for Docker logs is “json-file,” which writes the logs to local files on the Docker host in json format.

Office 365, or O365 as it is more commonly known, is much more than simply a cloud–based replacement of Email, Word and Excel—it’s a comprehensive and complete workplace productivity experience, accessible anywhere, from any device. In line with the other cloud services offered by Microsoft, O365 is continuously updated with new features and capabilities via the cloud, which come quickly and relentlessly.

When a critical incident strikes and hampers your business operations, it's how you handle what comes next that will make all the difference to the extent of damage and the length of downtime. Chaos in the aftermath does not need have to be the default. Your team can stay focused and cool-headed with a solid incident response (IR) plan.

In the world of information technology, data has become the fundamental currency that holds the highest value. IT Operations Analytics (ITOA) represents one of the largest and richest sources of fresh and actionable data. Many automated tools can be used to make sense of all the information that comes from day-to-day IT operations, from log to agent to wire data.

Kubernetes has fundamentally changed the way we manage our production environments. The ability to quickly bring up infrastructure on demand is a beautiful thing, but along with it brings some complexity, especially when it comes to logging. Logging is always an important part of maintaining a solid running infrastructure, but even more so with Kubernetes. Because Kubernetes clusters are constantly being spun up, spun down, always in flux, making sure logging functions correctly is critical.

It’s been a few years since the “Spotify Model” became the latest trend for structuring an engineering team. But, like its predecessors, the model based on tribes and squads has some pitfalls. How to structure an engineering team is a question that’s been covered at length, from the strengths and weaknesses of common team structures to a matrix of organization based on risk and scale to why you should choose your own model.

On any given day, we use rideshare apps to get from one place to another. We check public transportation apps to see when the next train is arriving at the station. We use streaming services to watch Frasier at the end of lo-ooo-ng work days. As part of engineering teams, we use application monitoring and cloud services (like CI and cloud infrastructure) to function, so that code changes seamlessly deploy into production.