Skip to main content

Seculyze 4.0.1 Release Notes

A redesigned Cost module with a fresh look, improved usability, and more accurate cost calculations, budgeting, and reporting.

Overview

Seculyze 4.0.1 brings a completely new look to the Cost module, along with sharper accuracy in Sentinel cost tracking. We corrected discrepancies in log source cost calculations - including 30-day cost figures - refined ingestion budgeting logic, and added month-over-month lookback so historical cost data stays accurate as usage patterns change. We also fixed several reporting issues to keep your reports reliable.




Detailed Description

This release gives the Cost module a new look and feel, designed for a clearer, more intuitive user experience. Alongside the redesign, we focused on getting the numbers right: we identified and corrected discrepancies in how log source costs were calculated and applied the same scrutiny to ingestion budgeting, which now includes improved error handling. A new month-over-month lookback approach also keeps historical cost data intact rather than resetting it. On top of these cost improvements, we corrected several report generation bugs that could surface stale or incorrect data.

Release Highlights

📊 Cost Module Refinements — More accurate budgeting, log source cost tracking, and monthly lookback logic

🛠️ Reporting Accuracy Improvements — Corrected bugs in monthly reports

⚙️ Platform Stability — General performance and reliability improvements

Changes

🏗️ Added Functionality

  • Added month lookback logic for more accurate historical data collection

  • Enhanced budgeting functionality with improved error handling

📊 Improved Features

  • Refined Cost module calculations across multiple phases (log source cost visibility and estimates)

  • Updated the 30-day log source calculation method for greater consistency

🛠️ Bug Fixes

  • Fixed monthly reports incorrectly naming threat-intel feeds and enrichment markers

  • Fixed reports incorrectly including internal-only labels

  • Fixed inaccuracies in report data tied to recent Cost module changes

Did this answer your question?