Currently, it is sequentially processed in a loop. The source for it is in the $SPLUNK_HOME/etc/apps/appdynamics/bin/metrics.py and $SPLUNK_HOME/etc/apps/appdynamics/bin/events.py files and you can change it to make it process concurrently on separate threads. Also, the sources for these Python scripts are there on GitHub which you can fork and submit pull requests for: https://github.com/Appdynamics/splunk-alerting-extension-old/blob/master/src/main/splunkApp/appdynamics/bin/metrics.py https://github.com/Appdynamics/splunk-alerting-extension-old/blob/master/src/main/splunkApp/appdynamics/bin/events.py Cheers, Pranta ... View more

Hi srisahitya_v, Cross-launching from Splunk to AppDynamics is only applicable for events and health-rule violations sent from AppDynamics to Splunk via the Splunk alerting extension. Not sure why the following section got deleted from the documentation: Custom Notifications in AppDynamics Use the AppDynamics Controller UI to configure the custom actions notify-splunk-of-event and notify-splunk-of-policy-violation in the Global Notifications and Policy Notifications screens. Details are available in Configure Custom Notifications (login required). Add the following field extraction section to your $SPLUNK_HOME/etc/apps/search/default/props.conf file: [source::http-simple] EXTRACT-AppD = url="http[s]*://(?[^"|]+)" Add the following workflow action to your $SPLUNK_HOME/etc/apps/search/default/workflow_actions.conf file: [LaunchAppD] display_location = both fields = url label = Launch in AppDynamics link.method = get link.target = blank link.uri = http://$!nurl$ type = link Meanwhile, while I investigate the documentation issue, please follow the above instructions which are also available here: https://github.com/Appdynamics/splunk-alerting-extension-old Cheers, Pranta ... View more

It was released last Friday: http://splunk-base.splunk.com/apps/67849/appdynamics ... View more