Comments
Sort by recent activity
Additionally, it is also possible to export the data on Disk Usage e.g. https://monitor.red-gate.com/Estate/Disks It is not currently possible to schedule this to be emailed as a monthly report, but you may find the data useful. / comments
Additionally, it is also possible to export the data on Disk Usage e.g. https://monitor.red-gate.com/Estate/DisksIt is not currently possible to schedule this to be emailed as a monthly report, but...
Version 8.0.23 has been released and includes the return of the ability to add a comment to multiple alerts. The next release should also see the return of the comment icon so you can see at a glance which alerts have comments - I'll update this thread once this is released.
These were initially removed while developing the ability to group alerts in the new alert inbox, and it’s taken us longer than expected to reintroduce them – apologies for the inconvenience we know this has caused. / comments
Version 8.0.23 has been released and includes the return of the ability to add a comment to multiple alerts.The next release should also see the return of the comment icon so you can see at a glanc...
Hi, we have an update on this. The information was showing if backups had occurred during the selected window, rather than if any backups existed at all. However we recognise that 'No backups' could be misleading (and alarming!) so we have redesigned the information to show the time period it refers to, and also show when the last backup occurred prior to that. This can be seen in the latest version (8.0.25) - we hope this solves the issue you reported. [image] Thanks, SQL Monitor Development Team / comments
Hi, we have an update on this. The information was showing if backups had occurred during the selected window, rather than if any backups existed at all. However we recognise that 'No backups' coul...
Thanks for your comment, it's an interesting point. We haven't excluded reportservertempdb because it seems it can have its uses:
The only reason to backup the reportservertempdb is to avoid having to recreate it if there is a hardware failure. In the event of hardware failure, it is not necessary to recover the data in reportservertempdb, but you do need the table structure. If you lose reportservertempdb, the only way to get it back is to recreate the report server database.
https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/backup-and-restore-operations-for-reporting-services
However, we'll give this some consideration to see if it still makes sense, and meanwhile if you raise this as a suggestion on Uservoice it may get additional support.
Regarding the configuration of alerts, we agree this could definitely be improved and we intend to address this later in the year. Apologies for the inconvenience and thanks for your patience.
Adam / comments
Thanks for your comment, it's an interesting point. We haven't excluded reportservertempdb because it seems it can have its uses:
The only reason to backup the reportservertempdb is to avoid havin...
Hi Karl,
This is an area we are exploring how best to improve. Currently you can drag the focus area to show the top 10 over a given time period - in the example screenshot, the table is showing the top 10 blocking processes overnight (from 8pm to 6am). [image]
I'm interested to understand what you would ideally want to be able to do, and what you would do with the output?
Thanks,
Adam / comments
Hi Karl,
This is an area we are exploring how best to improve. Currently you can drag the focus area to show the top 10 over a given time period - in the example screenshot, the table is showing th...
Hi,
We think this sounds like it would be a useful improvement. If you add it as a suggestion on Uservoice and it gets additional support, this would certainly help us prioritise looking further into it.
Were you thinking of something along the lines of how we show this in the Deadlock visualisation below? [image]
Thanks,
Adam / comments
Hi,
We think this sounds like it would be a useful improvement. If you add it as a suggestion on Uservoice and it gets additional support, this would certainly help us prioritise looking further in...
Thanks - I've added your suggestion to that Uservoice item so we can make sure we consider it. / comments
Thanks - I've added your suggestion to that Uservoice item so we can make sure we consider it.
Thanks for the additional detail - we'll get back to you with more information... / comments
Thanks for the additional detail - we'll get back to you with more information...
Ah okay, in that case, you can view and edit the defaults for the different collections by using the Configuration File editor.
First, locate the configuration file on the machine where the SQL Monitor Base Monitor service is hosted. Location: C:\ProgramData\Red Gate\SQL Monitor
File Name: RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config
Make a copy of this file and name it something useful like RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config_backup
This will act as a backup of the configuration file so that your changes can be reversed.
Next, run the SQL Monitor Configuration Editor as an administrator (right click > Run As):
C:\Program Files\Red Gate\SQL Monitor\BaseMonitor\Tools\ConfigurationFileEditor.exe
You will be prompted to "Load a configuration file". Find the .config file detailed in step 1.
You will be presented with a list of all the configuration options available. These relate to each item in the polling schedule. Any check box which is un-checked automatically uses the default - to check what the default is you can check the box, but not make any changes and the value shown will be the default value.
If you make any changes, once complete, click "Save Changes" and restart the SQL Monitor Base Monitor service. If you have any unexpected results then please delete your edited configuration file and rename the copy (then also restart the service). If you are not making changes, just close without saving.
Does that help?
Thanks,
Adam / comments
Ah okay, in that case, you can view and edit the defaults for the different collections by using the Configuration File editor.
First, locate the configuration file on the machine where the SQL Mon...