What are the steps to enabling debug logging for an on-premises EUM Server? What are the steps for an EUM Processor? In your computer terminal, navigate to  <EUM_HOME>/eum-processor/bin and locate the logback .xml file. Open the file and change the logging level from INFO to DEBUG for the logger that you are interested in troubleshooting. Example:  Save and restart the EUM Server. Example of typical debug logging ... View more

From Events Service v23.2 onward, port 9200 is always open, as a requirement for Elastic Search 8.  In prior versions, port 9200 is disabled by default. Used for debugging purposes,it needs to be turned on before troubleshooting begins.  NOTE | After the debugging session is done, remember to disable the property and restart the Events Service to avoid exposure to security vulnerabilities In this article Troubleshooting Example |  Port 9200 in Events Service 23.2 and beyond  | How to enable Port 9200 in prior versions   Troubleshooting example: finding shard or index status  Using the following commands to find the status of shards/indices: curl http://localhost:9200/_cat/shards?v curl http://localhost:9200/_cat/indices?v  will result in the following output: curl: (7) Failed to connect to localhost port 9200: Connection refused Back to Top   Port 9200 in Events Service 23.2 and beyond  As of Events Service 23.2, there is no ad.es.node.http.enabled property in <ES_HOME>/conf/events-service-api-store. Elasticsearch 8 requires that port 9200 is always open.  For the time being, we recommend one of the following options:  Deploy Events Service 23.2.0 behind a load balancer and restrict access to port 9200 from the outside world  Make firewall rules to restrict access to port 9200 only to the Elastic Search node's IP.  Back to Top   How do I  enable port 9200 for Events Service prior to v23.2? ?  Locate the events-service-api-store.properties file within the conf directory of your Events-Service home directory ( <ES_HOME>/conf/events-service-api-store.properties ). Change the value of the property ad.es.node.http.enabled  to true. Save, and restart the Events Service server. # To run this service in a fully, self contained mode, without # the need for dedicated master nodes, this should be set to 'true'. # If there are dedicated elasticsearch masters, then this flag # should be set to 'false'. ad.es.node.master=true ad.es.node.http.enabled=true Begin your debugging session. Leaving the property enabled will expose security vulnerabilities. So, be sure to disable the  ad.es.node.http.enabled  property and restart the Events Service once you complete the debugging session. Back to Top ... View more

