Splunk AppDynamics

Health rule for CLR Crash

Sundarapandian_
Path Finder

Hi,

Is there a way to,

1. Create a health rule for CLR crash events to use them dashboards?

2. Modify the default severity of CLR crash events from WARNING To CRITICAL?

Please advise

Thanks,

Sundar

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I dont think you can specifically create a health rule for CLR crash but you can setup a policy to send you alerts in case of CLR crash. (It is a default event type that is provided by AppD under server crashes)

Basically, create a new policy and on the right hand side, under server crashes, select CLR crash and then configure the actions to be taken.

irrespective of the severity you can set it up to send out alerts.

Thanks

Gurmit,

0 Karma

Sundarapandian_
Path Finder

Thanks, Gurmit,

Yes, that is something that im aware of. But, user specifically needs this as a status bubble in dashboard to be monitored by the command center team. If there is any workaround, that would be great.

Regards,

Sundar

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
Hi,
Not sure if you can show it as bubble but you can definitely show a events list widget and then filter your events to be displayed by the event type. (may be only select CLR crash here?)

Thanks,
Gurmit.
0 Karma

Sundarapandian_
Path Finder

Hi Gurmit,

Yes, in fact that is what i sugegsted :), but they are looking for bubble with RAG status which is easy for command center to take action

Thanks,

Sundar

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Reprocessing XML into Fixed-Length Events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...