Operations | Monitoring | ITSM | DevOps | Cloud

December 7 started as a typical, but busy, pre-holiday weekday. This included a mix of booming online retail sales ($33.9 billion spent during cyber week), packages flooding delivery services, and high online traffic. But much of that quickly came to a crawl. An outage of the AWS us-east-1 cloud region changed the good fortune for many websites and applications and impacted the lives of consumers across the United States and parts of Europe.

The recent Apache Log4j vulnerability CVE-2021-44228 dubbed Log4Shell is a big deal. By now there is no shortage of blogs, other write-ups, and analysis about why this vulnerability is an urgent issue and why there is a very good chance it applies to your environment. Here are some of the articles that dive into the gory details on this CVE.

Last Thursday, a researcher from the Alibaba Cloud Security Team dropped a zero-day remote code execution exploit on Twitter, targeting the extremely popular log4j logging framework for Java (specifically, the 2.x branch called Log4j2). The vulnerability was originally discovered and reported to Apache by the Alibaba cloud security team on November 24th. MITRE assigned CVE-2021-44228 to this vulnerability, which has since been dubbed Log4Shell by security researchers.

We’re excited to share with you that we have launched a completely new way to start using the JFrog DevOps Platform that you – as a developer – will love. We’ve provided a super-easy, developer-friendly path to discovering how Artifactory and Xray can help you produce safer apps, faster, getting started through the command line shell and IDE that you use every day.

Let’s get to the point about data management: Businesses need data, but accumulating too much can be detrimental. Data overcrowding can corrupt IT professionals, turning them into greedy hoarders. Being indigestible with excessive repeated, outdated or banal information, the so-called ROT data, is bad. Companies of the world! The Devil tempts you with Big Data! Something that, if too much, could be harmful! We tell you all about it in this article.

Interpreting data and making fast decisions is critical for any leader in today's business world. But how is it done? Everyone remembers the old way of doing things where analysts would manually crunch the numbers and give a final output. This business intelligence would be presented to their boss, and decisions would be made. This batch way of running numbers and presenting them is not sustainable due to the massive amount of manual effort involved to recompile datasets and present them properly.

In our last blog, "Splunk Cloud Self-Service: Announcing the Admin Config Service (ACS)" we introduced our modern, cloud-native API that is enabling Splunk Cloud Platform admins to manage their environments in a self-service fashion. In this blog, we take a look at our latest effort to empower our customers: ACS private app management.

Field service management covers a lot of areas, from installing and maintaining field equipment to scheduling, dispatching, and labor tracking. Across those myriad areas are numerous challenges: scheduling conflicts, miscommunications, workforce changes, customer dissatisfaction, poor first-time fix rates, lack of asset visibility, and more. But field service management is vital to successful business operations. Here are three ways ServiceNow helps companies improve their field service operations.

Wondering whether you can optimize your business using application performance monitoring? The answer is “Surely!” Our full guide on application monitoring usage will serve as proof. Contemporary businesses and startups depend on software applications for running their digital activities and supplying SaaS or AaaS (application-as-a-service). Nowadays, expedited application and service delivery without sacrificing quality is a top concern.

Time is a luxury that IT workers don’t often have – and that’s particularly true after the massive upheaval all of our businesses have experienced since the pandemic. Ever since the working model changed overnight and digital transformation accelerated to warp speed, IT teams have had to implement new initiatives quickly in order to keep up. But how can they know that these initiatives have been successful?