AppDynamics Events Service is the on-premise data storage facility for unstructured data generated by Application Analytics, Database Visibility, and End User Monitoring (EUM) deployments. To configure EUM to push raw data to Events Service, edit the eum.properties file to reflect the following properties: analytics.enabled=true analytics.serverScheme=http analytics.serverHost=events.service.hostname analytics.port=9080 analytics.accountAccessKey=1a59d1ac-4c35-4df1-9c5d-5fc191003441 Note: EUM will push EUM data to Events Service with or without an explicit analytics license. How to query EUM data with an analytics license  To query the EUM data from Events Service using the analytics API, follow the directions in our analytics API documentation (version 4.3). How to query EUM data with no explicit analytics license  When there is no explicit analytics license, you will need to change the authentication method outlined in the analytics API documentation. For this authentication, use the EUM account name and EUM license key which can be found on the license page by clicking on the gear menu in the upper-right corner of the controller UI, and then clicking on License.   Authenticate with curl One option is to use the following curl syntax for authentication: curl --user "<eum_account_name>:<eum_license_key>"..... Authenticate with base64 encoding Another option is to use the following base64 encoding syntax for authentication: base64accountname=<eum_account_name> base64licensekey=<eum_license_key> base64auth=`echo "$base64accountname:$base64licensekey" | base64 -b 0` echo $base64auth QXBwRHluYW1pY3MteHh4eHg6OWJhOWJkM2IteHh4eAo= curl -H"Authorization: Basic $base64auth".... Types of queries  After choosing the method of authentication, you can make queries to Events Service for the following types of data: Event Type Events Service Table Name Browser Records browser_records Mobile Records mobile_snapshots Mobile Crash Reports mobile_crash_reports Browser Sessions web_session_records Mobile Sessions mobile_session_records   API example With the chosen authentication method and chosen Events Service endpoint, use the following API script to make your query: curl --user "<EUM_Account_Name>:<EuM_License_Key>" -H"Content-type: application/vnd.appd.events+json;v=2" http://<events_service_endpoint>:9080/events/query -d ' select * from browser_records ' or curl -H"Authorization: Basic $base64auth" -H"Content-type: application/vnd.appd.events+json;v=2" http://<events_service_endpoint>:9080/events/query -d ' select * from browser_records ' Note: In some on-premise deployments, the EUM account license key may have changed in a license renewal which can cause authorization to fail. If the on-premise Events Service node(s) have   ad.es.node.http.enabled=true   configured in the events-service-api-store.properties file then the following cURL command can be used to find the correct EUM license key value. Please update the $ES_NODE variable to use the IP address or hostname of an/the Events Service node. Example: $ ES_NODE="192.168.102.171" $ curl -s "http:/${ES_NODE}:9200/appdynamics_accounts_v2/_search" | sed $'s/,/\\\n/g'| grep "eumAccountName" -B 3 | head -2 "accountName":"test-eum-account-XXXXXXXXX-1518596264712" "accessKey":"52218919-ddbb-XXXX-XXXX-edec188e4b73" Additional parameters For additional information, such as start and end parameters, follow the analytics API documentation.   ... View more

