Version 1.10.0 of the Cmd web app introduces a new interface that lets you easily configure data export to long-term storage, provides an option to 'archive' old servers without contacting support, updates other interface elements, and fixes several bugs.
Read on to learn more!
Saving data in long-term storage is often a top priority. The new data export interface introduced in this release enables you to quickly set up data export — without contacting Cmd support. Your preexisting data exports will also appear on the new interface.
After set up, the new interface lets you monitor the status of each data export: time active, time of last successful export, any data lost, and more:
The redesigned date picker on the Sessions tab offers more preset options, and lets you define a 'custom' preset to save for future use:
As before, you can focus on a window of time by highlighting it with your mouse, and adjust your zoom with the magnifying glasses:
File modification alerts
Alerts generated by File modify triggers now show which files were modified, and let you quickly inspect the changes by clicking them:
Triggers: "Show modification history" is now "Trigger history"
We've renamed the feature that allows you to review changes to triggers over time.
This was suggested by users, and we agree — the new name is better. Thanks!
(You can access this feature by clicking the three-dot menu to the right of a trigger.)
Fixed a bug that caused inconsistencies between the number of alerts appearing in "Unresolved alerts" emails and the Cmd web app's Alerts page.
Deep links to a Cmd project (such as to its Alerts or Sessions pages) will now switch you to that project. Previously, you would get a 404 notice if you tried to follow one when you were signed in to another Cmd project.
When you add new users, entering an invalid email will no longer create a blank list entry.
We are excited to get this version into your hands, and to continue iterating. Please feel free to reach out with any questions, comments, or feedback.