Skip to main content

Release Notes: Version 26.01

What's New ✨​

Run Trigger Schedules From The Console​

We've added a Run button to the trigger schedule details page. Now, you no longer need to run it from the API, but can start your test directly from the configuration page.

Processing Time Span Added As Alert Metric​

Process monitoring alerts can now be configured for the Processing Time Spam metric. This means it is now possible to set alerts to be sent off if a process takes longer than X hours to complete.

⚙️ Rule Framework

  • Improved rule parameter configuration: When adding a ResourceInput widget as a rule parameter, the default type is now a list. This means it is, by default, possible to add multiple resources (ie: multiple flows, datasources, etc). ⚠️Note: this means even if only one item is added, the rule framework will return a list. This does not impact existing rules, but all new rules created. It should be taken into account when inheriting rules which have a parameter of type ResourceInput

  • Flexible rule inheritance: Enabled the use of custom rules as base classes, removing the requirement to inherit directly from AbstractRule or AbstractTransformRule. Please note: inheriting from multiple classes is not supported

🖥️ UI improvements

  • Versioned API documentation: Each api version now has its own dedicated documentation page, which is accessible from both consoles.

  • Datasource View fix: Resolved a loading issue in the Datasource View that occurred when no source channels were present.

  • Flow creation defaults: Updated the default setting for new flows to Continuous | Datasource to align with the most frequent use cases.

  • Improved tag traceability Fixed issue where tags created from the console showed up as created by the System instead of the user who created it.

  • User group sorting: Implemented numerical ordering by ID for user groups in the console.

  • Faster search Added support for loading 250 and 500 results at a time for File Management, Search and Audit Events

🔌 API

  • BigQuery Sync Fix Fixed issue which prevented updates to datasources made through APIv1.5 to be reflected in BigQuery.

  • Improved ingestion validation When a trigger of type bigquery-ingest is executed with the same reference date (and a previous one has been executed successfully) a Conflict Error is returned (HTTP Error Code 409) as opposed to a 200, as it was the case.

  • Cross-console tag compatibility: Resolved a corruption issue to ensure tags can be seamlessly created and edited across both the original and new consoles.

🛠 Error Handling & Stability

  • Virtual Datasource Filtering: Improved handling for cases where a filter returns no datasources within the rule framework.

  • Sending Emails: Added audit events for errors that were previously failing silently. For instance, when having duplicate emails on to_emails and bcc_emails lists.

  • Timeseries Storage: Improved error messaging when attempting to use store_timeseries with an invalid channel_id.

  • Nested Rules: When loading a nested rule fails, the error audit event will now show in the Datasource's detail page. The message was also improved to show the rule that is trying to use the rule that is failing to be loaded.

📚 Documentation Updates

  • Flow Properties: Updated documentation regarding allowed types in flow properties.

  • CLI Resource Files: Improved the ewx-cli documentation for managing resource files.

  • Permissions: Refined documentation explaining the whitelisting permissions logic.

🚀 Notable Backend Changes

  • ⚠️ Process Pools Implementation In processing, billing accounts are now replaced by process pools, which behave the same as before. Process pools will be used, from now on, to separate the workloads in which processing happens.

    Note: Billing accounts remain as they are in terms of user whitelisting and access, but no longer define how processing is ran.

  • Processing Standardization: The rule framework now only receives standardized objects instead of legacy. This backend change cleans up the usage of legacy components in our processing, which will streamline and standardize the backend and make it easier to fix errors and develop new features in the future. (Note: This is a backend change with no impact on the end-user).

  • Improved XML File Creation: Fix issue when trying to create XML response files. This issue was caused by the mechanism to remove duplicated elements and attributes.

  • Fixed detector bug Fixed issue in Avro schema in the detectors writers

26.01.01​

Bug Fixes​

  • Fixed auth bug: Fixed an issue that was causing users being not authorized in some namespaces after using APIv2 or JWT tokens.
  • Deployment Improvement: Included backend changes to reduce manual steps needed for deployment

26.01.02​

Bug Fixes​

  • Fixed Frontend bug: Fixed an issue regarding the google analytics API, that was causing the Frontend Build to fail