We believe that small businesses are the backbone of the local economy and consider our suppliers as partners in our success. Unfortunately, the novel coronavirus/COVID-19 has brought tough times and economic disruption that could significantly change the global economy. So we at Logz.io decided that we can make a meaningful impact by supporting our suppliers and helping them to meet the challenges that this new era brings.

You can view mobile-friendly dashboards and interact with augmented reality (AR) visualizations with the Connected Experiences suite of mobile apps. Splunk Mobile, Splunk AR, and Splunk TV allow you to take Splunk data on the go for a secure mobile experience. Below, Ryan O'Connor from the Splunk for Good team shares some examples of how to build mobile-friendly dashboards. Splunk for Good makes machine data accessible and valuable to nonprofit organizations and educational institutions.

The duality of observability is controllability. Observability is the ability to infer the internal state of a "machine” from externally exposed signals. Controllability is the ability to control input to direct the internal state to the desired outcome. We need both in today's cloud native world. Quite often we find that observability is presented as the desired end state. Yet, in modern computing environments, this isn’t really true.

Security information and event management, or SIEM, has become part of the vocabulary of every organization. SIEM solutions gather events from multiple systems and analyze them—both in real time and through historical data. SIEM costs—as cyber security costs in general—can be high, but there is a tradeoff if you opt for the FOSS route (free and open source solutions).

Last month, we hosted a webinar, Hunting for persistence using Elastic Security, where we examined some techniques that attackers use in the wild to maintain presence in their victim’s environment. In this two-part blog series, we’ll share the details of what was covered during our webinar with the goal of helping security practitioners improve their visibility of these offensive persistence techniques and help to undermine the efficacy of these attacks against their organization.

That is a common question I see among developers. Most of the time, nobody cares about system logs. But when things go south, we absolutely need them. Like water in the desert, sometimes! At Dashbird, we have a list of criteria compiled to determine a reasonable retention policy for application logs. There is no one-size-fits-all, though. The analytical dimensions below will give a relative notion of how long the retention period should be.

There are 1.3 billion websites out there in the great unknown and it’s hard not to think about what makes them different from one another. Why do users flock to one website and ignore the other completely? One major differentiator is, of course, content. I’m not going to dwell on what type of content is better. Another reason why users stick to one website over another is the user experience. Today we’ll be looking at a third major differentiator: Website Performance.

Monitoring has been around since the dawn of computing. Recently, however, there’s been a revolution in this field. Cloud native monitoring has introduced new challenges to an old task, rendering former solutions unsuitable for the job. When working with cloud native solutions such as Kubernetes, resources are volatile. Services come and go by design, and that’s fine—as long as the whole system operates in a regular way.

In the context of logging, multiline logs happen when a single log is written as multiple lines in the log file. When logs are sent to 3rd party log monitoring platforms like Coralogix using standard shipping methods (e.g. Fluentd, Filebeat), which read log files line-by-line, every new line creates a new log entry, making these logs unreadable for the user.