Operations | Monitoring | ITSM | DevOps | Cloud

All over the internet, there are ominous rumblings that “768K Day” is on its way—and it’s likely going to happen before May is over. And while some ISPs think this BGP (Border Gateway Protocol) milestone is being overhyped like Y2K and Cisco assures us the sky isn’t falling, that doesn’t mean we’ll all be left unscathed. If you’re an MSP who hasn’t heard about 768K Day yet, brace yourself—you could be in for a serious connectivity headache.

It is difficult to overstate the importance and impact that Artificial Intelligence (AI) has had on the employee experience. This is crystal clear when you see how employees are interacting with their IT departments. Employees expect technology to just work. When there are technical problems the expectation is that fixing the issue will be fast and seamless. An increasingly important part of meeting this employee demand is the virtual agent, or chatbot.

As the first part of the three-part series on monitoring Apache Solr, this article explores which Solr metrics are important to monitor and why. The second part of the series covers Solr open source monitoring tools and identify the tools and techniques you need to help you monitor and administer Solr and SolrCloud in production.

The Emergency Services team at Trapeze Group provides 24/7/365 support for ambulances in Australia. Each fleet can contain as many as 1,000 vehicles, with more than 60 telemetry channels and 120 million messages going in and out to paramedics every day.

As shown in Part 1 Solr Key Metrics to Monitor, the setup, tuning, and operations of Solr require deep insights into the performance metrics such as request rate and latency, JVM memory utilization, garbage collector work time and count and many more. Sematext provides an excellent alternative to other Solr monitoring tools.