We’re thrilled to share the news that Splunk has been named a Leader in The Forrester Wave™: Security Analytics Platforms, Q4 2020. It’s an honor to be named a Leader by Forrester. We view it as an affirmation of our commitment to customer success and a reflection of our ability to understand their needs. Through close collaboration with our customers, we have developed innovative solutions to protect their data hosted in on-premises, hybrid or multi-cloud environments.

Securing access to business resources has always been of high priority for admins and IT teams. In the wake of the pandemic, workforces are more distributed than ever before, and 76 percent of global office workers state that they would like to work from home even when the pandemic is over.

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.