Alert Tuning : Please add export to CSV option
This comes up on a weekly basis for us but can you please add the ability to export all the items displayed on the Alert Tuning tab to a CSV. Many clients, dev groups ask us for a report on all the metrics that we are monitoring for a group of devices, location, technology and what thresholds are in place. The alert tuning tab has exactly this info but we cannot share with anyone in a meaningful manner. The "Threshold Report" is not a viable option as it spits out EVERYTHING and quickly maxes out on the 50k line limit. We just need the Entries listed in the Alert Tuning tab when clicking on a any device in the tree.129Views3likes4CommentsDevice Notes Tab
Currently, my team tends to attach small important notes for devices (firewalls, servers, switches, etc.) in the Description box. These notes might indicate if the device is supposed to be decommed soon, which vault the device's credentials are stored in, if the device is fully managed, who/manages owns the device, who deployed the device, or various other things. The description box is not designed for this. So, there are obviously many issues with it. No accountability, no formatting, no separation, etc. Could we please request a feature where each device in LM has its own proper "Notes" tab? Notes could be time-stamped, author-stamped, edited, or deleted. Examples: "Device is scheduled to be decommissioned in 2 months. -User123 4/30/2025 18:00:00UTC" "Device is not managed. No creds available. Alert client in event of issues. -User567 4/05/2025 03:00:00UTC" "Power Supply replaced on 2/10/2024. -User567 2/10/2024 10:00:00UTC" Below shows where a note has been added to the Description Box for this device, indicating the PSUs were reseated on 4/30/2025. If there were a Notes tab, this snippet could be put there instead. Anyone seeing that device afterward would see that User123 made that note today at 2pm. Someone could add an additional note a few months later indicating those PSUs have been replaced, while removing the old note. If there is already a feature similar to this (or one in the works), please let me know.60Views2likes5CommentsFeature request: SDT timings similar to Patch Tuesday schedules in Azure
Basically within azure you can schedule patches for the second Tuesday of the month +n days so you can apply patches the Thursday after patch Tuesday, which doesn’t necessarily fall on the second Thursday of the month, Take the current month as an example, the second Thursday falls before patch Tuesday Would love a feature option with SDT to accomplish this for more automation instead of having to set up an SDT for patching every month.115Views2likes1CommentExclusion of Alerts triggered during the SDT in Alerts report
It would be really helpful if this functionality were available in the out-of-the-box (OOB) template. Currently, the OOB template includes active SDT alerts but doesn’t account for completed ones. When running the report, it pulls all alerts triggered in the console, the SDT filter if set to "Yes," it only shows alerts currently in SDT and it exceeds the timeframe we kept for the generating a report, and none are active, it returns zero results. Is there an option to generate a custom report that excludes alerts triggered during the SDT time frame using any API.87Views6likes2CommentsDashboard Filtering Using Instance Properties
Recently I came up with a way to attach custom properties to instances created by the Cisco DNAC Devices DataSource. I was able to separate the locations of our devices based on our naming scheme of the device into 4 different categories and I was hoping to use these and apply them using the dashboard dynamic filters, only to see that I am limited to resource properties only. I’m aware that by making an instance group we could determine what kind overview graphs we see, but when we have hundreds of buildings, it becomes a heavy task to list all those groups and filter through thousands of switches.Solved139Views5likes3CommentsCreate a LogicModule status alert
Release notes have been including notice about deprecated logicmodules and indicated replacements for a while and this is great. I would like to request that consideration be given to what I think would be even better. A few ideas: the current way that replacement modules are presented in the Release Notes (side by side columns limited by screen real estate and page layout) can make it tedious to conclusively determine which module is the replacement since often the text of names wraps to additional lines. So finding some way change to change this presentation that shows an unequivocal 1:1 relationship between a deprecated module and its replacement would be awesome. If you navigate to MyToolbox and select a module, the bottom half of the screen opens with details about this module. There is a tag present that says "In Use". Maybe another tag could be created that says "Deprecated" and clicking on it takes you to the replacement module? In the reverse direction, if you navigate to the Exchange and select a module, maybe there could be a "Replacement For" tag, that if clicked upon takes you to the module/s that it replaces? What about if there was some way to create an OOB filter & Saved/Favorite view in My Toolbox that presents a list of deprecated modules, each with a clear mechanism that matches it to its replacement? Find some way to generate an alert (probably even with its own icon/color to give it maximum distinction in the Alerts Tab/table) when a module's status changes to 'deprecated' and have the alert message text includes exact replacement module details (Origin ID?) Maybe an OOB dashboard with a widget that dynamically populates a table when a Logicmodule in My Toolbox status changes to "deprecated" and includes its replacement?127Views4likes8Comments