Splunk AppDynamics

API Query - CLR Crashes

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I'm trying to write an API Query to retriev all the CLR Crashes from a single tier...

I've been able to retrieve application errors with the following but haven't been able to get any furhter;

http://gbwyeon0083:8090/controller/rest/applications/15/events?time-range-type=BEFORE_NOW&duration-in-mins=60&event-types=APPLICATION_ERROR&severities=WARN,ERROR&output=JSON

Any help would be greatly appreciated.

Cheers

Labels (3)
0 Karma

Atyuha_Pal
Contributor

As per the document we can extract the event data at the application level only not the specific tier level through the rest api

https://docs.appdynamics.com/display/PRO43/Alert+and+Respond+API#AlertandRespondAPI-RetrieveEventDat...

Please refer to the rest api and check whether it works for you 

https://<controller url>/controller/rest/applications/<applicaion id>/events?time-range-type=BEFORE_NOW&duration-in-mins=720&output=JSON&event-types=CLR_CRASH&severities=WARN,ERROR

http://gbwyeon0083:8090/controller/rest/applications/15/events?time-range-type=BEFORE_NOW&duration-in-mins=720&output=JSON&event-types=CLR_CRASH&severities=WARN,ERROR&output=JSON
Hope it will help .

Thanks,

Atyuha

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...