Operations | Monitoring | ITSM | DevOps | Cloud

When teams collect data without full observability of what others on the team can see, it becomes clear that no one’s picture is truly accurate. In this picture, all of the people are wearing blindfolds and feeling around to see what is in front of them. One thinks this creature is a spear, another thinks it is a tree trunk, and another a rope. As long as they cannot observe what the others can, there is poor data fidelity.

AWS recently introduced a new Lambda Telemetry API giving users the ability to collect logs, metrics, and traces for analysis in AWS services like Cloudwatch or a third-party observability platform like Coralogix. It allows for a simplified and holistic collection of observability data by providing Lambda extensions access to additional events and information related to the Lambda platform.

Here at LogicMonitor, we like to experiment and try new things. In fact, one of our core tenets is “better every day”. This means that we’re always hungry to learn new things, experiment, innovate, and take chances. One thing we’ve been experimenting with lately (and loving!) is the Quarkus framework. We love how lightweight it is and that it’s built from the ground up with Kubernetes in mind.

The process of delivering mobile apps utilizing cloud technology is known as mobile cloud computing (MCC). Complex mobile apps today carry out activities including authentication, location-aware features and providing users with customized communication and content. As long as your device is online, mobile cloud computing enables you to store and access data anywhere. This makes it possible for data to be sent without difficulty anytime required.

This year, global ecommerce transactions are expected to grow by over 12% during the 2022 holiday season. As the industry continues to rely more on ecommerce, retailers are looking at new ways to improve customer experience and provide a safe and secure shopping journey. In an increasingly competitive space, many retailers are leveraging their data assets to accomplish more, spark innovation, create more personalized experiences, and drive higher conversion rates.

An avid bird-watcher once told me that for bird-watching beginners, it’s more important to focus on learning about the birds and identifying their unique songs rather than trying to find the perfect pair of binoculars.

Everybody agrees network documentation is extremely important, but there tends not to be a lot of agreement on what that documentation should include. The short answer is that it should include everything that’s relevant—but what that means varies between networks. For example, in a really small network with one switch and a firewall, and perhaps a single wireless access point, there isn’t much to document. It might be enough to put everything in a single diagram.

A Microsoft Teams rooms strategy might seem like more effort than it’s worth on the surface, but you’d be surprised how much impact it can make. With many businesses now mixing in-person and remote Teams meeting participation, planning and optimizing how it works just makes sense.

One of the things that struck me upon joining Honeycomb was the seemingly laissez-faire approach we took towards internal SLOs. From my own research (beginning with the classic SRE book, following Google’s example), I came to these conclusions: If you read the original SRE book when it was released, before the workbook came out, these conclusions all made sense.

Today the Grafana Agent team is excited to announce the release of Grafana Agent v0.29.0. This September, we introduced a new way to easily run and configure Grafana Agent called Grafana Agent Flow, our new dynamic configuration runtime built on components. Within Flow, we are also embracing Grafana Labs’ big tent philosophy by introducing OpenTelemetry (OTel) Collector components and converters for traces, metrics, and logs in Agent v0.29.0.