For the "Oracle Long Running Transaction" alert, I have the Notification Policy set to "Use Repository Default (Currently 'Notify when level not visited since normal')", but I'm still getting notifications every 15 minutes. Any idea how to fix this?
Is the condition being met over and over again causing a new alert condition to be met?
You may look at this one: Custom Alert - Long Running Query (Oracle)
Might provide you with the ability to customize it more to your liking regarding the conditions...
Yes, but the condition is being met over and over again by the same query, so isn't the notification policy of "Notify when level not visited since normal" supposed to prevent it from repeatedly sending notifications as long as the level is consistently non-normal?
My guess is each execution is being run from a new session or getting logged in v$session as a new event.
We're just doing what we're being asked to do - track new queries that are running long. No distinction on if it's the same query.
Any opportunity to fix the query or you may want to exclude it from consideration in the where clause if it's always going to trigger this.
Nope, these alerts are all from the same session running the same query. If a metric is already at the "High" level and the next time it's evaluated again, it's still "High", why should DPA send another notification when the notification policy of "Notify when level not visited since normal"? Isn't that exactly what the notification policy is supposed to prevent, or am I misunderstanding something?
