5 posts tagged with "Changelog"

Parseable v1.6.0 is out now. Checkout the new features, improvements and bug fixes in Parseable since the last release.

Features​

Azure Blob Storage support​

In our quest to be truly multi-cloud, we have now added support for Azure Blob Storage. You can now deploy Parseable on Azure and use Azure Blob Storage as the backend data storage. This is available in the latest release v1.6.0.

With this release, Parseable supports AWS S3, other S3 compatible stores, and Azure Blob Storage - this gives you unparalleled flexibility to choose the cloud provider of your choice.

Shareable URLs for dashboards and explore pages​

This was one of most commonly requested features. You can now share your dashboards and explore pages with a simple URL. To share a dashboard or explore page, click on the share icon in the top right corner of the page. This will generate a URL that you can share with your team members.

Note that you can share the URL with anyone who has access to your Parseable instance. This means they will need to login to their Parseable account to view the shared dashboard or explore page.

Click on the share button in the top right corner of the dashboard to generate a shareable URL.

Click on the share button in the top right corner of the explore page to generate a shareable URL.

Generate schema for a log event​

One of the common challenges with dynamic schema is that users loose fine grained control over the field types. For example, they can't enforce a field to be a string or a number.

The alternative is to create streams with static schema, but that requires users to define the schema upfront. This can be cumbersome and error prone.

With this release, we have added a way to generate schema for a log event (when creating a static schema stream). To use this feature

• Click on the Create Stream button on landing page.
• Select Static Schema as the schema type.
• Toggle the Auto Detect Fields and Datatype button to ON.
• You can now either import a json file or paste a valid json or json array, with sample log events.
• Click submit to generate the schema. This will be populated in the schema editor for you to review and edit.
• Review the schema and click on Create Stream to create the stream.

Enhancements​

Retry object storage calls​

Parseable server now ensures any failed object storage API calls will be retried. This is a best effort retry mechanism and will help in cases where the object storage service is temporarily unavailable.

Sync files on Sigterm​

With this release, Parseable server will sync all the files to backing storage when it receives a SIGTERM signal. This ensures that all the data is safely stored before the server shuts down.

Detect timestamp in log events​

For dynamic schema streams, the server incorrectly detected timestamp fields as string fields. This is now fixed. The server will now correctly detect timestamp fields and store them as timestamp fields. This helps better utilize the timestamp fields in queries and visualizations.

Date range picker improvements and Timezone support​

We have made several improvements to the date range picker in the explore page. You can now select a date range with a single click. We have also added timezone support to the identified time columns. This will help you select the correct date range based on your timezone.

Breaking Changes​

The new helm chart version 1.6.0 is not backward compatible with the previous versions. Specifically, we've removed the field .Values.local. We've added a new field called .Values.store, which is a required field. Possible values for this field are local-store, s3-store or blob-store.

Please update your helm chart values accordingly.

Parseable v1.5.4 is out now. Checkout the new features, improvements and bug fixes in Parseable since the last release.

Features​

Custom Dashboards​

Search and visualization are key aspects of making sense of ad hoc log events. Search helps you when you know what you're looking for, while visualization helps in cases where you don't know yet. We released the first version of dashboards as a part of version v1.5.0. We made several improvements based on user feedback in last few releases.

Now, with v1.5.4, our fully customizable dashboards are out of beta! Tailor your visualizations with tiles created by SQL queries. Data fetched by a SQL query will be transformed to supply to visualizations, including charts, graphs, and tables.

With this release, you can:

• Choose from a selection of visualization options, including colors, sizes, orientations, and custom tick formats.
• Export your dashboard views in PNG, CSV, or JSON formats.
• Organize tiles with an adjustable, draggable layout to create dashboards that suit your workflow.
• Build and share unlimited dashboards, and import tile configurations with just one click.
• Access pre-built dashboard templates to get started quickly.

Explore page improvements​

The explore page includes an expandable sidebar for streamlined data exploration. This enhancement lets you:

• Quickly view columns and schema for each stream.
• Pin, drag, and arrange columns with full control over column width, word wrapping, and visibility settings to suit your preferences.

Performance improvements​

Version v1.5.4 includes performance improvements in query API specifically. You can expect faster query execution times and improved response times for queries. In our internal benchmarks based on ClickBench, we observed a 30% improvement in query execution times.

Bug Fixes​

Role-Based Access Control (RBAC)​

We’ve fixed bugs in RBAC, ensuring reliable and secure experience. Console now only exposes an option only if the logged in user has permissions to call the corresponding API. So, if you don't see an option that you expected to see, please check Review detailed API access control documentation here.

OAuth login issue​

We fixed an security issue where redirect URI and base URI should be the same for OAuth login. This ensures that the user is redirected to the correct page after login.

Parseable v1.4.0 is out now! We've added added features and enhancements based on inputs from the community.

This release puts on spotlight on the new SSD / NVMe based hot tier for faster data retrieval and reduced S3 costs, a versatile JSON view from on the explore page, saved filters in pb for streamlined workflows and much more. Let's dive into the details.

