We’ve introduced a first improvement to help you better track incidents at the Data Product level.

You can now view all incidents related to a specific Data Product in a dedicated list. From this list, you can click on any incident to open the Incident Overview page directly.

We’ve made a few improvements to the integration setup experience:

1. The Credentials menu has been moved under Settings. Permissions remain unchanged .

   

2. You can now create and edit credentials directly from the integration creation page, making the setup process smoother and faster.

v642

We’ve improved the domain and subdomain selector to make navigation faster and easier, especially for large lists.

Find domains and subdomains instantly with search, eliminating the need to scroll through long lists.

We’ve improved filtering on the Incident page to make it easier to identify, prioritize, and review incidents efficiently.

Incident Count per Filter

Each filter now displays the number of associated incidents .This provides a quicker overview of impact before applying filters.

Data Source Filter Added

A new “Data Source” filter is now available in the Incident tab, allowing users to refine incidents based on their data source.

“Last Updated” Filter

We added a “Last Updated” filter to allow users to sort incidents by their most recent update event, whether triggered by a user or automatically by the system.

We improved the Jira integration to fetch and display Jira-native values directly in dropdowns. Supported fields:

• Labels
• Priority
• Assignees

This ensures better alignment and improves configuration accuracy.

🔐 New Required Jira Permission

To support user-type allowed values, a third Jira permission is now required.

• This permission is mandatory for all new Jira configurations.
• Existing clients will not lose their current setup — everything will continue working as before.

However, they will need to grant the new permission if:

• They refresh the connection (e.g., expired token),
• They attempt to resave the configuration, or
• They want access to user-type allowed values.

Version v620

The Time window and offset setting on the Asset Overview will be deprecated soon. What this means:

• This change will not affect any existing monitors.
• The configuration is now available directly in the Monitor creation flow.

The equivalent options are now available in the Monitor creation flow under the incremental scan configuration in advance settings.

• First run time window
• Time offset amount

These provide more flexible and precise controls.

📖 Learn more in the documentation.

✨What’s new

Users can now define a custom expiration delay for access tokens, overriding the default 24-month validity.

⏱️ Custom expiration settings

• Users can set a custom expiration duration (e.g. 45 days, 3 months).
• Default expiration remains 24 months if no custom value is set.

Version 607

We’ve introduced two major enhancements to our custom monitoring capabilities, giving you granular control over how you aggregate metrics and define row-level failure conditions using SQL.

What’s New?

• Custom Aggregation for Metrics Monitors: You are no longer limited to built-in functions like SUM or AVG. You can now write custom SQL aggregations to calculate unique numerical values, such as MEDIAN() or complex ratios across joined datasets (e.g., SUM(datasetA:field1) / SUM(datasetB:field2)).

• SQL Condition Custom Monitor: For complex logic that goes beyond our No-Code Condition builder, the new SQL Condition monitor allows you to define failure criteria using a SQL boolean expression. If a row evaluates to TRUE, an anomaly is triggered.

  Unlike the SQL Query Custom monitor, this monitor benefits from the same features as the other monitor types : Time Settings, Where Clause, Group By,...

ℹ️ Key Technical Notes:

Field Formatting: To reference fields in these SQL editors, use the format datasetId:fieldName.

UI Autocomplete: Simply start typing your table or field name in the editor, and Sifflet will automatically suggest the correctly formatted ID for you.

Scope: Queries must be performed on the datasets already selected in your join clause; querying external tables within the SQL snippet is not supported.

Version:v608

As organizations grow, maintaining access and ownership for every individual user becomes a bottleneck. We are excited to introduce Teams—a new way to mirror your company’s real-world structure directly within the platform.

What’s new?

You can now group users into Teams to manage permissions and ownership once — and apply them automatically to everyone in the group.

• Onboard new users faster with instant, team-level access
• Update permissions for an entire team in one action
• Clarify ownership across Domains, Assets and Incidents
• Built to reflect how your teams actually work

👉 Check this document to learn more.

Version:v603

Sifflet now automatically synchronizes your account timezone with your local browser timezone upon first login.

New users no longer need to manually select a timezone; Sifflet detects your browser’s settings to ensure all incident data and schedules are displayed in your local time.

ℹ Impact on Existing Users: If you haven’t previously updated your timezone in your profile settings, your account will now automatically match your current browser timezone.

Manual Overrides: You still have full control to manually change your timezone at any time via the User Profile icon in the top-right corner of the Sifflet application.

Version:v599