If your Mobile Agent version is 4.5, 4.4 & 4.3, you need to use the  loggingLevel  method to enable and set the different logging levels in your instrumentation code. For instance: // appKey should be assigned your EUM app key ADEumAgentConfiguration *config = [[ADEumAgentConfiguration alloc] initWithAppKey:@ "AD-AAB-AAK-VMJ"]; config.loggingLevel = ADEumLoggingLevelAll; [ADEumInstrumentation initWithConfiguration:config];   Screenshot: 4.5,4.4 & 4.3  If your Mobile Agent version is 4.2 & below, you need to use the  enableLogging boolean property to enable it. [ADEumInstrumentation initWithKey:@"<App Key>" collectorUrl:@“<Collector URL>" enableLogging:<Boolean>]; [ADEumInstrumentation initWithKey: @"EUM-AAB-AAD" collectorUrl: @"http://localhost:7001" enableLogging: YES]; Note: AppDynamics logs are prepended with tag x/AppDynamics , where x = the first letter of the log level. i/AppDynamics indicates INFO level logging and D/AppDynamics indicates DEBUG level logging. Once you have enabled the above DEBUG logging and re-build and run your app in a simulator using Xcode, you will see your debug logs in the console/terminal window in the debug area of the Xcode. Typical  IOS Agent DEBUG logging:  2018-07-31 19:24:52.988848+0530 rayan-test[65046:12836369] I/AppDynamics: Agent release version DEVBUILD 2018-07-31 19:24:52:987 rayan-test[65046:303] I/AppDynamics: Agent release version DEVBUILD 2018-07-31 19:24:53.000508+0530 rayan-test[65046:12836375] I/AppDynamics: Agent will use Application Key: AD-AAB-AAK-VMJ 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent will use Application Key: AD-AAB-AAK-VMJ 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent will use Collector URL: https://mobile.eum-appdynamics.com 2018-07-31 19:24:53.001126+0530 rayan-test[65046:12836369] I/AppDynamics: Agent will use Collector URL: https://mobile.eum-appdynamics.com 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent has enabled the Screenshot System 2018-07-31 19:24:53.001621+0530 rayan-test[65046:12836369] I/AppDynamics: Agent has enabled the Screenshot System 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent will use Screenshot URL: https://image.eum-appdynamics.com 2018-07-31 19:24:53.002102+0530 rayan-test[65046:12836369] I/AppDynamics: Agent will use Screenshot URL: https://image.eum-appdynamics.com 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent has enabled JS Agent Instrumentation 2018-07-31 19:24:53.002562+0530 rayan-test[65046:12836369] I/AppDynamics: Agent has enabled JS Agent Instrumentation 2018-07-31 19:24:53:000 rayan-test[65046:303] I/AppDynamics: Agent has not enabled JS Agent Ajax Instrumentation 2018-07-31 19:24:53.003029+0530 rayan-test[65046:12836369] I/AppDynamics: Agent has not enabled JS Agent Ajax Instrumentation 2018-07-31 19:24:53.004019+0530 rayan-test[65046:12836104] Could not successfully update network info during initialization. 2018-07-31 19:24:53:007 rayan-test[65046:303] D/AppDynamics: Agent using executable UUID: bef3fdcb458d3333a3717cf96be9b7c1 2018-07-31 19:24:53.007749+0530 rayan-test[65046:12836369] D/AppDynamics: Agent using executable UUID: bef3fdcb458d3333a3717cf96be9b7c1 2018-07-31 19:24:53:008 rayan-test[65046:303] D/AppDynamics: Agent using executable UUID: bef3fdcb458d3333a3717cf96be9b7c1 2018-07-31 19:24:53.008403+0530 rayan-test[65046:12836369] D/AppDynamics: Agent using executable UUID: bef3fdcb458d3333a3717cf96be9b7c1 2018-07-31 19:24:53.091846+0530 rayan-test[65046:12836375] D/AppDynamics: Crash reporting enabled 2018-07-31 19:24:53:091 rayan-test[65046:303] D/AppDynamics: Crash reporting enabled 2018-07-31 19:24:53:092 rayan-test[65046:303] I/AppDynamics: Master ANR Timer set to 1.000000 2018-07-31 19:24:53.092656+0530 rayan-test[65046:12836369] I/AppDynamics: Master ANR Timer set to 1.000000 2018-07-31 19:24:53:092 rayan-test[65046:303] I/AppDynamics: UI ANR Timer set to 0.900000 2018-07-31 19:24:53.093138+0530 rayan-test[65046:12836369] I/AppDynamics: UI ANR Timer set to 0.900000 2018-07-31 19:24:53:093 rayan-test[65046:d03] D/AppDynamics: Flush postponed due to SQL Data Protection lock. 2018-07-31 19:24:53.094162+0530 rayan-test[65046:12836369] D/AppDynamics: Flush postponed due to SQL Data Protection lock. 2018-07-31 19:24:53:192 rayan-test[65046:303] V/AppDynamics: onApplicationDidBecomeActive 2018-07-31 19:24:53.192499+0530 rayan-test[65046:12836367] V/AppDynamics: onApplicationDidBecomeActive 2018-07-31 19:24:53:192 rayan-test[65046:310f] D/AppDynamics: Loading default beacons from persistence 2018-07-31 19:24:53.192950+0530 rayan-test[65046:12836367] D/AppDynamics: Loading default beacons from persistence 2018-07-31 19:24:53:198 rayan-test[65046:310f] D/AppDynamics: Total number of beacons loaded: 0 2018-07-31 19:24:53.198349+0530 rayan-test[65046:12836367] D/AppDynamics: Total number of beacons loaded: 0 2018-07-31 19:24:53:198 rayan-test[65046:310f] D/AppDynamics: Loading crash beacons from persistence 2018-07-31 19:24:53.198849+0530 rayan-test[65046:12836367] D/AppDynamics: Loading crash beacons from persistence 2018-07-31 19:24:53:202 rayan-test[65046:310f] D/AppDynamics: Total number of beacons loaded: 0 2018-07-31 19:24:53.203174+0530 rayan-test[65046:12836367] D/AppDynamics: Total number of beacons loaded: 0 2018-07-31 19:24:53:202 rayan-test[65046:310f] D/AppDynamics: We need to send #3 beacons to collector 2018-07-31 19:24:53.203639+0530 rayan-test[65046:12836367] D/AppDynamics: We need to send #3 beacons to collector 2018-07-31 19:24:53:203 rayan-test[65046:310f] D/AppDynamics: Adding ADRUM headers to request. 2018-07-31 19:24:53.204140+0530 rayan-test[65046:12836367] D/AppDynamics: Adding ADRUM headers to request. 2018-07-31 19:24:53:204 rayan-test[65046:310f] D/AppDynamics: Agent sending message to collector (eumcollector/mobileMetrics?version=2 -- https://mobile.eum-appdynamics.com) [AD-AAB-AAK-VMJ] 2018-07-31 19:24:53.204584+0530 rayan-test[65046:12836367] D/AppDynamics: Agent sending message to collector (eumcollector/mobileMetrics?version=2 -- https://mobile.eum-appdynamics.com) [AD-AAB-AAK-VMJ] 2018-07-31 19:24:53:204 rayan-test[65046:310f] D/AppDynamics: [{ "et" : 1533045293093, "eut" : 582833854, "st" : 1533045293093, "cf" : "-1794", "ct" : "wifi", "osv" : "11.4", "dmo" : "x86_64", "mv" : "1", "type" : "system-event", "event" : "Agent Init", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "sut" : 582833854, "agv" : "DEVBUILD", "ds" : "476902", "av" : "1.0" },{ "viewControllerName" : "ViewController", "viewControllerUuid" : "b62392e0-4f33-4025-9be9-4bbee10fe387", "cf" : "-1794", "osv" : "11.4", "ec" : 242, "dmo" : "x86_64", "mv" : "1", "type" : "ui", "ct" : "wifi", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "event" : "View Controller Start", "st" : 1533045293187, "sut" : 582833949, "agv" : "DEVBUILD", "ds" : "476902", "av" : "1.0" },{ "et" : 1533045293192, "eut" : 582833953, "st" : 1533045293093, "cf" : "-1794", "osv" : "11.4", "ec" : 243, "dmo" : "x86_64", "mv" : "1", "type" : "ui", "ct" : "wifi", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "event" : "App Start", "rootView" : "ViewController", "sut" : 582833854, "agv" : "DEVBUILD", "ds" : "476902", "av" : "1.0" }] 2018-07-31 19:24:53.205070+0530 rayan-test[65046:12836367] D/AppDynamics: [{ "et" : 1533045293093, "eut" : 582833854, "st" : 1533045293093, "cf" : "-1794", "ct" : "wifi", "osv" : "11.4", "dmo" : "x86_64", "mv" : "1", "type" : "system-event", "event" : "Agent Init", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "sut" : 582833854, "agv" : "DEVBUILD", "ds" : "476902", "av" : "1.0" },{ "viewControllerName" : "ViewController", "viewControllerUuid" : "b62392e0-4f33-4025-9be9-4bbee10fe387", "cf" : "-1794", "osv" : "11.4", "ec" : 242, "dmo" : "x86_64", "mv" : "1", "type" : "ui", "ct" : "wifi", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "event" : "View Controller Start", "st" : 1533045293187, "sut" : 582833949, "agv" : "DEVBUILD", "ds" : "476902", "av" : "1.0" },{ "et" : 1533045293192, "eut" : 582833953, "st" : 1533045293093, "cf" : "-1794", "osv" : "11.4", "ec" : 243, "dmo" : "x86_64", "mv" : "1", "type" : "ui", "ct" : "wifi", "tm" : "2048", "cc" : "8", "ab" : "DEVBUILD", "e 2018-07-31 19:24:53:204 rayan-test[65046:310f] D/AppDynamics: ----------------------------------- 2018-07-31 19:24:53.210121+0530 rayan-test[65046:12836367] D/AppDynamics: ----------------------------------- 2018-07-31 19:24:54:467 rayan-test[65046:310f] D/AppDynamics: Agent received response code: 200 2018-07-31 19:24:54.468413+0530 rayan-test[65046:12836367] D/AppDynamics: Agent received response code: 200 2018-07-31 19:25:15.329407+0530 rayan-test[65046:12836375] D/AppDynamics: We need to send #1 beacons to collector 2018-07-31 19:25:15:296 rayan-test[65046:a00b] D/AppDynamics: Adding ADRUM headers to request. 2018-07-31 19:25:15.329962+0530 rayan-test[65046:12836375] D/AppDynamics: Adding ADRUM headers to request. 2018-07-31 19:25:15:297 rayan-test[65046:a00b] D/AppDynamics: Agent sending message to collector (eumcollector/mobileMetrics?version=2 -- https://mobile.eum-appdynamics.com) [AD-AAB-AAK-VMJ] 2018-07-31 19:25:15.330499+0530 rayan-test[65046:12836375] D/AppDynamics: Agent sending message to collector (eumcollector/mobileMetrics?version=2 -- https://mobile.eum-appdynamics.com) [AD-AAB-AAK-VMJ] 2018-07-31 19:25:15:297 rayan-test[65046:a00b] D/AppDynamics: [{ "sut" : 582855921, "av" : "1.0", "ec" : 244, "see" : false, "mv" : "1", "et" : 1533045315234, "dmo" : "x86_64", "url" : "http:\/\/localhost:8080\/output.json", "eut" : 582855995, "pcl" : 2829, "osv" : "11.4", "cc" : "8", "tm" : "2048", "is" : "AppDynamics.NSURLSession", "ct" : "wifi", "type" : "network-request", "agv" : "DEVBUILD", "ab" : "DEVBUILD", "ds" : "476902", "cf" : "-1794", "bkgd" : false, "hrc" : 200, "st" : 1533045315160, "crg" : "2b18b43d-b3d7-49e1-bd2e-7b1e6b46a3f3" }] 2018-07-31 19:25:15.331062+0530 rayan-test[65046:12836375] D/AppDynamics: [{ "sut" : 582855921, "av" : "1.0", "ec" : 244, "see" : false, "mv" : "1", "et" : 1533045315234, "dmo" : "x86_64", "url" : "http:\/\/localhost:8080\/output.json", "eut" : 582855995, "pcl" : 2829, "osv" : "11.4", "cc" : "8", "tm" : "2048", "is" : "AppDynamics.NSURLSession", "ct" : "wifi", "type" : "network-request", "agv" : "DEVBUILD", "ab" : "DEVBUILD", "ds" : "476902", "cf" : "-1794", "bkgd" : false, "hrc" : 200, "st" : 1533045315160, "crg" : "2b18b43d-b3d7-49e1-bd2e-7b1e6b46a3f3" }] 2018-07-31 19:25:15:297 rayan-test[65046:a00b] D/AppDynamics: ----------------------------------- 2018-07-31 19:25:15.331955+0530 rayan-test[65046:12836375] D/AppDynamics: ----------------------------------- 2018-07-31 19:25:15:540 rayan-test[65046:a00b] D/AppDynamics: Agent received response code: 200 2018-07-31 19:25:15.540791+0530 rayan-test[65046:12836823] D/AppDynamics: Agent received response code: 200 Screenshot:  Console log Console debug logs You can export the contents of the debug logs by either selecting and copying them to a file or exporting them to a file directly using the option below: 1. Click on Window > Devices from the Xcode menu. 2. Under Devices section in the left column, choose your device. 3. To view the console logs, select View Device Logs button under the Device Information section on the right-hand panel. 4. To view the device console, click the up-triangle at the bottom left of the right-hand panel to show the device console. To save the console as a file, click the down arrow on the bottom right. ... View more

