Mark Freeman
My feedback
25 results found
-
1 voteMark Freeman
shared this idea
·
-
2 votes
An error occurred while saving the comment Mark Freeman
supported this idea
·
-
18 votes
An error occurred while saving the comment Mark Freeman
commented
Another way of looking at it is that I want to be able to have a monitoring target in multiple groups, allowing multiple orrganizational schemes to exist at the same time:
Project
Prod
Server1Prod
Project
Server1I care about: Project/Product, Region, Environment (Dev, Test, Prod, etc.). I should be able to set each of those up as a top level grouping and have all my monitoring targets in the appropriate place in a hierarchy under each of them, so I can easily find them within any top-level grouping.
Mark Freeman
supported this idea
·
-
10 votesMark Freeman
supported this idea
·
An error occurred while saving the comment Mark Freeman
commented
SQL Sentry shows the login, host, and application for queries in some areas of the product. So it can be done.
I get that this type of data would be lost in aggregation after a set number of days or weeks, but only having the detail for set time would be sufficient.
If a query is throwing an error or causing a major performance issue, I need to who ran it. In Azure SQL DB, I would have to keep an Extended Events Session running to capture that. With hundreds of databases, that creates not only performance overhead, but a maintenance issue.
-
22 votesMark Freeman
supported this idea
·
An error occurred while saving the comment Mark Freeman
commented
My browser is in the eastern US, EST/EDT, currently UTC-5. But next week, I think it will be UTC-4.
I monitor servers all around the globe. Having to do this extra time conversion on top of the one for whatever the current offset from UTC the Azure region housing the database I’m looking at is just one step more than my brain wants to handle. Many of those switch to/from Daylight Savings time during a different week than the US does, and go in a different direction, making this even more difficult. I would love to be able to configure a time zone for each server and then have an option to show all times for anything related to each server in that server’s local time.
As a possible half-way step, just add a setting that chooses between the current behavior and displaying everything in UTC.
And don't get me started about trying to define alert suppression windows when fighting with time zone calculations when I'm in one TZ, the base monitor is in another, and the server is in a third.
I want to choose between my local time, the monitoring service's time, or a manually entered time per monitored server or even per database.
For example, I am in EST, I have monitoring services in North America, Europe, and Asia. Each covers servers that are in different time zones within a monitoring server. Some have many databases, each of which could have users mainly from a different time zones within a region. When I look at a metrics chart, the first thing I want to know is if the issue I am looking at occurred within the users' normal work hours or not. It is a nightmare to figure out when everything is presented in my browser's local time zone, but the database is mainly used by people in New Zealand and is covered by the Asia monitoring service (which may have a time zone from China).