One of the defining features of snaps is their strong security. Snaps are designed to run isolated from the underlying system, with granular control and access to specific resources made possible through a mechanism of interfaces. Think of it as a virtual USB cable – an interface connects a plug with a slot. Security and privacy conscious users will certainly be interested in knowing more about their snaps – what they can do and which resources they need at runtime.

Maintaining legacy applications can be an affliction that saps up energy, time, and resources. Application modernization remains fashionable and involves refactoring, re-purposing, or consolidating legacy software to align it more closely with current business needs and add business value. Traditional methods for modernizing applications include rewriting existing application code to a more modern programming language to salvage parts of the application that might still have value.

We recently announced four new VMware Tanzu editions, each of which packages capabilities of the Tanzu portfolio into a solution that directly addresses a single, common customer challenge. Your effort to modernize applications is already complex. Tanzu editions simplify your access to the tools you’ll need to move forward. Before walking through each of the four new editions, it’s important to first call out the characteristics that are common to all of them.

Many of us hate our backup environments. That’s because backups kind of suck, even with a backup product as great as IBM Spectrum Protect. As I said in another post, it’s the thing that everyone needs, but no one cares about, and most definitely can make your life crappy. Ask any backup admin, and I know they’ll agree. Go ahead; I’ll wait. Yep, they said the same thing, didn’t they?

In this post, we learn how to use the reduce(), findColumn(), and findRecord() Flux functions to perform custom aggregations with InfluxDB. This TL;DR assumes that you have either registered for an InfluxDB Cloud account – registering for a free account is the easiest way to get started with InfluxDB – or installed InfluxDB 2.0 OSS. In order to easily demonstrate how these functions work, let’s use the array.from() function to build an ad hoc table to use in the query.

If you’re new to the Dashboards Beta app on Splunkbase and you’re trying to get started with building beautiful dashboards, this "Dashboards Beta" blog series is a great place to start. The Splunk Dashboards app (beta) brings a new dashboard framework, intended to combine the best of Simple XML and Glass Tables, and provide a friendlier experience for creating and editing dashboards.

At Splunk, we understand that a secure platform is a trustworthy one. We strive to implement a protected foundation for our customers to turn data into action, and part of that effort is giving you more frequent insight into the security enhancements that we’ve made to the platform. In this blog series, we’ll share the latest enhancements to Splunk Enterprise, review our security features in depth, and explain why these updates are important for you and your organization.

AWS Step Functions is a service that abstracts distributed applications into state machines, with each state representing a component of an application. Not only does this automatically generate an architectural diagram of your application’s workflow, it also makes it straightforward to reorder your states as well as implement parallel execution, retries, and other tasks.

One of the first requirements of building an effective team that consistently delivers results is having dynamic team members with the right skill set. This means having the right number of people with the right skills working on your projects at the right time.

Running systems in production involves requirements for high availability, resilience and recovery from failure. When running cloud native applications this becomes even more critical, as the base assumption in such environments is that compute nodes will suffer outages, Kubernetes nodes will go down and microservices instances are likely to fail, yet the service is expected to remain up and running.