To enable EUM Client side debug logs dynamically, you can use the Glassfish admin console or use the asamin utility. 1. Access the Glassfish admin console following the steps outlined here: AccesstheGlassfishAdminConsole 2. Once logged in, navigate to the  server config  in the console. Select Logger Settings, then Log Levels and add the logger below as shown in the screenshot and save it. Please note that these logging will be very verbose, hence it's normally enabled for few minutes during troubleshooting to capture the debug information in order to find out the root cause of the issue.     com.appdynamics.eum.client.EUMClient=FINEST com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean=FINEST    EUM CLient logger If you can't access the Glassfish console for some reason, you can log in to the Controller machine and navigate to the pathbelow and enable it via the asadmin utility. For example; cd /AppDynamics/Controller/appserver/glassfish/bin ./asadmin set-log-levels Enter admin user name> admin Enter admin password for user "admin"> Enter the value for the name_value operand> com.appdynamics.eum.client.EUMClient=FINEST: com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean=FINEST com.appdynamics.eum.client.EUMClient package set with log level FINEST. com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean package set with log level FINEST. These logging levels are set for server. Command set-log-levels executed successfully. To disable it after you have captured the required debug info: ./asadmin set-log-levels Enter admin user name> admin Enter admin password for user "admin"> Enter the value for the name_value operand> com.appdynamics.eum.client.EUMClient=INFO: com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean=INFO com.appdynamics.eum.client.EUMClient package set with log level INFO. com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean package set with log level INFO. These logging levels are set for server. Command set-log-levels executed successfully. The command above sets multiple loggers and notice the colon(:) above to set multiple loggers. If you would like to set any one of them, you can use the command below. ./asadmin set-log-levels Enter admin user name> admin Enter admin password for user "admin"> Enter the value for the name_value operand> com.appdynamics.eum.client.EUMClient=FINEST com.appdynamics.eum.client.EUMClient package set with log level FINEST. These logging levels are set for server. Command set-log-levels executed successfully. or ./asadmin set-log-levels Enter admin user name> admin Enter admin password for user "admin"> Enter the value for the name_value operand> com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean=FINEST com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean package set with log level FINEST. These logging levels are set for server. Command set-log-levels executed successfully. Once the loggers are enabled, the sample FINEST message will look like this: [#|2018-07-19T16:13:59.963+0530|FINER|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=179;_ThreadName=Thread-5;ClassName=com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean;MethodName=uploadAppConfiguration;|Skipped. No reason to update configuration at this time for appId=25|#] [#|2018-07-19T16:14:00.154+0530|FINE|glassfish3.1.2|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=165;_ThreadName=Thread-5;ClassName=com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean;MethodName=registration;|EUM registration done|#] [#|2018-07-19T16:04:57.068+0530|FINEST|glassfish3.1.2|com.appdynamics.eum.client.EUMClient|_ThreadID=1406;_ThreadName=Thread-5;ClassName=com.appdynamics.eum.client.EUMClient;MethodName=fetchEvents;|fetchEvents invoked|#] [#|2018-07-19T16:04:57.068+0530|FINEST|glassfish3.1.2|com.appdynamics.eum.client.EUMClient|_ThreadID=1405;_ThreadName=Thread-5;ClassName=com.appdynamics.eum.client.EUMClient;MethodName=fetchEvents;|fetchEvents invoked|#] Examples:  asadmin asadmin multiple logger ... View more

If the End User Monitoring (EUM) data/license does not appear in the Controller UI and the logs of the Controller (server.log) contains the message below, this is normally caused by an EUM license key mismatch between the  property_eum-license-key value in license.lic and the license-key value in the accounts table of the eum_db schema. server.log: Unable to fetch/update information for EUM account with name: <EUM ACCOUNT NAME>com.appdynamics.eum.rest.client.exception.UserErrorClientException: ApiError: requestId=null httpStatus=401 apiErrorCode=UNAUTHORIZED userMessage='Credentials required for this resource' additionalInfo=[null]|#] [#|2018-07-18T01:14:26.702+0300|WARNING|glassfish 4.1|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=318;_ThreadName=__ejb-thread-pool15;_TimeMillis=1531865666702;_LevelValue=900;|Failed to provision EUM Cloud License with cloud for eum account [EUM ACCOUNT NAME] com.appdynamics.eum.rest.client.exception.UserErrorClientException: ApiError: requestId=null httpStatus=401 apiErrorCode=UNAUTHORIZED userMessage='Credentials required for this resource' additionalInfo=[null]|#] [#|2018-07-18T01:14:26.702+0300|WARNING|glassfish 4.1|com.singularity.ee.controller.beans.eumcloud.EUMCloudManagerBean|_ThreadID=313;_ThreadName=__ejb-thread-pool10;_TimeMillis=1531865666702;_LevelValue=900;|Failed to get EUM event service key com.appdynamics.eum.rest.client.exception.UserErrorClientException: ApiError: requestId=null httpStatus=401 apiErrorCode=UNAUTHORIZED userMessage='Credentials required for this resource' additionalInfo=[null]|#] How to validate if it's an EUM license key mismatch issue You can use the aggreagator servlet endpoint using the EUM license key to validate if the license is valid or not. If it's SAAS EUM, you can query the end-point below using your current EUM license key and if it returns as true, it's not a license issue. If it returns as false, it's an EUM license key issue. https://agg.eum-appdynamics.com/eumaggregator/validate-lic?eumLicenseKey=<Paste your eum license key>   If it's on-prem EUM, you can use the end-point below: http://<EUM_HOSTNAME:7001/eumaggregator/validate-lic?eumLicenseKey=<Paste your eum license key> For on-premise EUM only: Assuming it has returned false, you need to query your eum_db.accounts table to check what EUM key it is using. If the EUM Server is 4.4+, you can log in to the eum_db using the option below on the EUM host itself. If it's a lesser version, log in from the Controller host using the command below: <Controller_Home>/bin/controller.sh login-db option 1. For instance, navigate to  cd /AppDynamics/EUM450_23508/mysql/bin 2. Please replace welcome1 with your correct password while running the login command below: ./mysql -h 127.0.0.1 -P 3388 -u root -pwelcome1 --protocol=tcp 3. Once logged into the DB, you can issue the following queries to find out the license key[license-key=] Use eum_db; Select * from accounts \G;   Once you have determined that the license-key in the accounts table and the  property_eum-license-key in the license.lic file are different, please reach out to Licensing/OrderOps to get the  license re-issued with the correct EUM account name and key. If you would like to delete the existing records in the accounts table and use the new EUM account and key, delete the records in the accounts and the account_credentials table and provision the new license file using the  provision-license command. Please note that this will change your EUM app key in the applications table since the app key generation is based on the EUM account name and EUM license key value, so you need to change the app key accordingly in your application. 1. Login to the eum_db 2. Delete from accounts \G; 3. Delete from account_credentials \G; 4. Copy the new license.lic file to the eum host and execute the command below. From the eum-processor directory, run the following script: On Linux: ./bin/provision-license <path_to_license_file> On Windows: bin\provision-license.bat <path_to_license_file> 5. Once this is done, query the accounts table and verify if you are able to see the correct eum account name and key. select * from accounts\G; ... View more

If you would like to instrument the Private Synthetic Agent for internal monitoring purposes, you can achieve it by using the steps below.  1. Locate the Synthetic-driver.bat file under the Private Synth Agent install folder and add the javagent.jar to the  DEFAULT_JVM_OPTS  as shown in the screenshot below 2. Save and restart the PSA, then verify if it registered successfully by looking for [Started Java Agent Successfully] in the console log. Agent Registration Successful PSANODE ... View more

Users can retrieve the EUM Browser page views, EUM Mobile usage, and Synth usage by utilizing the licensing API. curl -X GET -H "Content-Type: application/vnd.appd.eum.license.terms+json;v=2.0" --user "<EUM_Account_Name>:<EUM_License_Key>" "<EUM_URL_BASE>/v2/account/<EUM_Account_Name>/license" On-Premise example: curl -X GET -H "Content-Type: application/vnd.appd.eum.license.terms+json;v=2.0" --user "AppDynamics-a0Q3400000Dg:xyzxyzxyzxyzxyzxyz" "https://eum:7002/v2/account/AppDynamics-a0Q3400000Dg/license" Returns a usage output similar to the following: { "state": { "allocatedMobileAgents": 50000, "allocatedSyntheticTime": 80000000, "consumedMobileAgents": 1, "consumedSyntheticTime": 2604680, "mobileCurrentUsagePeriodEndMillis": 1512158400000, "mobileCurrentUsagePeriodStartMillis": 1509562800000, "syntheticCurrentUsagePeriodEndMillis": 1512158400000, "syntheticCurrentUsagePeriodStartMillis": 1509559200000, "syntheticPrivateAgentUnitsAllocated": 200, "syntheticPrivateAgentUnitsUtilized": 1, "webAllocatedPageViews": 400000000, "webConsumedPageViews": 60174, "webCurrentUsagePeriodEndMillis": 1515182400000, "webCurrentUsagePeriodStartMillis": 1483646400000 }, "terms": { "expirationDate": 1515139200000, "iotLicenseType": "IOT_NONE", "mobileAnalyticsLicenseType": "PRO", "mobileAnalyticsRetentionDays": 8, "mobileLicenseAllowsOverages": false, "mobileLicenseType": "MOBILE_PRO", "mobileLicenseUnits": 10, "mobileTrialExpirationDate": 1515139200000, "synthSchedulingEnabled": true, "syntheticLicenseType": "PRO", "syntheticLicenseUnits": 400, "syntheticPrivateAgentLicenseType": "PA_PRO", "syntheticPrivateAgentLicenseUnits": 200, "syntheticTrialExpirationDate": 1515139200000, "webAnalyticsLicenseType": "PRO", "webAnalyticsRetentionDays": 8, "webLicenseAllowsOverages": false, "webLicenseType": "EUM_PRO", "webLicenseUnits": 40, "webTrialExpirationDate": 1515139200000 } } SaaS example:  curl -X GET -H "Content-Type: application/vnd.appd.eum.license.terms+json;v=2.0" --user "EUM_ACCOUNTNAME:EUM_Licensekey" "https://api.eum-appdynamics.com/v2/account/EUM_ACCOUNTNAME/license" The synth license value displayed in the Controller UI is in terms of STB(Synthetic Time Blocks). Synth Licensing is based on units known as Synthetic Time Blocks (STBs), which are five-second chunks of time. One unit of Synthetic Pro gives you 40,000 STBs per month. For more information: Browser Synthetic Licenses The License API in the above output displays the result in terms of seconds, so the user needs to divide by 5 to get the results in STB. Modify start and end time in the above API: If a user needs to check the usage period for past 1 hour or between a specific time ranges, use the timeRange query parameters. 1-hour example: https://api.eum-appdynamics.com/v2/account/EUM_ACCOUNT_NAME/license?timeRange=last_1_hour.BEFORE_NOW.-1.-1.60 Custom time range example: Between 3 PM IST to 5 PM IST https://api.eum-appdynamics.com/v2/account/EUM_ACCOUNT_NAME/license?timeRange=Custom_Time_Range.BETWEEN_TIMES.1516015800918.1516008600918.120 Note: 1516015800918 is in Epoch time.  ... View more

What are the steps to enable EUM debug logging for the .NET Agent? Go to the installation directory and edit the AppDynamicsAgentLog.config as follows. Under the <targets> section add: <target name="eumlog" xsi:type="File" archiveAboveSize="5000000" maxArchiveFiles="5" createDirs="True" fileName="C:\ProgramData\AppDynamics\DotNetAgent\Logs\eumlog.txt" layout="${longdate} ${processid} ${processname} ${threadid} ${level} ${logger:shortName=True} ${message}" />​ Under the <rules> section add: <logger name="com.singularity.ee.agent.appagent.services.transactionmonitor.eum.*" minLevel="Trace" writeTo="eumlog" final="true" />​ <logger name="com.appdynamics.eum.*" minLevel="Trace" writeTo="eumlog" final="true" /> Save the file. You don't have to restart the agent as it's dynamic. You will see the log file being generated as shown in the below screenshot.  log config EUM log ... View more