Problem  I want to enable/disable synthetic jobs programmatically in order to automate the process during the planned downtimes so that false alerts are not generated. Solution For dealing with synthetic jobs, use the  https://api.eum-appdynamics.com  endpoint to make changes to the schedule, and either enable or disable jobs. To use this API, use your username and password for authentication. The username should be the EUM account name, and the password should be the EUM license key. These can be found on the licensing page in the controller UI by clicking on the gear menu in the upper right corner of the controller UI, clicking on license and then scrolling down to "End User Monitoring" as seen in the screenshot below.  The APIs below can be used to get and modify the schedules:   Get a list of all the synthetic jobs available for the authenticated user: GET https://api.eum-appdynamics.com/v1/synthetic/schedule  Get the exact job identified by the schedule ID. To find the schedule ID and description, use the previous request to get a list of all jobs: GET https://api.eum-appdynamics.com/v1/synthetic/schedule/<schedule_id> Modify the schedule according to the new schedule object provided in the body: PUT https://api.eum-appdynamics.com/v1/synthetic/schedule/<schedule_id>​ Use the response body from the previous request to get the exact job using the schedule ID as the JSON body. The field "userEnabled" controls whether the job is enabled or disabled, and will show the same result as enabling/disabling from the UI. Sample curl implementation Get a particular schedule  Modify the given schedule  Create your own script  Enable a particular job  Disable a particular job  synth.py  Get all schedules curl -XGET --user AppDynamics-a0Q340ABCDEABCDEAV:9ba9bd3b-652d-abcd-abcd-abcdefecd4f0 https://api.eum-appdynamics.com/v1/synthetic/schedule Output: { "_first": null, "_items": [ { "_id": "fcedd1d0-88bc-49c1-9bbe-397227616d1f", "appKey": "AD-AAB-WWW-WWW", "browserCodes": [ "Chrome" ], "captureVisualMetrics": true, "created": "2016-11-02T04:07:22.764Z", ..... Get a particular schedule curl -XGET --user AppDynamics-a0Q340ABCDEABCDEAV:9ba9bd3b-652d-abcd-abcd-abcdefecd4f0 https://api.eum-appdynamics.com/v1/synthetic/schedule/fcedd1d0-88bc-49c1-9bbe-397227616d1f 2>/dev/null|python -m json.tool { "_id": "fcedd1d0-88bc-49c1-9bbe-397227616d1f", ..... "userEnabled": false, "version": 13 } Modify the given schedule curl -XPUT --user AppDynamics-a0Q340ABCDEABCDEAV:9ba9bd3b-652d-abcd-abcd-abcdefecd4f0 -H"Content-Type: application/json" -d '{ "_id": "fcedd1d0-88bc-49c1-9bbe-397227616d1f", ..... "userEnabled": true, "version": 13 }' https://api.eum-appdynamics.com/v1/synthetic/schedule/fcedd1d0-88bc-49c1-9bbe-397227616d1f Create your own script Use the following Python implementation as a starting point to create your own script. osxltmkshi:analytics-agent mayuresh.kshirsagar$ python ~/Desktop/synth.py --help usage: synth.py [-h] -n <eum_account_name> -l <eum_license_name> [-u <eum_url>] -j <synth_job_name> [-e] optional arguments: -h, --help show this help message and exit -n <eum_account_name>, --eumaccountname <eum_account_name> EUM Account Name -l <eum_license_name>, --eumlicensekey <eum_license_name> EUM License Key -u <eum_url>, --url <eum_url> EUM Server URL, Defaults to https://api.eum- appdynamics.com -j <synth_job_name>, --job <synth_job_name> Job Name -e, --enable Enable Job - If present marks the job enabled. If absent, marks the job disabled Enable a particular job python ~/Desktop/synth.py -n AppDynamics-a0Q340ABCDEABCDEAV -l 9ba9bd3b-652d-abcd-abcd-abcdefecd4f0 -j 90220 -e Disable a particular job python ~/Desktop/synth.py -n AppDynamics-a0Q340ABCDEABCDEAV -l 9ba9bd3b-652d-abcd-abcd-abcdefecd4f0 -j 90220 synth.py Click "Learn More" to view the  synth.py file Spoiler (Highlight to read) # -*- coding: utf-8 -*- import requests import argparse import sys import json def find(list, filter): for x in list: if filter(x): return x return None def main(): accountname=None licensekey=None url=None jobname=None enable=False getallschedules="/v1/synthetic/schedule" scheduleendpoint="/v1/synthetic/schedule/" parser = argparse.ArgumentParser() parser.add_argument("-n", "--eumaccountname", help="EUM Account Name", required=True, metavar='<eum_account_name>') parser.add_argument("-l", "--eumlicensekey", help="EUM License Key", required=True, metavar='<eum_license_name>') parser.add_argument("-u", "--url", help="EUM Server URL, Defaults to https://api.eum-appdynamics.com", default="https://api.eum-appdynamics.com", required=False, metavar='<eum_url>') parser.add_argument("-j", "--job", help="Job Name", required=True, metavar='<synth_job_name>') parser.add_argument("-e", "--enable", help="Enable Job - If present marks the job enabled. If absent, marks the job disabled", default=False, action="store_true", required=False) args = parser.parse_args() accountname=args.eumaccountname licensekey=args.eumlicensekey url=args.url jobname=args.job enable=args.enable # Get all the schedules response = requests.get(url + getallschedules,auth=(accountname,licensekey)) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _items= _json['_items'] _return = find(_items, lambda x: x['description'] == jobname) scheduleid=_return['_id'] # Get the individual schedule matching the description response = requests.get(url + scheduleendpoint + scheduleid,auth=(accountname, licensekey)) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _json['userEnabled'] = enable _json=json.dumps(_json, indent=3) print "Request: " + _json headers = {'Content-type': 'application/json'} # Modify the schedule response = requests.put(url + scheduleendpoint + scheduleid, auth=(accountname, licensekey), headers=headers, data=_json) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _json=json.dumps(_json, indent=3) print "Response: " + _json if __name__ == "__main__": main() # -*- coding: utf-8 -*- import requests import argparse import sys import json def find(list, filter): for x in list: if filter(x): return x return None def main(): accountname=None licensekey=None url=None jobname=None enable=False getallschedules="/v1/synthetic/schedule" scheduleendpoint="/v1/synthetic/schedule/" parser = argparse.ArgumentParser() parser.add_argument("-n", "--eumaccountname", help="EUM Account Name", required=True, metavar='<eum_account_name>') parser.add_argument("-l", "--eumlicensekey", help="EUM License Key", required=True, metavar='<eum_license_name>') parser.add_argument("-u", "--url", help="EUM Server URL, Defaults to https://api.eum-appdynamics.com", default="https://api.eum-appdynamics.com", required=False, metavar='<eum_url>') parser.add_argument("-j", "--job", help="Job Name", required=True, metavar='<synth_job_name>') parser.add_argument("-e", "--enable", help="Enable Job - If present marks the job enabled. If absent, marks the job disabled", default=False, action="store_true", required=False) args = parser.parse_args() accountname=args.eumaccountname licensekey=args.eumlicensekey url=args.url jobname=args.job enable=args.enable # Get all the schedules response = requests.get(url + getallschedules,auth=(accountname,licensekey)) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _items= _json['_items'] _return = find(_items, lambda x: x['description'] == jobname) scheduleid=_return['_id'] # Get the individual schedule matching the description response = requests.get(url + scheduleendpoint + scheduleid,auth=(accountname, licensekey)) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _json['userEnabled'] = enable _json=json.dumps(_json, indent=3) print "Request: " + _json headers = {'Content-type': 'application/json'} # Modify the schedule response = requests.put(url + scheduleendpoint + scheduleid, auth=(accountname, licensekey), headers=headers, data=_json) if response.status_code != 200: print "Error Occurred. Status Code: " + str(response.status_code) + " Response: " + json.dumps(json.loads(response.text),indent=3) sys.exit(1) _json = json.loads(response.text) _json=json.dumps(_json, indent=3) print "Response: " + _json if __name__ == "__main__": main() Related Links Create scripts for synthetic jobs Synthetic scripts FAQ ... View more

