Discussion Feed

Hello, Steven. Normally customers use an event management system, for this reason, otherwise, your ticket may get extremely cluttered or you will end up with a lot of duplicate tickets. We do not have an integration which does what you are asking, but if you look at how we integrate with ServiceNow Event Management you can likely derive a new HTTP Action template from the concept using the table API.    #set($controllerName="demo1.appdynamics.com") { "records":[ #foreach(${event} in ${fullEventList}) #foreach(${entity} in ${event.affectedEntities}) #if($foreach.index > 0) , #end { "source": "AppDynamics" ,"event_class": "$controllerName" ,"x_apd_appdynamics_event_source_url": "$event.deepLink" #if( $entity.entityTypeDisplayName == "Node" ) ,"node": "$entity.name" , "resource": "$entity.name" , "ci_type": "x_apd_appdynamics_node" ,"ci_identifier" :{ "name":"$entity.name", "tier_name":"$event.tier.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif( $entity.entityTypeDisplayName == "Tier" ) ,"node": "$entity.name" , "resource": "$entity.name" , "ci_type": "x_apd_appdynamics_tier" ,"ci_identifier" :{ "name":"$entity.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif( $entity.entityTypeDisplayName == "Application" ) ,"node": "$entity.name" , "resource": "$entity.name" , "ci_type": "x_apd_appdynamics_application" ,"ci_identifier" :{ "name":"$event.application.name", "controller_name": "$controllerName" } #elseif( $entity.entityTypeDisplayName == "Business Transaction" ) , "ci_type": "x_apd_appdynamics_tier" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$event.tier.name" ,"ci_identifier" :{ "name":"$event.tier.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif( $entity.entityTypeDisplayName == "Service Endpoint" ) , "ci_type": "x_apd_appdynamics_tier" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$event.tier.name" ,"ci_identifier" :{ "name":"$event.tier.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif( $entity.entityTypeDisplayName == "Backend" ) , "ci_type": "x_apd_appdynamics_remote_service" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$entity.name" ,"ci_identifier" :{ "name":"$entity.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #else #if($event.node) , "ci_type": "x_apd_appdynamics_node" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$event.node.name" ,"ci_identifier" :{ "name":"$event.node.name", "tier_name":"$event.tier.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif($event.tier) , "ci_type": "x_apd_appdynamics_tier" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$event.tier.name" ,"ci_identifier" :{ "name":"$event.tier.name", "application_name":"$event.application.name", "controller_name": "$controllerName" } #elseif($event.application) , "ci_type": "x_apd_appdynamics_application" , "resource": "$entity.entityTypeDisplayName - $entity.name" ,"node": "$event.application.name" ,"ci_identifier" :{ "name":"$event.application.name", "controller_name": "$controllerName" } #else , "node": "$entity.name" , "resource": "$entity.entityTypeDisplayName - $entity.name" #end #end #if($event.healthRule) ,"metric_name" : "$event.healthRule.name" #set( $msg=$event.healthRule.name) #else #set( $msg="") #end #set( $msg=$msg + ". " + ${event.eventMessage}) #set( $msg = $msg.replace("<b>", "") ) #set( $msg = $msg.replace("</b>", "") ) #set( $msg = $msg.replace("<br>", "") ) ,"description" : "$msg" #if($event.eventType == "POLICY_OPEN_WARNING" || $event.eventType == "POLICY_CONTINUES_WARNING" || $event.eventType == "POLICY_DOWNGRADED") ,"severity": "2" #elseif($event.eventType == "POLICY_OPEN_CRITICAL" || $event.eventType == "POLICY_CONTINUES_CRITICAL" || $event.eventType == "POLICY_UPGRADED") ,"severity": "1" #elseif($event.eventType == "POLICY_CLOSE_WARNING" || $event.eventType == "POLICY_CLOSE_CRITICAL" || $event.eventType == "POLICY_CANCELED_WARNING" || $event.eventType == "POLICY_CANCELED_CRITICAL") ,"severity": "0" #end } #end #end ] } ... View more

That is correct, I am updating the docs to be more clear. Please follow https://www.appdynamics.com/community/exchange/appdynamics-servicenow-cmdb-integration/ section 4.2 otherwise, it's quite close to being accurate. Just use the downloaded file (velocity template) for the content of the HTTP Request Template. Feel free to open a support case if you'd like help. We will get the docs fixed as soon as possible.  ... View more

Hello, @Dominic.Behnood there is no Python script, so I'm not quite sure what you are doing exactly. When you install the sync tool (which is what synchronizes the AppD topology info into ServiceNow (which is what makes Event Correlation automatically work) there is a simple web UI. In that UI you configure the AppD controllers and ServiceNow Instances. There is a tab which looks like this  which allows you to download the template. We will get this corrected in the docs shortly.    ... View more

Hello, Kevin. The Xandra product uses synthetic transactions to verify that things "should" work when a user tries to execute a transaction (similar to AppDynamics Synthetics on web applications). The issue is that when things don't work, why are they failing? AppDynamics for SAP does transaction tracing from end to end, and we do deep monitoring of the SAP components in both Java and ABAP to help identify the root cause of the issues. This means we look at every transaction from web, mobile, and SAPGUI.  ... View more

AppDynamics for SAP is focused on ABAP. AppDynamics Java agent supports other SAP technologies. Many SAP systems use Java and ABAP together, so we combine both technologies often. Depending on the version of Crystal you are using it could be legacy VB based technology (which we do not support), or the newer technology which is built on .NET in which case our .NET agent could be used.  ... View more

Hello, Adrian. We actually do have an agent for IIB on Linux, but if you are running another platform we do not have an agent. There are two things you can do with AppD, one is to configure IIB to allow the messages to pass through with our headers and we will correlate. We also have an IIB extension (https://www.appdynamics.com/community/exchange/extension/ibm-websphere-message-broker-monitoring-extension/) which uses APIs to collect the metrics from IIB and bring them into AppD. You can do things such as monitoring queue lengths and such, which are more operationally useful than logs.    Unfortunately, there is no way to import data from Splunk into AppDynamics, we only send data the other way. AppDynamics also has log analytics capabilities where you can ingest the logs into AppD as well, but logs don't provide a lot of value for monitoring, they are much more useful for debugging purposes.    Splunk has built an app to bring data in from AppDynamics, that should work fine using standard APIs. You can find it in Splunk Base.  ... View more

Yes, we support HEC, but each customer implementation with HEC is variable. The variables include what they are hosting for you, your level of access, and the contract terms. Most of the contract terms depend on your deal, implementation, and SLAs with SAP for the hosting.  ... View more

We now support additional subsystems with this including IMS, VSAM, and outgoing WebSphere.   ... View more

  Hello, Tom. You can find the full documentation here: https://www.ibm.com/support/knowledgecenter/en/SSYHZ9_5.5.0/com.ibm.omegamon_apm.doc/overview/zapm_overview.htm to answer your question we don't really have any requirements for that system since it's not a system doing a lot of work. It can be installed on any Intel Linux system really. We had some preliminary hardware requirements, but during load testing, we found it needed far fewer resources. I will check with the product team just to verify this.  ... View more