Operations | Monitoring | ITSM | DevOps | Cloud

Raise your hand if you enjoy being kicked out of the application you were working on for an unexpected security patch! No one? We can wait … Really, no one? Okay, we figured. And we’re not surprised. Jamie Whalen, host of the Everywhere Workplace Podcast, recently sat down with Steve Brasen, Research Director for Enterprise Management Associates, to talk about the perceived conflict between Digital Employee Experience (DEX) and security.

The internet of things is one of my favorite topics. IOT enables low-powered connected devices that opens gateways from the digital to the real world. While I love tinkering away with an Arduino sketch and the latest Espressif or Arduino board, there is always an air of frustration when trying to build out what at first seems like simple functionality using one of these “smart devices” because of the limited view we have into their operations.

Typically, startup founders and executives must meet with their board of directors each quarter to review the progress of the company. They may talk about broad topics such as total costs and total revenue, and use these numbers as a guide to determine which moves the company should make in the near future. Often missing from the conversation, however, is a clear and detailed discussion of SaaS metrics.

There is a famous quote that goes like this…‘For every minute spent organizing, an hour is earned.’ At least in the world of incident response, nothing is more apt than this. Digital infrastructure these days is made up of multiple services, an outage could result from either one impacted service or multiple impacted services. So it's essential to have a catalog of all the services along with the point of contact (service owner) responsible for maintaining it.

This article was originally published in The New Stack and is reposted here with permission. Working with geo-temporal data can be difficult. In addition to the challenges often associated with time-series analysis, like large volumes of data that you want real-time access to, working with latitude and longitude often involves trigonometry because you have to account for the curvature of the Earth. That’s computationally expensive. It can drive costs up and slow down programs.

I like to leverage our technologies to ensure our products have a pleasant user experience. Elastic Synthetics enables you to configure it in an out-of-the-box experience directly through your Elastic Cloud deployment without the need to install anything! It also works across the globe with multiple locations you can choose from. Ever wondered how fast your web service is when accessed from Japan, Germany, or the eastern U.S.? Now you can do this by simply clicking on a checkbox.

Cloud Logging launched Log Analytics powered by BigQuery. The top 10 reasons to get started with Log Analytics for no additional cost

It may surprise you to hear, but Honeycomb doesn’t currently have a platform team. We have a platform org, and my title is Director of Platform Engineering. We have engineers doing platform work. And, we even have an SRE team and a core services team. But a platform team? Nope. I’ve been thinking about what it might mean to build a platform team up from scratch—a situation some of you may also be in—and it led me to asking crucial questions. What should such a team own?