New features​

Hot Tier in distributed Parseable cluster​

Parseable now allows tiering of data, this means you can store data locally on the query node, for faster retrieval and reduced S3 costs. We recommend using dedicated SSD on the query nodes to fully leverage the performance. This feature is especially useful for real-time data analysis and monitoring, in cases where most of the queries are targeted to local Refer the documentation for more details.

JSON View from the Explore Page​

Several of our users love the table view for even the unstructured log events, but we also got several requests for a raw view of the data. We have now added a JSON view to the Explore page, with the raw JSON data for each log event.

The JSON view also allows you to run a text search or jq queries on a given query result. This offers a more flexible way to explore the data, especially for the unstructured logs, exactly the way you want.

Saved filters in pb​

pb, the Parseable CLI client now supports saving, applying or deleting filters. We introduced the saved filter feature on the server in previous release, and it was an instant hit among the users.

The CLI users however felt left out. With this release, we have added the saved filter feature to pb as well. You can now save, apply or delete filters from the CLI itself. This feature is especially useful for the users who prefer to work from the terminal.

Enhancements​

Partition management for streams​

If you use streams with custom partitions, or have historical data with custom time partitions) at the time of stream creation. You can now manage the columns and partitions for the streams in the stream management page.

Unified filter and SQL modal​

Filter Builder and SQL options are now merged into a single modal for easy switching between the two.

Delete offline ingestors​

You can now delete all the entries for an offline ingestor from the cluster page. To remove a live ingestor, you need to stop the ingestor first and then delete it from the cluster page.

Copy capabilities for data​

Copy column text directly from the explore page from both table and JSON view.

Honor new line characters in table view​

The table view now respects new line characters in log event, displaying field data in multiple lines if applicable.

CORS configuration​

The server now supports configurable Cross-Origin Resource Sharing (CORS) through the environment variable P_CORS. By default, CORS is disabled, but users can enable it by setting P_CORS=false. Refer the documentation for more details.

Security​

One of our dependencies, the object_store crate, was detected with a security vulnerability. Link to the relevant CVE.

With the version v1.4.0, we have updated the object_store crate to the 0.10.2, which has the fix for the vulnerability. We recommend all users to upgrade to the latest version to avoid any security risks.

Load testing​

Since the last release, we have made it a point to include ingestion (load testing) performance in the release notes. We have tested the ingestion performance for this release as well, and we are happy to report that the performance has improved by 10% compared to the last release.

Parseable setup​

Parseable v1.4.0 was deployed on Kubernetes cluster in distributed mode. We set up 3 ingest nodes and 1 query node in the Parseable cluster. Each Parseable pod was allocated 2 vCPU and 4 GiB memory. We also ensured to deploy each pod on a separate node to avoid any resource contention.

Load generation​

We use K6 on Kubernetes for load testing. K6 is a modern load testing tool that allows you to write test scripts in JavaScript. For simpler deployment and ease in scale out, we used the K6 Operator. Refer the steps we followed to set up K6 on Kubernetes in this blog post.

The load testing script is available in the Quest repository.

Results​

Test Run 1: 1 Query, 3 Ingestor Nodes. 2 vCPU, 4 Gi Memory each node. 15 k6 clients to ingest data, Number of batches per http requests - 300, Run time: 10 mins

Test Run 2: 1 Query, 3 Ingestor Nodes, 3 vCPU, 4 Gi Memory each node, 15 k6 clients to ingest data, Number of batches per http requests - 525, Run time: 10 mins

Note: We're hard at work to run a better, standardized load test for Parseable. We will share the results in the upcoming release notes. Also, we'll add the query performance results in next releases for a better overview.

Parseable v1.3.0 is out now! This release includes a good mix of new features, improvements, and bug fixes. In this post, we'll take a a detailed look at what’s new in this release.

We'll love to hear your feedback on this release. Please feel free to create an issue on our GitHub or join our Slack community.

New Features​

Saved filters and queries in the explore logs view​

A long-pending request from our community has been the ability to save a filter in order to return at a later date to a specific view without having to re-apply the filter from scratch. The same goes for queries.

We initially considered implementing this as a purely client-side feature, i.e. on the Console only, to deliver it more quickly. The idea was to use the browser's local store to keep a saved filter’s details and then load it from there on demand. But this approach would have been too limiting; for instance, the same user would not have been able to see their saved filters when logging in from a different browser or IP address. Also, sharing filters across users would not work and any browser event that cleared local storage would essentially mean the loss of all the saved filters, many of which are carefully created after months of analysis.

With the release of Parseable v1.2.0, we are excited to introduce a major upgrade focusing on enhanced querying and ingestion capabilities. This new version brings a suite of powerful features designed to improve the speed, flexibility, and compatibility of log management.

Our focus this release has been to improve user experience when querying data. Additionally, we made several server side improvement to enhance the query performance.Let's go over the highlights of this release.