We’re excited to announce Trinity 4.5.1, a power-packed release with brand new features, usability improvements, and important bug fixes to streamline your deployment experience. From cron job management to an alert testing playground, this update is all about giving you more control, flexibility, and clarity in your workflows.
Here’s what’s new:
New Features
New Features1.Cron Job Management
You can now create, update, delete, and view cron jobs, along with detailed job audits split into api triggers and cron triggers for better traceability.
2.Alert Playground
Test your alert API configurations before saving with the new alert test playground—ensuring alerts reach the right place, every time.
3.Notifications to Teams
You can now send alert notifications directly to Microsoft Teams using webhooks—keeping your team instantly informed.
4.Retention Policy Management
A new section to manage log and trace retention policies for Metricbeat, Filebeat, and Tracing, all in one place.
5.Delete Unwanted Environment Variables
Clean up your deployments by removing unnecessary environment variables during the deployment process.
6.Smarter Variable Selection
During deployment, you can now select variables from previous, staged, or successfully completed deployments, helping you save time and avoid repetition.
7.Improved Storage Mapping
The storage list now only includes cluster-created storages, filtering out those provisioned via Trinity for a cleaner view.
8.Email Host Configuration
Users can now configure the email host while setting up email alerts—offering greater flexibility in how notifications are sent.
9.In-Flow Email Configuration for Alerts
You can now add a new email configuration directly while setting up an alert, without switching screens or breaking your flow—quick and seamless.
Bug Fixes
Bug Fixes1.Auto-filled Node Pool Configuration
Node pool details are now automatically filled in using data from past deployments, reducing manual input and setup time.
Database Migration (Before Upgrading)
| Repository Name | Docker Image | Tag |
|---|---|---|
| trinity-frontend | neutrinos.azurecr.io/trinity/trinity-frontend/ui | 25.07.4.5.1-azure |
| neutrinos.azurecr.io/trinity/trinity-frontend/api | 25.07.4.5.1-azure | |
| trinity-orchestrator | neutrinos.azurecr.io/trinity/trinity-orchestrator | 25.07.4.5.1-azure |
| trinity-db-operations | neutrinos.azurecr.io/trinity/trinity-db-operations | 25.07.4.5.1-azure |
| trinity-assets-orchestrator | neutrinos.azurecr.io/trinity/trinity-assets-orchestrator | 25.07.4.5.1-azure |
| trinity-deployments | neutrinos.azurecr.io/trinity/trinity-deployments | 25.07.4.5.1-azure |
| trinity-promscale-connector | neutrinos.azurecr.io/trinity/trinity-promscale-connector | 25.07.4.5.1-azure |
| trinity-alerts-base-app | neutrinos.azurecr.io/trinity-utils/alerts-base-app | 25.07.4.5.1-azure |
| trinity-alerts-email-service | neutrinos.azurecr.io/trinity/trinity-alerts-email-service | 25.07.4.5.1-azure |
| ttrinity-app-logs | neutrinos.azurecr.io/trinity/trinity-app-logs | 25.07.4.5.1-azure |
Closing Note
Closing NoteWe 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!