With the first quarter of the year behind us, it’s worth reflecting on some exciting developments to make it easier to deploy, manage and scale Apache Solr. Below is a quick round-up of the features our team has released that we think will be most beneficial for developers and agencies alike.
More-Affordable Non-Production Plan for Azure
Based on customer demand, we’ve introduced a new Dedicated Node plan for Microsoft Azure called “DN2”. This plan provides customers with a more-affordable non-production environment. Compared to the existing DN4 plan for Azure, the DN2 plan has 1⁄2 the Ram and Storage (2GB, 16GB) and is 75% cheaper than the DN4 plan. See pricing here.
Availability of Apache Solr 7.5
All plans, including Self-Service plans, now support deployments of Apache Solr 7.5 for all cloud providers on all available regions. You can learn more about it here.
Backup Schedules with Hourly Granularity
Our team has now made automatic hourly backups available to all Premium and Self-Service Plans. Customers can now adjust the frequency of backups within a day and meet design requirements per their Recovery Point Objective (RPO) or other business needs. You can learn more about it here.
New Monitoring Metrics for Your Deployments
Last quarter, the team released three new metrics within SearchStax Pulse.
- Disk Space Usage: Customers can now plan for upgrades or index cleanups by monitoring Free and Used space on their Solr deployment’s data directories. Automatic alerts send email when critical disk-space thresholds are exceeded.
- CPU Utilization (percentage): Customers can now monitor System Load metrics in terms of percentage of capacity. CPU Utilization Usage is available on all newly created deployments with a range of 0% to 100%. Customers can also create threshold alerts in order to plan for scale-up and scale-down needs.
- 500 Error Count: Problems in Apache Solr deployments typically surface as 5xx errors. These are different than 4xx errors, which are typically bad requests or invalid queries. In contrast, 5xx errors are problems executing requests, which could be due to a variety of reasons that should be monitored and triaged. All newly-created deployments now show a 500 Error Count metric in SearchStax Pulse and allow customers to create threshold-based alerts on it.
Tagging Your Deployments
Customers who have tens or hundreds of Solr deployments, such as agencies with many Solr clients, can now organize their deployments more easily using Tags. For example, you can tag each deployment with a customer’s id and quickly view only deployments for certain customers.
SearchStax Pulse provides the ability for customers to create heartbeat and threshold-based email alerts. We’ve enhanced our Management API to let customers automate the creation of alerts. Our documentation provides examples of how you create various alerts here.