Thomas Franz
My feedback
13 results found
-
4 votes
An error occurred while saving the comment -
3 votesThomas Franz
supported this idea
·
-
25 votesThomas Franz
supported this idea
·
-
14 votes
An error occurred while saving the comment Thomas Franz
commented
Addtion: Do not alert only once (when a new SP / CU is available), but trigger the alert every x weeks again (if still not installed).
Thomas Franz
supported this idea
·
-
23 votesThomas Franz
supported this idea
·
-
4 votes
An error occurred while saving the comment Thomas Franz
commented
PS: there should be already an internal ticket SRP-10897 regarding this topic.
Thomas Franz
shared this idea
·
-
98 votes
Daniel Rothig
responded
Thanks for the suggestion – we’ll monitor how popular it gets
Thomas Franz
supported this idea
·
-
19 votesDaniel Rothig
responded
An error occurred while saving the comment Thomas Franz
commented
it would be nice to have multiple alerts for a single custom metrics.
Examples:
- Your application has its own job scheduler. You want to be informed if the duration of a specific job is greater than 1 hour. But you want to be informed too, if the duration was lesser than 1 minute (because then the job may have been failed).- Custom metric for specific database / server objects (as number of databases or of tables or certificates or logins or members in a specific role or ...). You want to be alerted if the number increases or decreases.
An error occurred while saving the comment Thomas Franz
commented
You are right - I could have skipped the multiply by number of seconds. On the other hand I can now see how many DBs were created / dropped (by rounding the value).
A single alert / metric would work, if you would not only me allow to compare the theshold above or below a given value but simply changed by value (regardless if + or -).
And if you would output the current value and the last value in the alert email I would be able to decide if it was a drop or create.
Regarding the built-in-documentation: go to the configure tab | custom metric | create (or edit) and click onto the question mark at "Use collected or calculated values". Neither here nor on the following custom alert page at "Define alert thresholds" I can find a hint that this will refer to the change rate per second if I use calculated values.
I'll open two new user voices for built-in alarms and multipe alerts from one metric. The non-equal-alert is the intent of this user voice request.
An error occurred while saving the comment Thomas Franz
commented
In this case I have to multiply the number of databases by the number of seconds in my refresh interval (e.g. 60 for every minute; 300 for 5 min; 600 for 10 min ...).
But this solution would help me only halfway - it removes the need to customize the alert for every server, but I still need two alerts - one for create and one for drop.
And you'll get only one alert, e.g if you collect the values once per hour and someone creates a db at 9:15 and the another one at 10:15 because the threshold remains at 1 in this case.
PS: you should mention that the threshold is the rate per second between collections in the build-in-documentation (question mark) in the SQL Monitor.
Thomas Franz
shared this idea
·
-
20 votes
An error occurred while saving the comment Thomas Franz
commented
It would be nice to have a build in alert when someone (e.g. a vendor) created or dropped a database.
Reasons:
- you may want to delete old backup files (if dropped) or have to modify / delete some maintenances
- you'll make a manual full backup of the new DB so that log-backups could be taken by your backup solution
- maybe you have to add the new DB to monitoring (as DLM Dashboard), backups (and have to consinder its the disk space at the backup drive) or an Excel-Sheet with a list of your databases :-)Real-Live-Example:
I received at around 18:45 a log-backup-overdue-alert (should trigger if there were no log backups since 10 minutes). By checking the backup directory at the next morining I figured out that there were no log backups made between 16:00 and 00:45 (so the alert should have been triggered at 16:10). Speaking with the admin for this application I discovered that the DB was dropped at ~16:00 and recreated at ~18:35 (= database creation time in the log-backup-overdue-alert). Because they did not make a manual full backup it could not create log backups until the nightly job made an automatical full backup.If I had an alert telling me, that someone dropped / created a database, it would have been easier to figure out the "strange" behavior.
Thomas Franz
supported this idea
·
-
62 votesThomas Franz
supported this idea
·
-
42 votesDaniel Rothig
responded
When we’ll be improving the alert configuration UI, we’ll keep that use case in mind
Thomas Franz
supported this idea
·
-
7 votesThomas Franz
supported this idea
·
An error occurred while saving the comment Thomas Franz
commented
Voted up (sent a similar Request to the support and they linked me back to this thread):
I have several global keywords (as backup / restore / dbcc checkdb) that should not trigger this alert and several that apply only to one server / db. If I find a new global keyword, I have to remember and modify any server with a local alert configuration whith could be a little bit errorprone. Something like {inherited} as keyword in the local configuration that would add all global keywords would be very helpful.
-
153 votes
Adam
responded
We’ve made some improvements in this area but will leave it open so you can continue to give us your suggestions
An error occurred while saving the comment Thomas Franz
commented
If they would consider to use a separate database per monitored server (plus a DB that gathers all the metrics from all DBs in views) instead only a single, big DB it would solve the problem too.
In this case you would only need to set up a free SQL Server Express on an old server / VM and would be able to full monitor a server for ~80 days (150 MB per Server and day) within the 10 GB limit (more if you aggregate the datas more often or reduces the sampling rate).
Chrome and Firefox allows you to "pin" tabs. This means that they are placed at the left side of the tab list and their title was hidden (only the favicon was shown).
I use this feature e.g. to pin my SQL Monitor and DLM Dashboard pages.