Join the Conversation
- Find Answers
- :
- Splunk Products
- :
- Splunk AppDynamics
- :
- Retrieving specific Health Rule Violations via the...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
I've recently begun getting my head around the AppDynamics API and how it all works. As a small excercise I wanted to produce a list showing all the times a specific health rule has triggered a violation.
I was hoping this would get me the result I was after:
curl --user me@tenant:secret 'https://saasaddress/controller/rest/applications/applicationid/problems/healthruleviolations?time-range-type=BEFORE_NOW&duration-in-mins=mins&name=Health+Rule+Name'.
Unfortunately, this gives me all of the violations by all health rules, and not violations by name.
I supposed there are a few questions I should ask here:
Is this the right way to go about it / am I probing the right location?
Can the above accept a value of name, or am I limited to whats listed in the following: https://docs.appdynamics.com/display/PRO45/Alert+and+Respond+API#AlertandRespondAPI-RetrieveAllHealt...
Also, for reference, is there a schema diagram that shows the relationships with all API functions?
Cheers!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since the API does not provide a "filter by Health Rule Name" option, your best bet is to fetch all the Health Rule violations, then iterate through them and ignore the ones not associated with the target Health Rule.
Regards,
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since the API does not provide a "filter by Health Rule Name" option, your best bet is to fetch all the Health Rule violations, then iterate through them and ignore the ones not associated with the target Health Rule.
Regards,
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
