Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
We have implemented service now Integration with APPDynamics with service and we see lot of noise for the alert that are getting generated and we want to fine tune it and is there any best practices for the same which talks about correlation and finetuning to reduce the same
We have a Knowledge base article, How do I use AppDynamics with ServiceNow?
Please check it out and let me know if it helped! If you learn anything, please do share those learnings back as a reply to this post. Knowledge sharing is what drives this community forward.
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
What are your trigger conditions for the rule? Are they a simple count, or deviation from baseline? If so, you could try setting the rule to look for multiple occurrences in the last 30 minutes.
We've found this can substantially reduce the violations created by single spikes.
The process I go through for this is to look at each event, examine the data points in the metric browser that caused the event to trigger, and determine whether it was a true or false positive. From there I try to figure out a rule that wouldn't be triggered by the false positive. It can be a very iterative process....