Apache Solr was always ready to be extended. What was only needed is a binary with the code and the modification of the Solr configuration file, the solrconfig.xml and we were ready. It was even simpler with the Solr APIs that allowed us to create various configuration elements – for example, request handlers. What’s more, the default Solr distribution came with a few plugins already – for example, the Data Import Handler or Learning to Rank.
A large number of security breaches are impacting industry verticals, including banking, financial services and insurance (BFSI), telecom, and hospitality, so there's a growing need for organizations to fortify their infrastructure against these threats. For example, by the time T-Mobile identified the intrusion and unauthorized access to its sensitive data in 2019, both its customer and employee details were already stolen by hackers.
As we connect with customers we increasingly hear the need for teams to be more predictive with their data. A big challenge is uncertainty around how to get started, especially when much of their data is unstructured. At Splunk, our goal is to make data — and machine learning — accessible for a broad range of users. The good news is, with machine learning doing even more work on your behalf, you don’t need to be a data scientist to use these advanced capabilities.
On the internet, nothing necessarily stays easy, simple, and reliable forever – but we’re trying to keep it that way for your logs. When our customers use Kubernetes, they want to remain focused on the real challenges of scaling, and avoid infrastructure headaches, so that they can adapt to the unexpected easily and with a minimum of toil. That’s why we continue to invest in the LogDNA Agent. It’s built to handle file logging in even the most intensive Kubernetes deployments.
LogDNA is adding the ability to store and view raw lines, allowing customers to debug with logs in their unaltered form. If you’ve ever looked at your logs and noticed that the timestamp was different than what you expected, it is usually due to a long latency between the event and processing time of the logs. Depending on the size of the latency, we may update the log timestamp to order them accurately and to provide a cleaner and more intuitive search experience.
Many people are working from home (WFH) now and will be for at least the next few weeks. The VPN and TLS connections that remote workers rely on allow for secure access, and although these are not new connection types to monitor, the current WFH situation has created a significant increase in the number of these connections you must monitor. This new WFH scenario has made one thing easier: mobile users are no longer mobile.