Overview There might be situations where the IP address that you see in the browser snapshots for incoming requests is not what you expect. This document mentions the precedence of how the IP address is resolved for an incoming request. However, sometimes there may be mis-configurations at the network device level, which may make it hard to debug the issue. Debugging IP address resolution To debug the IP address resolution, add the following logger to the EUM server (<eum_install_dir>/eum-processor/bin/logback.xml) <logger name="com.appdynamics.eumcloud.processor.collector.ABeacon" level="TRACE" additivity="false"> <appender-ref ref="FILE"/> </logger> A log appears like the following: In the EUM log (eum-processor.log file) 06 Nov 2015 02:24:04.978 -0800 Beacon to Record Converter-1 AD.ABeacon TRACE HEADER_AD_X_FORWARDED_FOR: null 06 Nov 2015 02:24:04.984 -0800 Beacon to Record Converter-1 AD.ABeacon TRACE HEADER_X_FORWARDED_FOR: 14.102.224.6 This tells you the exact source of the IP address that is being resolved (HTTP request, X_FORWARDED_FOR header, AD_X_FORWARDED_FOR header, etc). ... View more

You can see that the Job is run periodically and the Last Run and the Next run times are getting Updated. However when you try to see the results for the job you do not see any results available: This usually happens when the Synthetic Job runs, however it is running on some new pages, but doesn't have enough room to register new pages in EUM. Check the page limit (usually 500) to see if the page limit has been reached. In the screenshot below, the page limit is set to 2000, but we see that that limit has been reached, and EUM can no longer register any more new pages: The Page limit is common between Real User as well as Synthetic Monitoring as of 4.2, and the same page limit can also be seen when checked in Real Users->Pages & AJAX Requests: To fix this, you would have to delete the pages that you do not care about, or pages those were registered as part of name rule testing. A suggested way of getting rid of such pages is to look for pages without load for the past month and selecting the pages that do not have load for the gone month and deleting them. Once some pages are deleted and room is created for more pages to register, the new pages detected with the synthetic jobs should be registered and metrics should be collected for them. It is also recommended to revisit the naming rules as described here to further refine the page identification and naming so that similar pages are grouped into a single name to reduce the Page Name limit consumption. ... View more

Loading Transaction Analytics Flow map throws "Server Encountered an internal error" message Affects Controller version 4.2 Problem An application Agent pushes Transaction Analytics data to the Events Service. Though the user is able to see Transaction Analytics data in Analytics, when they double-click a Transaction Analytics record, an error pops-up: The server encountered an internal error () that prevented it from fulfilling this request Diagnosis This error indicates that, though the user trying to access the Analytics record has Analytics permissions, they don't have permissions on the application to which this record belongs. To load the  BT flow map, a user requires read permissions to that application.  Solution Provide the user with a role that includes Read access to the application. Once this permission is granted, the user should be able to see that BT flow map when loading the Transaction Analytics record: ... View more