We’re excited to announce Trinity 4.7.0, a major update focused on enhancing platform observability and simplifying alert management. This release introduces critical usability improvements for asset deployment, better control over asset configurations, and a complete migration from the ELK (Elastic) stack to SigNoz, bringing improved reliability and a modernized monitoring foundation.
New Features
This release introduces several new functionalities to improve the deployment workflow and event management.
1. DRY Run for Asset Deployment
Assets now support an automatic DRY Run during the final Review stage of the deployment flow, helping to catch issues early and ensuring safer deployments.
2. Version-Based DB Migration Configuration
Assets now allow version-specific migration configuration, enabling precise control of database migrations per asset version.
Info: DB migration configuration is based on the version selected in Step 1: Environment and Namespace.
3. Configurable Asset Deployment Timeout
The timeout duration for asset deployment is now fully configurable, giving more flexibility for long-running deployments.
4. Copy Option in Asset Deployment Error Dialog
A new Copy to Clipboard button is added inside the deployment error dialog, making it easy to copy logs and share with support teams.
5. Post-Deployment Resource Updates for Assets
Users can now update replica count, CPU limits, CPU requests, memory limits, and memory requests after an asset has been successfully deployed.
This allows fine-tuning resource consumption without needing to redeploy or modify Helm values manually.
6. Multi-Select Export in Cron Events List
You can now select multiple cron event records and export them at once directly from the Cron Events List table.
This improves efficiency when analyzing or backing up multiple event entries.
Enhancements
1. Storage Alert Removed
The Storage Alert designed to monitor Elastic storage usage is no longer relevant and has been removed from the system following the ELK deprecation.
2. Node Storage Alert Upgraded
The Node Storage Alert has been fully migrated from Prometheus to SigNoz. And redesigned Alert Configuration UI to reflect SigNoz-based metric inputs.
3. Environment Initialization – SigNoz & OTEL Collector Configuration
Users must now provide domain details for SigNoz and the SigNoz OTEL Collector during environment initialization to ensure each environment is fully connected for observability.
4. New Environment Configuration Options (SigNoz Integration)
The Environment Details page now includes new fields that allow users to easily manage SigNoz configurations, including the ability to add or update the SigNoz API Token, SigNoz URL, and OTEL Collector URL.
5. Removal of Elastic Logs Section
With the deprecation of the ELK (Elastic) Stack, the Logs section powered by Elastic has been fully removed.
Bug Fixes
-
Migration App Cleanup – Fixed an issue where the migration app was not getting undeployed in certain deployment scenarios.
-
Deployment Rollback – The deployment rollback now works correctly and reverts to the last successful version.
-
DB Migration Endpoint – Resolved a problem where the migration endpoint was called twice during DB migration.
-
Unsaved Changes Warning – Added a confirmation prompt when attempting to leave the asset deployment page with unsaved changes.
-
Duplicate Resource Validation – If a domain CR, secret, or storage already exists, creating another with the same name now shows the correct validation errors.
Database Migration (Before Upgrading)
Docker Images
Images Updated In This Release
| Repository Name | Docker Image | Tag |
|---|---|---|
| trinity-frontend | neutrinos.azurecr.io/trinity/trinity-frontend/ui | 25.11.4.7.0-azure |
| neutrinos.azurecr.io/trinity/trinity-frontend/api | 25.11.4.7.0-azure | |
| trinity-orchestrator | neutrinos.azurecr.io/trinity/trinity-orchestrator | 25.11.4.7.0-azure |
| trinity-db-operations | neutrinos.azurecr.io/trinity/trinity-db-operations | 25.11.4.7.0-azure |
| trinity-assets-orchestrator | neutrinos.azurecr.io/trinity/trinity-assets-orchestrator | 25.11.4.7.0-azure |
| trinity-deployments | neutrinos.azurecr.io/trinity/trinity-deployments | 25.11.4.7.0-azure |
| trinity-promscale-connector | neutrinos.azurecr.io/trinity/trinity-promscale-connector | 25.11.4.7.0-azure |
| trinity-alerts-base-app | neutrinos.azurecr.io/trinity-utils/alerts-base-app | 25.11.4.7.0-azure |
| trinity-alerts-email-service | neutrinos.azurecr.io/trinity/trinity-alerts-email-service | 25.11.4.7.0-azure |
| trinity-app-logs | neutrinos.azurecr.io/trinity/trinity-app-logs | 25.11.4.7.0-azure |
Closing Note
We continue to focus on delivering better functionality, stability, and an improved user experience. Thank you for your continued support and feedback — it helps us make the platform better with every release!










