We are delighted to announce that Imply 3.2 is now available! Imply 3.2 is based on Apache Druid 0.17 (Druid’s first Apache top level project release) and adds new cloud management, alerting, reporting, and data loading features.
Imply 3.2 is based on Druid 0.17.0, which you can read about in a separate blog post. The Druid 0.17.0 release includes over 250 new features, performance enhancements, bug fixes, and major documentation improvements.
Highlights include:
This release includes a fully managed solution for your cloud. The cloud manager lets you deploy and manage clusters in your own cloud via Kubernetes.
Newly released cloud management functionality includes:
It is now possible to define regularly scheduled reports to be delivered in-application or via email. Scheduled report configurations support all existing data export formats, such as CSV, JSON, and Excel as email attachments. Additionally, scheduled reports support email delivery to external, non-Pivot users.
This release brings many improvements to Imply Pivot’s alerting functionality. Alerts can be configured against multiple condition thresholds, checking against either aggregate measures for a dimension or against dimension values, and users will be notified when alerts are triggered via either email or webhook.
In this release we are adding the ability for Druid to read binary data (e.g. ORC, Parquet) from HDFS directly. This means that if your data is stored in a data lake you can now index it in Druid via a point and click wizard directly, without using Hadoop.
This release also expands Pivot’s customization ability. Pivot can now be configured to hide information about the underlying version and can also be configured to display a custom message when a logged-in user does not have any permissions, e.g. when a user authorized via LDAP has no matching groups.
The Imply 3.2 distribution is now available for download as a 30-day trial, or you can subscribe to a 30-day trial of the Imply Cloud managed service based on Imply 3.2, at https://imply.io/get-started.
Why You Shouldn’t Have to Delete Your VPC Flow Logs
When a security incident happens, investigators almost always start with the same questions: Which systems communicated? Where did the traffic originate? What changed before the incident? Was data exfiltrated?...
Learn MoreSplunk Smartstore vs Lumi Loglake: Two Very Different Ways to Search Logs in Object Storage
One copies data back before it can be searched. The other queries it where it lives. Lumi Loglake lets Splunk teams query logs directly in object storage, including AWS S3, Delta Lake, Apache Iceberg, using...
Learn MoreSupercharging Schema-On-Read: Logs in Object Storage Don’t Need a Data Catalog
Machine data architectures are rapidly changing. As telemetry volumes continue to grow and as costs rise, organizations are increasingly moving logs and other machine data into object stores such as AWS S3....
Learn More
Vadim Ogievetsky