Operations | Monitoring | ITSM | DevOps | Cloud

There are so many great things that can be said about Loki – I recently wrote about them here. But today, I want to talk about something technical that has been difficult for Loki users, and how we might make it easier: using Loki for short-lived services. Historically, one of Loki’s blind spots is ingesting logs from infrastructure you don’t control, because you can’t co-locate a forwarding agent like promtail with your application logs.

On September 14, CVE-2020-14386 was reported as a “high” severity threat. This CVE is a kernel security vulnerability that enables an unprivileged local process to gain root access to the system. CVE-2020-14386 is a result of a bug found in the packet socket facility in the Linux kernel. It allows a bad actor to trigger a memory corruption that can be exploited to hijack data and resources and in the most severe case, completely take over the system.

With the accelerated pace of digital transformation, DevOps, adoption of new platforms, and also managing cloud resources are becoming increasingly challenging for central IT. Applying available best practices, compliance requirements and cost management are adding to the challenge. With the Serverless technologies, customers can apply such policies to cloud resources and run them over a long time.

Your cloud application or service can look pristine from an IT perspective, while the end-user identifies it as “glitchy” and “unreliable”. Though the technical issues may not be your fault, it still impacts the user’s perception of your company and brand. Issues could spawn from the user’s device limitations, the browser version, or a regional public cloud outage that is causing the poor user experience.

The new quality release offers many bug fixes for increased stability, as well as Mattermost Omnibus — a new method for installing and maintaining Mattermost, and a one-click experience in Team Edition to access Mattermost Enterprise features.

APM tools have been formerly and primarily siloed in the application development arena, with only the most important and mission-critical applications having their APM instrumentation extended into production use due to complexity and cost. In the modern world of application monitoring, the requirements for Dev and Ops need to be tightly integrated.

Today is a momentous day for JFrog, as we’re excited and proud to join the Nasdaq family of listings. While COVID-19 challenges every company and prevents us from being together in many ways, we’re humbled that Times Square was turned green today! This is obviously an important milestone, and it couldn’t have happened without over a decade of hard work and millions of hours that have gone into this amazing company.

Whether military, a civilian agency, or even a public education institution, organizations across the public sector have witnessed a substantial increase in cyberattacks. There were a number of hits on education around this time last year, and then on health-related agencies as the COVID-19 pandemic struck. So, how do government agencies ensure their security posture is up to the task of defending against increasingly opportunistic forces of evil?

I’m incredibly excited about the future of Webpagetest and web performance testing in general with today’s announcement that Webpagetest and Catchpoint will be joining forces and I hope you’re as excited as I am for the possibilities it will bring.

This is the second in a two-part blog series about AIOps where I sit down with Julian Dunn, Director of Product Marketing at PagerDuty, to level-set on the hot DevOps topic. The first post discussed whether AIOps was just marketing fluff and whether ITOps actually has an AIOps problem. Let’s continue…