Operations | Monitoring | ITSM | DevOps | Cloud

The Federal Cloud Computing Strategy (FCCS) makes it clear government agencies have significant responsibilities for protecting cloud-hosted data. The FCCS states the need for agencies to develop their own governance models and create service level agreements to ensure they’ll have continuous access to log data and prompt notification from their cloud service provider if there’s a breach.

The COVID-19 pandemic has been difficult for enterprises. Our CIO New Normal survey shows a litany of issues CIOs are dealing with. We discussed these challenges in our previous blogs here and here. But we also took note of the fact that some enterprises are actually doing quite well.

For public IPs, it is possible to create tables that will specify which city specific ranges of IPs belong to. However, a big portion of the internet is different. There are company private networks with IP addresses of the form 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 scattered in every country in the world. These IP addresses tend to have no real information for the geographic locations.

Over the last decade, data collection has become a commodity. Consequently, there has been a tremendous deluge of data in every area of industry. This trend is captured by recent research, which points to growing volume of raw data and growth of market segments fueled by that data growth.

For decades, compute or server infrastructure has been the backbone of the IT world. Compute has gradually evolved from on-premise hardware to programmable compute in the form of software containers. Technology operators need to constantly monitor the performance of their Windows, Linux, and container infrastructure so that they can optimize their compute environments to match workload demands.

Whether you’re trying to troubleshoot a problem, defend against attacks, or simply optimize your environment, event logs are your best source of information. More than that, not logging or ignoring your logs is like not checking your blindspot when you’re changing lanes—sooner or later you’re going to seriously regret it because the effects will be disastrous.

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.

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.