Operations | Monitoring | ITSM | DevOps | Cloud

With the advanced containerization that has become the norm in the modern cloud, your infrastructure is likely more distributed, and thus more exposed to networking issues, than ever before. When troubleshooting application performance issues, this can make it difficult to link the symptoms you observe through monitoring the “golden signals” (requests, latency, and errors) on individual endpoints in your application to their underlying root causes.

Grafana Tempo, the recently announced distributed tracing backend, relies on integrations with other data sources for trace discovery. Tempo’s job is to store massive amounts of traces, place them in object storage, and retrieve them by ID. Logs and other data sources allow users to quickly and more powerfully jump directly to traces than ever before. Previously we investigated discovering traces with Loki and exemplars.

Performance monitoring is great because it lets you see whether your application is fast or slow, and which parts need speeding up. For Node developers, those “parts” are most often endpoints handling incoming requests. Since the introduction of our performance monitoring offering in July 2020, Node devs have been able to use the Sentry SDK, @sentry/node, to measure the total time it takes to process each request, but we made some significant improvements since then.

Kubernetes namespaces enable you to organize cluster objects, such as applications, devices and variables. Once you define namespaces, you can use this classification to filter, group and manage objects. You can use the same namespaces in duplicated environments and apply policies to specific clusters segments. Kubernetes namespaces are also important for defining roles and ensuring proper access configuration. If you're monitoring Kubernetes, you should try out MetricFire.

We want to hear directly from you about your experience using Puppet products so we can ensure our portfolio rises to the demand of our customers. Take this survey to share your expertise with us. At Puppet, we’re dedicated to innovating the most modern, easy-to-use, secure and compliant products for our customers to ensure practitioners can simplify their workflows and enterprises can meet their business goals. Your input is extraordinarily valuable to us.

Trying to improve the reliability of your Kubernetes deployment? Start with these 5 chaos experiments. Kubernetes 1.20 is scheduled to be released next week, and this version contains a number of amazing enhancements including graceful node shutdown, more visibility into resource requests, and snapshotting volumes. But the change generating the most buzz is the deprecation of Docker as a container runtime.

If you work in monitoring, you know how important it is for the right people to see the right data. Too much irrelevant data creates a flurry of alerts that hinders productivity, and missing out on key data leads to visibility issues. Worst of all is when you get the wrong people tinkering with data that belongs to other teams.

Cloud-native is the ultimate buzzword lately. So, is “cloud-native storage” just an attempt to grab on to this concept, hoping for a little boost? Actually, there is something more to it, and I’ll unpack that here. The premise of cloud-native storage is simple: its native habitat is a Kubernetes cluster. When we design with the assumption that a technology will exist in Kubernetes, we get to look around and see what functionalities already exist in that system.

We’ve heard your feedback and are happy to announce that Mattermost will be introducing Collapsed Reply Threads in beta early next year! This feature is a top priority for our team and is the most voted feature request on our idea forum. Threads are core to the messaging experience in Mattermost. They allow users to organize conversations about various topics within a channel.

Under the leadership of innovative CIOs—Chief Information Officers—the public sector is blazing new trails and focusing on things like digital transformation to provide constituents with the best services available in the most efficient way possible. While digital transformation will impact the way federal and state agencies look at and adopt new technologies, it will also affect the role of the CIO.