Is there a way to configure the Synthetic Private Agent to use the domain Admin User instead of the agent_user? If you want to run the Synthetic Private Agent jobs using the chosen domain admin user account instead of the installer created agent_user , try this workaround.  Note: This solution is not officially documented or supported at this time and therefore may not work in every environment. Table of Contents Configuring Synthetic Private Agent to use the domain Admin User  Does your scheduled task use the correct Admin user?  Configuring Synthetic Private Agent to use the domain Admin User This configuration workaround to using the default agent_user to run the Synthetic Private Agent jobs is to modify the Synthetic Private Agent's configurations so they use chosen domain admin user account user (ex: DOMAIN\appdadmin ) instead.  To achieve this you will need to do the following: Login to the Synthetic Private Agent host as DOMAIN\appdadmin . Validate that all Private agent processes are fully stopped, and kill any java.exe processes even if they don't belong to the agent_user. Clear out the logs directory into a temp folder so that the current logs directory is empty. Also, take a backup of the synthetic-driver.yml file before making any changes. C:\appdynamics\synthetic-agent\synthetic-driver\conf\synthetic-driver.yml Edit the synthetic-driver.yml to remove any lines that reference the agent_user. Specifically, update the following two sets of commands. Remove  agent_user Appdynamics123 ​ from the line starting with -Command​ Change this: webdriverServerCommand: name: WebDriver Server exe: powershell.exe args: > -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123 .\synthetic-driver\scripts\windows\start-webdriver-server.bat To this: webdriverServerCommand: name: WebDriver Server exe: powershell.exe args: > -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\start-webdriver-server.bat Remove > -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123 powershell.exe ​ from the line starting with args: ​ Change this: - name: Reset IE cache exe: powershell.exe args: > -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123 powershell.exe -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\reset-ie-cache.ps1 browsers: IE10, IE11 To this: - name: Reset IE cache exe: powershell.exe args: -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\reset-ie-cache.ps1 browsers: IE10, IE11 After you've made these changes, save the .yml file.    Finally, backup the start_agent.bat file first and then edit the original start_agent.bat file located at C:\appdynamics\synthetic-agent​ by modifying the following line: Change this:  if exist "C:\appdynamics\installers" (powershell.exe -ExecutionPolicy Unrestricted C:\appdynamics\cookbooks\run_chef_as_unprivileged_user.ps1 ) To this: rem if exist "C:\appdynamics\installers" (powershell.exe -ExecutionPolicy Unrestricted C:\appdynamics\cookbooks\run_chef_as_unprivileged_user.ps1 )   Does your scheduled task use the correct Admin user? If you’re running the scheduled task to start the agent, make sure to update the scheduled task to use the DOMAIN\appdadmin user instead of the agent_user for running said task. ... View more

Update 1/8/18 - This issue has been resolved in v4.5.5. Table of Contents Issue Overview Steps Issue For users who are impacted by EUMUI-2031 - HTTP Status 500 Error Returned When Accessing the Browser App Dashboard, there is a safe and simple workaround that can be applied to prevent the errant HTTP status 500 error warning boxes until the code fix is released by our Engineering team.  Overview  The workaround requires the temporary removal of the "Synthetic Availability Trend" widget from the Overview sub-tab of any EUM application Browser App Dashboard. Once removed, you can re-add the widget moments later, preventing future warning boxes as described above. The workaround is safe and will have no impact on product functionality/usability during the application of the workaround or anytime after it is applied.  Steps 1. For a given EUM Browser Application, access the Browser App Dashboard (ex: _Mike-P-TestApp). ​ ​ 2. Please find the "Synthetic Availability Trend" widget and click the small black x in the top right of the widget. This will remove the "Synthetic Availability Widget". Please note that the removal of the "Synthetic Availability Trend" widget it temporary. It will cause the "Synthetic Availability Trend" widget to be temporarily removed from all EUM Browser App Dashboards. ​ ​ 3. You will receive a confirmation that the widget was removed successfully in the form of a small blue text box in the top-right of the Controller's UI. ​ 4. After it's removed, re-add the "Synthetic Availability Trend" widget to the Browser App Dashboard by clicking the "+" button in the top-left of the Overview sub-tab and selecting the "Synthetic Availability Trend" option from the dropdown. 5. Completion of step four will add a new "Synthetic Availability Trend" widget to the chosen Browser App Dashboard and will also automatically add the "Synthetic Availability Trend" widget back to all the other EUM Browser App Dashboards.  Note: ​The process should only take 30 seconds to complete and, if applied properly, should prevent the red herring 500 errors warning boxes from showing up whenever a user accesses an EUM Browser App Dashboard going forward.  ... View more

Table of Contents Overview Generic F5 iRule template How to use this template Results Overview A load balancer is a device that distributes network or application traffic across a number of servers. Load balancers are used to increase the capacity and reliability of applications. When properly configured, F5 iRules utilize a scripting syntax that allows the load balancer to intercept, inspect, transform, and direct inbound or outbound application traffic. In the event that the application's source is unable to be modified and all other forms of injection have failed or are not applicable (e.g., assisted injection through Java rules for a PHP-based application), clients with a F5 load balancer can request their network security team configure an iRule to intercept an application's response and inject HTML into the page source necessary for enabling EUM. This is similar to the format that manual injection uses, but HTML is inserted into the webserver's response rather than into the original source code. For instructions on how to build, deploy, and test an iRule, we recommend consulting your F5 support team and network security team since they are most knowledgeable and equipped to handle such a request. From an AppDynanics perspective, you must be properly licensed for EUM and have End User Monitoring (EUM) enabled for an application in your AppDynamics Controller UI. Clients who have the limited option of injection via F5 iRules have seen success using a template similar to the iRule listed below. Note: If you are using the 4.3.x EUM JavaScript Agent, click here for instructions.  Generic F5 iRule template (requires further customization) when HTTP_REQUEST { if { [HTTP::uri] contains "segments/in/uri" } { set enableEum 1 HTTP::header remove "Accept-Encoding" } STREAM::disable } when HTTP_RESPONSE { STREAM::disable if { ( $enableEum == 1 ) && ( [HTTP::header "Content-Type"] starts_with "text/html" ) } { set search "</title>" set replace "</title>\ <script type='text/javascript' charset='UTF-8' src='//application.domain.com/adrum/adrum-config.js'></script>" STREAM::expression {@${search}@${replace}@} STREAM::enable } unset enableEum unset search unset replace } How to use this template 1) Matching Condition - The matching condition in your first "if statement." Change the condition in the above template to match inbound traffic to your application. In the template, we match against segments in the application's URI. However, there are other properties that can be used (e.g., [HTTP::path], [HTTP::host], etc.).  [HTTP::uri] contains "segment/in/uri" 2) Compression - Does your application use compression? If you are unsure if compression is being used, there is a simple Curl test to find out. The results will return one of three responses: "Content-Encoding: gzip" "Content-Encoding: deflate" or Nothing If the first or second response comes back, that means the site is using compression. An empty response means that compression is not being used. curl -sILH 'Accept-Encoding: gzip,deflate' <<URL>> | grep -i 'content-encoding' Example: curl -sILH 'Accept-Encoding: gzip,deflate' www.appdynamics.com | grep -i 'content-encoding' Response: content-encoding: gzip If compression is being used, uncomment the following line from the template. HTTP::header remove "Accept-Encoding"  If there isn't any compression, then keep the line commented out or remove it from the rule completely. # HTTP::header remove "Accept-Encoding" 3) JavaScript Agent Config (adrum-config.js) - What is the JavaScript agent config file and where does it get hosted? An agent config file ( adrum-config.js ) is injected directly into the page source. It is a small JavaScript file that contains the JavaScript Agent configuration options, such as the location of the adrum.js file, EUM application key, etc. The agent-config.js file is a self-hosted file. <script type='text/javascript' charset='UTF-8' src='//application.domain.com/adrum/adrum-config.js'></script> Before using the adrum-config.js file to initialize your JavaScript Agent configuration, you will need to update the file to match your EUM Application Key, hosted location of the JavaScript Agent files ( adrum.js or adrum-latest.js ), and the URL for the EUM Server (SaaS or On-Prem). The adrum-config.js example below assumes you are using our EUM cloud to process the JavaScript Agent beacon data, as well as the latest JavaScript Agent hosted in our CDN. You will need to create a file similar to this and host it yourself. A customized version of this file can be downloaded from within your EUM Application's configuration as documented here. window['adrum-start-time'] = new Date().getTime(); (function(config) { config.appKey = 'EUM-APP-KEY'; config.adrumExtUrlHttp = 'http://cdn.appdynamics.com'; config.adrumExtUrlHttps = 'https://cdn.appdynamics.com'; config.beaconUrlHttp = 'http://col.eum-appdynamics.com'; config.beaconUrlHttps = 'https://col.eum-appdynamics.com'; config.xd = { enable: false }; config.spa = { "spa2": false }; } )(window['adrum-config'] || (window['adrum-config'] = {})); document.write(unescape('%3Cscript') + " src='//cdn.appdynamics.com/adrum/adrum-latest.js' " + " type='text/javascript' charset='UTF-8' " + unescape('%3E%3C/script%3E'));   4) JavaScript Agent Config Options – What is your application-specific configuration?  EUM Application Key – What is your EUM Application Key as assigned in your Controller's UI? This can be found by accessing your EUM Application Configuration via the controller UI. The key is typically eight letters long. Change the example key (EUM-APP-KEY) in the above template to your specific application key. config.appKey = 'EUM-APP-KEY'; JavaScript Agent Location - Where is the JavaScript agent being hosted? If you intend to host the JavaScript agent file yourself, please update the source address for the adrum.js. Please see bolded lines in the example above for where to specify hosting location. document.write(unescape('%3Cscript') + " src='//cdn.appdynamics.com/adrum/adrum-latest.js' " + " type='text/javascript' charset='UTF-8' " + unescape('%3E%3C/script%3E')); EUM Collector URL - Where should the agent send the beacon data? If you are using an On-Prem EUM server, you will need to update the  config.beaconUrlHttp  and  config.beaconUrlHttps  above. For more information on how to find this URL, please refer to our documentation on manual injection found here. config.beaconUrlHttp = 'http://col.eum-appdynamics.com'; config.beaconUrlHttps = 'https://col.eum-appdynamics.com';  JavaScript Agent Extension Location - Where should the agent download the adrum-ext.js file? If you are hosting the JavaScript Agent extension file yourself, you will want to update the  config.adrumExtUrlHttp  and  config.adrumExtUrlHttps  above. For more information on how to find this URL, please refer to our documentation on manual injection found here. config.adrumExtUrlHttp = 'http://cdn.appdynamics.com'; config.adrumExtUrlHttps = 'https://cdn.appdynamics.com'; Cross-Domain Session Correlation - Do I want to monitor cross-domain sessions? As described in our documentation here, cross-domain session correlation is disabled by default. If you wish to monitor sessions which span multiple domains, you will want to update  config.xd  in the template above.  config.xd = { enable: true }; SPA2 Monoitoring - Do I want to enable SPA2 Monitoring? As described in our documentation here, SPA2 Monitoring is disabled by default. If you wish to enable, you will want to update  config.spa  in the template above.  config.spa = { "spa2": true }; 5) Other Points To Consider  In some cases, the Stream profile must re-enable response re-chunking as documented in https://support.f5.com/csp/article/K6422. Although the above script template is typically successful, every client environment is different. Therefore, our team recommends that you consult a trained engineer responsible for managing your F5 load balancer. We also highly recommend testing in a sandbox or development environment before deploying any changes to your production environment. Results If properly configured, the iRule matches a condition for your application-specific traffic, the load balancer will inject the EUM-specific source via the adrum-config.js file into the response received by the browser. This will allow the Javascript Agent and the associated configurations to load in the browser, capture EUM data, and send the associated beacons back to the EUM Server. <script type='text/javascript' charset='UTF-8' src='//application.domain.com/adrum/adrum-config.js'></script> Sample Files (see attachments): adrum-config.js.txt iRule-template.txt ... View more

When planning an Events Service backup using the built-in snapshots functionality, you may have to calculate how much space is needed for the allocation of storage space. The most accurate and easiest way I have found to check the expected size of an Events Service backup is by running through the following steps: 1. On one of the nodes in the cluster, please run the following command to determine the master node and the size of its primary store according to Elastic Search. Note: Please update the host variable if the host is not listening on localhost. host="localhost" master=$(curl -s -XGET http://${host}:9200/_cat/master | awk $'{print $2}') sizeMaster=$(curl -s -XGET http://${host}:9200/_cat/allocation | grep "${master}" | awk $'{print $2}') echo "Master Node:  ${master} | Store Size:  ${sizeMaster}" 2. To validate the size found in step 1, please SSH into the master node so we can verify that the store size is consistent with what we are seeing in the physical data directory. Please execute the following commands: cd [EVENTS_SERVICE_HOME]/processor/conf dataDir=$(cat events-service-api-store.properties | grep "dataDirectory" | cut -d"=" -f2 | rev | cut -d"/" -f2- | rev) sizeDataDir=$(du -sh "${dataDir}" | awk $'{print $1}') echo "Data Directory: ${dataDir} | Directory Size: ${sizeDataDir}" For example, in my demo 3-node clustered Events Service, I found the following results: 1. From one of the nodes in my cluster, I executed step 1 and the following results were returned: Master Node:  192.168.254.128  |    Store Size:  315.7mb 2. I then started a terminal session into my master node 192.168.254.128 to calculate the physical size of the data directory as defined in the  events-service-api-store.properties  file. Data Directory:  /opt/AppDynamics/Data  |  Directory Size:  319M 3. Post-Backup Validation - To make sure the values found in 1 and 2 are consistent with the actual size of a full snapshot backup, I took a full backup and verified the size of the backup.  cd [EVENTS_SERVICE_HOME]/processor snapshotBytes=$(bin/events-service.sh snapshot-status -p conf/events-service-api-store.properties | cut -d',' -f7 | cut -d'=' -f2) echo "Snapshot Size: $(( snapshotBytes / (1024 * 1024) ))M" The command above returns several properties related to the snapshot, one of them being size in bytes. After a quick conversion, the calculation above shows the size in MB. Snapshot state is SUCCESS. Details: SnapshotStatus(startTime=2018-10-22T20:25:10.166Z, endTime=2018-10-22T20:25:40.503Z, durationInMillis=30337, numberOfFiles=868, processedFiles=868, totalSizeInBytes=330175594, processedSizeInBytes=330175594). Snapshot Size: 314M From the three different checks I confirmed that the known store size values are 315.7MB, 319MB, and 314MB. As a safe bet, I will go with the largest of the three values (319MB) as the size of my Events Service's full data backup.    ... View more

Similar to the steps outlined in the Set the Security Protocol document for the Controller, you can also set the security protocol or update the existing security protocol used by the EUM Server. The document link above refers to changing these settings for the Controller. However, these can be applied when setting the JRE security protocol for the EUM Server. The location of the JRE installation and  java.security  file for the EUM Server is the major difference to keep in mind when following the steps for the Controller. The process is still the same.   To enable encryption keys up to 256-bit in the EUM Server, download and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files within the EUM Server's embedded Java runtime.  Download the Unlimited Strength Jurisdiction Policy Files from the following location: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html  Stop the EUM app server. Install the policy files in the JRE installed under the EUM Server's "Installation Path". Start the EUM app server.  After restarting the EUM app server, the following cipher suites become available: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDH_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA If you want to modify the cipher suites, you can use the following steps. Please note that the example below shows how you would disable the DES cipher. Download the Unlimited Strength Jurisdiction Policy Files from the following location: http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html. Extract the contents of the downloaded policy files. Stop the EUM app server. Make a copy of the original JCE policy files ( US_export_policy.jar and local_policy.jar ). Replace the strong policy files in EUM Server's <java-home>\lib\security directory with the unlimited strength versions extracted during Step 2. From the EUM Server's  <java-home>\lib\security  directory, make a copy of the  java.security file and add the line jdk.tls.disabledAlgorithms=MD5, SHA1, DSA, DES RSA keySize < 2048  to the original file. Save the changes. Start the EUM app server. As always, when making a change that will affect the availability and security of a production environment, we recommend testing in a development/pre-prod environment first to ensure you get the results you expect. Once verified outside of production, you can then follow the same steps in the live production environment. Precautionary measures such as backing up the original file before modification are always a good idea.  ... View more

Assuming you are already successfully auto-injecting the EUM JavaScript Agent, the following steps can be used to turn on SPA2 monitoring. 1. From the User Experience tab, double-click on the EUM application you'd like to enable SPA2 monitoring for. You'll be directed to the application's Browser App Dashboard.  2. Once you are on the Dashboard, select the Configuration sub-tab at the bottom left of the window.  3. Select the option to "Configure JavaScript Agent" (see the screenshot above).    4. Select the "Advanced" option.    5. Scroll down slightly to add the following custom configuration.  (function(config){ config.spa = {spa2:true}; })(window['adrum-config'] || (window['adrum-config'] = {}));      6.  Scroll down and click "Save Config & Generate HTML Snippet." At this point, your EUM application will now have the SPA2 configuration enabled for auto-injection. Please send a load of traffic to the pages that are instrumented with auto-injection until you are able to see the configuration update. ... View more

To work around this issue, follow the steps outlined below. Essentially, you will be changing the EUM key within the events-service-api-store.properties file temporarily so that EUM can fail authorization again. Once the EUM Server fails, you will change the EUM key back to the original value, at which point the EUM Server should successfully connect. Please note that the paths to the platform components in the commands below will need review to ensure accuracy. 1. Please stop your EUM Server manually. Once the EUM Server is stopped, use your Platform Admin CLI to stop the Events Service (ES) cluster. On EUM Host: cd [EUM_HOME_DIR]/eum-processor bin/eum.sh stop On Platform Admin Host: cd [PA_HOME_DIR]/platform-admin bin/platform-admin.sh submit-job --service events-service --job stop   2. Back up your events-service-api-store.properties  file on all of the ES nodes. On Events Service Nodes: cp -R /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties.orig 3. Update the  events-service-api-store.properties  file (not  .orig ) on each of the ES nodes, changing the last character in  ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea60 ​. For example: ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea6a ​. On Events Service Nodes: sed -i 's/6a981b83-251d-4d0b-a56a-b309fc3bea60/6a981b83-251d-4d0b-a56a-b309fc3bea6a/g' /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties   4. Using your Platform Admin CLI, start the Events Service cluster. Once the ES cluster is running, start your EUM Server manually. On Platform Admin Host: cd [PA_HOME_DIR]/platform-admin bin/platform-admin.sh submit-job --service events-service --job start On EUM Host: cd [EUM_HOME_DIR]/eum-processor nohup bin/eum.sh start &   5. Once the EUM Server fails authorization again, stop the EUM Server manually and stop the Events Service cluster using your Platform Admin CLI. On EUM Host: cd [EUM_HOME_DIR]/eum-processor bin/eum.sh stop On Platform Admin Host: cd [PA_HOME_DIR]/platform-admin bin/platform-admin.sh submit-job --service events-service --job stop 6. Update the  events-service-api-store.properties  file on each of the ES nodes, changing the last character in  ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea6a ​  back to the original value. For example:  ad.accountmanager.key.eum=6a981b83-251d-4d0b-a56a-b309fc3bea60 ​. On Events Service Nodes: mv /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties.orig /opt/appdynamics/events-service/processor/processor/conf/events-service-api-store.properties 7. Using your Platform Admin CLI, start the Events Service cluster. Once the ES cluster is running, start your EUM Server manually. On Platform Admin Host: cd [PA_HOME_DIR]/platform-admin bin/platform-admin.sh submit-job --service events-service --job start On EUM Host: cd [EUM_HOME_DIR]/eum-processor nohup bin/eum.sh start & At this point, the Events Service nodes will be configured with the original EUM key and the EUM Server should successfully connect to the Events Service. Please contact AppDynamics Support if you continue to encounter issues. ... View more

Table of Contents Description Requirements Reason Overview Steps Description This article walks through how to add required edits to events-service.vmoptions if you are using the Enterprise Console Discovery process. This is a temporary workaround in order to succeed with the Discovery process, therefore allowing you to administer your Events Service node/cluster using the Enterprise Console. Requirements If there is an existing (4.4.x/4.5.x) Events Service node/cluster that requires specific options be added to the events-service.vmoptions in order to start. A system which has noexec for their /tmp directory will likely qualify. If you are discovering an existing Events Service node/cluster and the process is unsuccessful due to failed health checks. Reason When the Enterprise Console's Discovery process is used to find an existing Events Service cluster/node, the tasks will fail to complete due to the events-service.vmoptions file being reset to their defaults on each of the nodes. Once the vmoptions are reset, the node will fail to start, leading to the node(s) failing the health check required by the Discovery process. Overview In short, what you'll do is take the prepackaged vanilla events-service.zip  file that comes with the Enterprise Console (ex: [ENTERPRISE_CONSOLE_HOME_DIR]/platform-admin/archives/events-service/4.5.2.20561/events-service.zip ), unpack the archive, add the required   vmoptions ​ file to the events-service.vmoptions file​, recompress the modified events-service directory, and then run the Discovery process with the Enterprise Console. Before you start, please make a backup copy of the existing Events Service installation. If you have any doubts or are unsure about whether these steps are needed for your deployment -- PLEASE STOP HERE. Steps 1.   From the terminal of the Enterprise Console host, please navigate to the following directory (or whatever is the latest 4.4.x/4.5.x version directory available). cd [ENTERPRISE_CONSOLE_HOME_DIR]/platform-admin/archives/events-service/4.5.2.20561 2.   The directory should have the following contents: ....4.5.2.20561]# ls -1 events-service.zip pa-es.jar playbooks service.yml 3.  Backup the original  events-service.zip ​. cp events-service.zip events-service.zip.bk 4. Unzip the original archive and remove the archive. unzip events-service.zip -d ./modified rm events-service.zip 5.  At this stage, your present working directory listing should look like  ....4.5.2.20561]# ls -1 events-service.zip.bk modified pa-es.jar playbooks service.yml and the  modified ​subdirectory will contain the unzipped  events-service ​directory. 4.5.2.20561]# find ./modified -maxdepth 2 ./modified ./modified/events-service ./modified/events-service/bin ./modified/events-service/plugins ./modified/events-service/elasticsearch ./modified/events-service/version.txt ./modified/events-service/lib ./modified/events-service/conf 6.   Navigate to  ./modified/events-service/conf ​and using your editor of choice, please update the  events-service.vmoptions ​file to include your required options. In our example, the options that can be added are either -Djna.tmpdir=/new/tmp/location​ or  -Djava.io.tmpdir=/new/tmp/location ​where  /new/tmp/location  is a path on the host machine which is has  exec  permissions -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djna.tmpdir=/new/tmp/location​ -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+DisableExplicitGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintClassHistogram -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -verbose:gc -XX:GCLogFileSize=64m -XX:NumberOfGCLogFiles=4 -XX:+UseGCLogFileRotation -XX:CompileCommand=exclude,org/apache/lucene/lucene54/Lucene54DocValuesConsumer.addSortedNumericField -XX:CompileCommand=exclude,org/apache/lucene/lucene54/Lucene54DocValuesConsumer.addBinaryField -XX:CompileCommand=exclude,org/elasticsearch/search/aggregations/metrics/percentiles/tdigest/AbstractTDigestPercentilesAggrega$ -XX:CompileCommand=exclude,org/apache/lucene/index/SortedNumericDocValuesWriter.flush -XX:CompileCommand=exclude,org/apache/lucene/codecs/PushPostingsWriterBase.writeTerm 7.  Save out the file and navigate to the version directory if you've navigated away. cd [ENTERPRISE_CONSOLE_HOME_DIR]/platform-admin/archives/events-service/4.5.2.20561 8.   Move the modified events-service directory one level up and then r ecompress the  events-service ​directory containing the edits mv ./modified/events-service ./events-service zip -r events-service.zip ./events-service 9.  At this point, the version directory listing should look like the following: 4.5.2.20561]# ls -1 events-service.zip <---modified events-service.zip events-service.zip.bk <---original events-service.zip modified pa-es.jar playbooks service.yml 10.   Remove the directory  modified ​now that the edits have been made rm -rf ./modified 11.   Feel free to backup the modified archive to a temp directory in the event you wish to save time if you are running multiple tests. 12.   In the Enterprise Console UI, run the Discovery task again. 13.  The hope is that the full Discovery process will now complete, allowing you to administer this cluster using the Enterprise Console. 14. If the Discovery process completes, one can assume the required options have not been reset. To be extra sure, you can verify all the required options are present in the events-service.vmoptions by running the following command on each node: cat [EVENTS_SERVICE_HOME_DIR]/processor/conf/events-service.vmoptions ... View more

A load balancer is a device that distributes network or application traffic across a number of servers. Load balancers are used to increase capacity and reliability of applications. When properly configured, F5 iRules utilize a scripting syntax which allows the load balancer to intercept, inspect, transform, and direct inbound or outbound application traffic. In the event the application's source is unable to be modified and all other forms of injection have failed or are not applicable (i.e. assisted injection through Java rules for a PHP-based application), clients with a F5 load balancer can request their network security team configure an iRule to intercept an application's response and inject HTML into the page source necessary for enabling EUM. This is similar to the format that manual injection uses, but HTML is inserted into the webserver's response rather than into the original source code. For instructions on how to build, deploy, and test an iRule, we recommend you consult your F5 support team and network security team as they are most knowledgeable and equipped to handle such a request. From an AppDynanics perspective, you must be properly licensed for EUM and have End User Monitoring (EUM) enabled for an application in your AppDynamics Controller UI. Clients who have the limited option of injection via F5 iRules have seen success using a template similar to the iRule listed below. Generic F5 iRule Template (requires further customization) when HTTP_REQUEST  {   # This is the condition for which requests will be matched against   if {[HTTP::uri] contains "segment/in/uri"} {    set enableEum 1    }    else {    set enableEum 0    }   # Disable the stream filter for client requests as we are only interested in the server response   STREAM::disable   # LTM does not uncompress response content, so if the server has compression enabled   # and it cannot be disabled on the server, we can prevent the server from   # sending a compressed response by removing the compression offerings from the client   # HTTP::header remove "Accept-Encoding"  }    when HTTP_RESPONSE  {   # Disable the stream filter for all server responses   STREAM::disable   # Inserts the necessary JavaScript for EUM   if {($enableEum == 1) && ([HTTP::header "Content-Type"] starts_with "text/html")} {    STREAM::expression {    @</title>@</title>    <script type="text/javascript" src="https://application.domain.com/adrum/adrum-config.js"></script>@}   # Enable the stream filter for this response only   STREAM::enable    }  } How to use this template 1) Matching Condition - The matching condition in your first "if statement." Change the condition in the above template to match inbound traffic to your application. In the template we match against segments in the application's URI. However, there are other properties which can be used (i.e [HTTP::path], [HTTP::host], etc.).  [HTTP::uri] contains "segment/in/uri" 2) Compression - Does your application use compression? If you are unsure if compression is being used, there is a simple Curl test to find out. The results will return one of three responses: 1) "Content-Encoding: gzip". 2) "Content-Encoding: deflate", or 3) nothing. If the first or second response comes back that means the site is using compression, while an empty response means that compression is not being used. Test: curl -sILH 'Accept-Encoding: gzip,deflate' www.appdynamics.com | grep 'Content-Encoding' Response: Content-Encoding: gzip If compression is being used, uncomment the following line from the template. HTTP::header remove "Accept-Encoding"  If there isn't any compression, then keep the line commented out or remove it from the rule completely. # HTTP::header remove "Accept-Encoding" 3) JavaScript Agent Config Location - Where is the JavaScript agent config file being hosted? Slightly different than the previous version of the injection rule, an Agent config file (adrum-config.js) is injected directly into the page source. The Agent config file is a small JavaScript file which contains the 4.3.x JavaScript Agent configuration options such as the location of the adrum.js file, EUM application key, etc. The agent-config.js file is a self-hosted file. <script type="text/javascript" src="https://application.domain.com/adrum/adrum-config.js"></script> Before using the adrum-config.js file to initialize your JavaScript Agent configuration you will need to update the file to match your EUM Application Key, hosted location of the JavaScript Agent files (adrum.js or adrum-latest.js), as well as the URL for the EUM Server (SaaS or On-Prem). The adrum-config.js example below assumes you are our EUM cloud to process the JavaScript Agent beacon data as well as the latest JavaScript Agent hosted in our CDN. You will need to create a file similar to this and host it yourself. A customized version of this file can be downloaded from within your EUM Application's configuration as documented here. window['adrum-start-time'] = new Date().getTime(); (function(config){         config.appKey = 'AAB-AA-AUA';         config.adrumExtUrlHttp = 'http://cdn.appdynamics.com';         config.adrumExtUrlHttps = 'https://cdn.appdynamics.com';         config.beaconUrlHttp = 'http://col.eum-appdynamics.com';         config.beaconUrlHttps = 'https://col.eum-appdynamics.com';         config.xd = {enable : false}; })(window['adrum-config'] || (window['adrum-config'] = {})); if ('https:' === document.location.protocol) {        document.write(unescape('%3Cscript')        + " src='https://cdn.appdynamics.com/adrum/adrum-latest.js' "        + " type='text/javascript' charset='UTF-8'"        + unescape('%3E%3C/script%3E')); } else {        document.write(unescape('%3Cscript')        + " src='http://cdn.appdynamics.com/adrum/adrum-latest.js' "        + " type='text/javascript' charset='UTF-8'"        + unescape('%3E%3C/script%3E')); } 4) JavaScript Agent Config Options – What is your application-specific configuration?  EUM Application Key – What is your EUM Application Key as assigned in your Controller's UI? This can be found by accessing your EUM Application Configuration via the controller UI. The key is typically eight letters long. Change the example key (AAB-AA-AUA) in the above template to your specific application key. src='https://cdn.appdynamics.com/adrum/adrum-latest.js' JavaScript Agent Location - Where is the JavaScript agent being hosted? If you intend to host the JavaScript agent file yourself, please update the source addresses in the if-else conditional statements at the bottom of the adrum-config.js file. Please see bolded lines in the example above for where to specify hosting location.   src='https://cdn.appdynamics.com/adrum/adrum-latest.js' and   src='http://cdn.appdynamics.com/adrum/adrum-latest.js' EUM Server URL - Where should the agent send the beacon data? If you are using an On-Prem EUM server, you will need to update the config.beaconUrlHttp and config.beaconUrlHttps above. For more information on how to find this URL, please refer to our documentation on manual injection found here. config.beaconUrlHttp = 'http://col.eum-appdynamics.com'; and config.beaconUrlHttps = 'https://col.eum-appdynamics.com'; 5) Other Points To Consider  In some cases, the Stream profile must re-enable response re-chunking as documented in https://support.f5.com/csp/article/K6422. Although the above script template is typically successful, every client environment is different. Therefore our team recommends that you consult a trained engineer responsible for managing your F5 load balancer. We also highly recommend testing in a sandbox or development environment before deploying any changes to your production environment. Results If properly configured, the iRule matches a condition for your application-specific traffic, the load balancer will inject the EUM-specific source (adrum-config.js) into the response received by the browser allowing the Javascript agent and the associated configuration to load in the browser, capture EUM data, and send the associated beacons back to the EUM Server. <script src="https://application.domain.com/adrum/adrum-config.js"></script> ... View more

The instructions below will guide you through how to configure Metric Browser baselines for User Experience applications. In this example, we are using a User Experience application named "EUM ONLY." Follow steps 1-9 below.  1. Click the Applications tab. ​ 2. Click the Actions button and check the box "Include Applications from User Experience." Note: You'll notice that the User Experience application named "EUM Only" is now listed. 3. Double-click on the EUM application. 4. Select Configuration > Baselines. 5. Create a baseline and configure the available options (or keep the defaults), then click Save. 6. Click the User Experience tab and double-click on the EUM application. 7. Click the Metric Browser button.   8. Verify that the new baseline exists for the EUM application via the drop-down menu in the top right corner.   9. Use the new baseline with EUM metrics. ... View more

 Assuming the following application structure. Please note that there are several important elements missing from the list required to make a functional Angular 2 app. src \   - favicon.ico   - index.html   - systemjs.config.js   app \     - app.component.html     - app.component.css     - app.component.ts     - app.module.ts     - app.routing.ts     - main.ts     - test.component.html - test.component.css - test.component.ts   assets \     - adrum-config.js     - adrum.js     - adrum-ext.js // index.html <html> <head>   <base href="/">   <title>Mp Test App</title>   <meta charset="UTF-8">   <meta name="viewport" content="width=device-width, initial-scale=1">   <script src="node_modules/core-js/client/shim.min.js"></script>   <script src="node_modules/zone.js/dist/zone.js"></script>   <script src="node_modules/reflect-metadata/Reflect.js"></script>   <script src="node_modules/systemjs/dist/system.src.js"></script>   <script src="assets/adrum-config.js"></script>   <script src="systemjs.config.js"></script>   <link href="resets.css" rel="stylesheet">   <script>         System.import('app').catch(function(err){ console.error(err); });     </script> </head> <body>   <mp-app>Loading...</mp-app> </body> </html> // adrum-config.js window['adrum-start-time'] = new Date().getTime(); (function(config){     config.appKey = 'EUM-APP-KEY';     config.adrumExtUrlHttp = 'assets';     config.adrumExtUrlHttps = 'assets';     config.beaconUrlHttp = 'http://eum-collector.example.com:7001';     config.beaconUrlHttps = 'https://eum-collector.example.com:7002';     config.xd = {enable : true}; })(window['adrum-config'] || (window['adrum-config'] = {})); if ('https:' === document.location.protocol) {     document.write(unescape('%3Cscript')   + " src='assets/adrum.js' "   + " type='text/javascript' charset='UTF-8'"   + unescape('%3E%3C/script%3E'));  } else {     document.write(unescape('%3Cscript')   + " src='assets/adrum.js' "   + " type='text/javascript' charset='UTF-8'"   + unescape('%3E%3C/script%3E'));  }  // main.ts import { platformBrowserDynamic } from '@angular/platform-browser-dynamic'; import { AppModule } from './app.module'; platformBrowserDynamic().bootstrapModule(AppModule); // app.module.ts import { NgModule } from '@angular/core'; import { BrowserModule } from '@angular/platform-browser'; import { ReactiveFormsModule } from '@angular/forms'; import { HttpModule } from '@angular/http'; import { AppComponent } from './app.component'; import { TestComponent } from './test.component'; import { routing } from './app.routing'; @NgModule({   imports: [     BrowserModule,     ReactiveFormsModule,     HttpModule,     routing   ],   declarations: [     AppComponent,     TestComponent     ],   providers: [     ],   bootstrap: [     AppComponent   ] }) export class AppModule {} // app.component.html <nav>   <a routerLink="/">   LINK   </a> </nav> <section>   <header>     <h1>TEST</h1>   </header>   <router-outlet></router-outlet> </section> // app.component.ts import { Component } from '@angular/core'; @Component({   selector: 'mp-app',   templateUrl: 'app/app.component.html',   styleUrls: ['app/app.component.css'] }) export class AppComponent { } // test.component.ts import { Component, Inject } from '@angular/core'; import { Router } from '@angular/router'; import { lookupListToken } from './providers'; declare var ADRUM: any; var vpView = new ADRUM.events.VPageView(); @Component({   selector: 'test',   templateUrl: 'app/test.component.html',   styleUrls: ['app/test.component.css'] }) export class TestComponent {   form;   constructor(     private formBuilder: FormBuilder,     @Inject(lookupListToken) public lookupLists,     private router: Router) {}   ngOnInit() {     vpView.start();     // mark start of vp     vpView.markViewChangeStart();     // mark view change start     }   ngOnChanges() {     .....     }     ngOnDestroy() {     vpView.markViewChangeEnd();     // mark view change end     vpView.markViewDOMLoaded();     // mark dom loaded     vpView.markXhrRequestsCompleted();     // mark xhrs completed     vpView.markViewResourcesLoaded();     // mark resources loaded         vpView.end();     // mark end of vp     ADRUM.report(vpView);     // report vp     } } // app.routing.ts import { Routes, RouterModule } from '@angular/router'; import { TestComponent } from './test.component'; const appRoutes: Routes = [   { path: '', pathMatch: 'full', redirectTo: 'all' } ]; export const routing = RouterModule.forRoot(appRoutes); export class AppRoutingModule { constructor(router:Router) { var vPageView = new ADRUM.events.VPageView(); router.events.forEach((event: NavigationEvent) => { // NavigationStart var absoluteURI = ADRUM.utils.getFullyQualifiedUrl(event.url); if(event instanceof NavigationStart) { console.log(ADRUM.utils.getFullyQualifiedUrl(event.url)); vPageView = new ADRUM.events.VPageView({ url: absoluteURI, }); console.log("init adrum pg"); vPageView.start(); vPageView.markViewChangeStart(); console.log(vPageView); } // NavigationEnd if (event instanceof NavigationEnd) { //give it 0.5s setTimeout(function(){ console.log("NavEnd"); vPageView.markViewChangeEnd(); vPageView.markViewDOMLoaded(); vPageView.markXhrRequestsCompleted(); vPageView.markViewResourcesLoaded(); vPageView.end(); ADRUM.report(vPageView); console.log(vPageView); }, 500); } // NavigationCancel // NavigationError // RoutesRecognized }); } } ... View more

1. Make commands generic 2. Make statement how any existing data in associated with the original field will be lost / needs transfer After doing further research there does not appear to be a standard way of changing the data format associated with a field once it's created. There is available workaround which will remove the old field, add a new field with the correct data type, and then rename the new field to the original field name. Given you agree with ALL of the assumption below you should be able to follow these steps to achieve your updated field data format. Assumptions:  1. You have a schema named  performancedetail 2. You have a field named  old_name  which is in  integer  format 3. There is no data associated with the field  old_name   4. You would like to change the data format for  old_name ​ from  integer  to  float   1. View Original Schema: curl -s -XGET "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type: application/vnd.appd.events+json;v=2" -H"Accept: application/vnd.appd.events+json;v=2" Response: {   "eventType": "performancedetail",   "schema": {     "eventTimestamp": "date",     "pickupTimestamp": "date",     "id": "integer",     "old_name": "integer"   } } 2. Add New Field To Schema With Correct Data Type curl -s -XPATCH "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type:application/vnd.appd.events+json;v=2" -H"Accept:application/vnd.appd.events+json;v=2" -d '[{ "add": { "new_name": "float" } }]' 3. View Updated Schema curl -s -XGET "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type: application/vnd.appd.events+json;v=2" -H"Accept: application/vnd.appd.events+json;v=2"   Response: {   "eventType": "performancedetail",   "schema": {     "eventTimestamp": "date",     "pickupTimestamp": "date",     "id": "integer",     "old_name": "integer",     "new_name": "float"       } } 4. (Optional) Delete Old Field From Schema curl -s -XPATCH "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type:application/vnd.appd.events+json;v=2" -H"Accept:application/vnd.appd.events+json;v=2" -d '[{ "delete": [ "old_name" ] }]' 5. (Optional) View Resulting Schema curl -s -XGET "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type: application/vnd.appd.events+json;v=2" -H"Accept: application/vnd.appd.events+json;v=2"   Response: {   "eventType": "performancedetail",   "schema": {     "eventTimestamp": "date",     "pickupTimestamp": "date",     "id": "integer",     "new_name": "float"       } } 6. (Optional) Rename New Field To The Original Field Name curl -s -XPATCH "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type:application/vnd.appd.events+json;v=2" -H"Accept:application/vnd.appd.events+json;v=2" -d '[{ "rename": { "new_name": "old_name" } }]' 7. (Optional) View Final Schema curl -s -XGET "http://svphxappdynprd02.hotelgroup.com:9080/events/schema/performancedetail" -H"X-Events-API-AccountName:customer1_197d3f0a-9a8d-4​0c4-a883-047266c8ae70" -H"X-Events-API-Key:d25c5243-1682-4434-b15b-5b7318a9c2d7" -H"Content-type: application/vnd.appd.events+json;v=2" -H"Accept: application/vnd.appd.events+json;v=2"   Response: {   "eventType": "performancedetail",   "schema": {     "eventTimestamp": "date",     "pickupTimestamp": "date",     "id": "integer",     "old_name": "float"       } }  _______________________________________________________________________________________ Was this helpful? Give it kudos [click on the thumbs up icon at the end of the article, bottom left corner] to let others know too! Do you have a question or need clarification? [Post Your Comment] Below.  ... View more

In an ongoing effort to improve security around the data captured and reported via the Synthetic Monitoring Product suite, the below change is being rolled out to Appdynamics' Synthetics Cloud Description: Currently, if you have Synthetic jobs that pass credentials to the website(your are monitoring) by embedding them in the URL (e.g. http://user:pass@site.com), then those credentials propagate to the resulting Synthetic Sessions and therefore are visible in the UI in plain text. Common industry security practice(s) classifies such clear text username / passwords as sensitive / confidential. Change: In our upcoming 4.4.1 Synthetics Cloud deployment, we will begin to redact these credentials from Synthetic Sessions, and this data will no longer appear in the UI.  Impact to you: Depending on your EUM Page Naming rules, it's possible that some of your Pages currently include these credentials. For example, if your synthetic job visited the page http://user:pass@site.com, you may have Pages named "user:pass@site.com". Because this change will strip out the credentials, data will subsequently be reported under just "site.com". This could impact you in two ways: If you were tracking metrics for that specific page, you will need to track the new page instead. If you have reached the limit for registered Pages (this is rare), you will need to remove the orphaned page before you'll see data for the new Page. Should you have any questions regarding this change OR need help with the impact of this change to your monitoring framework, please contact AppDynamics Support at help@appdynamics.com ... View more

Symptoms After upgrading the EUM Server from version 4.0.x or 4.1.x to 4.2+, the EUM Server will not start. The following errors will be displayed when attempting to start the EUM Server: 08 Jun 2017 00:19:24.472 +0200 main AD.SqlAccountSettingStore ERROR | Exception caught while getting account analytics info: | SQL: select * from account_settings | | com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'eum_db.account_settings' doesn't exist | at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) | at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) | at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) | at java.lang.reflect.Constructor.newInstance(Unknown Source) | at com.mysql.jdbc.Util.handleNewInstance(Util.java:404) | at com.mysql.jdbc.Util.getInstance(Util.java:387) | at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:941) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) | at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) | at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) | at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) | at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2550) | at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861) | at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962) | at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76) | at com.appdynamics.eumcloud.data.sql.SqlQuery.execute(SqlQuery.java:39) | at com.appdynamics.eumcloud.data.sql.SqlAccountSettingStore.getAccountSettings(SqlAccountSettingStore.java:64) | at com.appdynamics.eumcloud.data.cache.AccountSettingsCache.<init>(AccountSettingsCache.java:30) | at com.appdynamics.eumcloud.data.cache.AccountSettingsCache$$FastClassByGuice$$c7e60f52.newInstance(<generated>) | at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) | at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) | at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) | at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) | at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) | at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) | at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) | at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) | at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) | at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) | at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) | at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) | at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) | at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) | at com.appdynamics.eum.processor.EUMProcessorServerApplication.startServer(EUMProcessorServerApplication.java:244) | at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:178) | at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:114) | at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:42) | at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76) | at io.dropwizard.cli.Cli.run(Cli.java:70) | at io.dropwizard.Application.run(Application.java:72) | at com.appdynamics.eumcloud.EUMProcessorServer.main(EUMProcessorServer.java:40) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) | at com.exe4j.runtime.WinLauncher$2.run(Unknown Source) | +--------------------------------------------------------------------------------------- 08 Jun 2017 00:19:24.472 +0200 main AD.EUMFixedThreadPool INFO Created [Analytics Event Dispatcher Processors] Thread Pool with [20] Threads 08 Jun 2017 00:19:24.503 +0200 main AD.EUMFixedThreadPool INFO Created [Analytics Event Dispatcher Processors] Thread Pool with [3] Threads 08 Jun 2017 00:19:24.503 +0200 main AD.ADAppAgentModule INFO JVM not instrumented with AD Agent; reporting disabled 08 Jun 2017 00:19:24.535 +0200 main AD.ALL ERROR | Error Starting EUM Processor Server | java.lang.RuntimeException: Failed to verify table [mobile_infopoints]: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'eum_db.mobile_infopoints' doesn't exist | Failed to verify table [mobile_packages]: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'eum_db.mobile_packages' doesn't exist | | at com.appdynamics.eum.processor.EUMProcessorServerApplication.startServer(EUMProcessorServerApplication.java:260) | at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:178) | at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:114) | at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:42) | at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:76) | at io.dropwizard.cli.Cli.run(Cli.java:70) | at io.dropwizard.Application.run(Application.java:72) | at com.appdynamics.eumcloud.EUMProcessorServer.main(EUMProcessorServer.java:40) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) | at java.lang.reflect.Method.invoke(Unknown Source) | at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) | at com.exe4j.runtime.WinLauncher$2.run(Unknown Source) | +--------------------------------------------------------------------------------------- Diagnosis The issue arises when the EUM installer fails to add tables to the EUM database during the upgrade process. Related Links: Upgrading the EUM Server Solution Manually add the missing tables to the EUM database using the 407to410.sql file which is located in /opt/AppDynamics/EUM/eum-processor/bin/ or [EUM_HOME]/eum-processor/bin/ after running the downloaded 4.2+ EUM installation script. Then validate the changes using the eum-schema command. Assumptions: Controller and EUM Server are hosted on a Linux OS. Controller home directory is  /opt/AppDynamics/Controller/ . EUM Server home directory is  /opt/AppDynamics/EUM/eum-processor/ . Controller IP address is 192.168.102.99. 1. In the command line, log in to EUM Server to confirm the EUM processor is not running. cd /opt/AppDynamics/EUM/eum-processor/ bin/eum.sh stop 2. Log in to Controller host. 3. Navigate to the Controller's database directory to access the MySQL client binary. cd /opt/AppDynamics/Controller/db/bin 4. Execute the following query to update eum_db with the missing tables. Note: Update the Controller's installation path for the EUM Server and hostname/IP address for the eum_db. ./mysql -u root -p -P 3388 -h 192.168.102.99 -D eum_db < /opt/AppDynamics/EUM/eum-processor/bin/407to410.sql 5. On the Controller, re-run the EUM installation and select option 2. This will complete the remaining  eum_db updates. 6. Once the EUM installer completes on Controller, navigate to the bin directory of the Controller's installation of the EUM Server. cd /opt/AppDynamics/EUM/eum-processor/bin 7. Create a backup of the liquibase.properties file, then update and save the original file in order to use the current EUM user's database password. cp liquibase.properties liquibase.properties.bak 8. Validate the changes to the EUM database using the eum-schema command. ./eum-schema updateSQL 9. The outputs after running the eum-schema command should generate similar output to the following: --  ********************************************************************* --  Update Database Script --  ********************************************************************* --  Change Log: liquibaseChangelog.xml --  Ran at: 9/2/16 12:49 PM --  Against: eum_user@localhost@jdbc:mysql://localhost:3388/eum_db?createDatabaseIfNotExist=true --  Liquibase version: 3.2.0 --  ********************************************************************* --  Lock Database --  Release Database Lock 10. On success, return to the EUM Server host and start the EUM Server. ... View more

As of version 4.2.x, the EUM Server is not available for High Availability out of the box. High Availability Controller deployment is available to help minimize disruptions caused by server or network failure, administrative downtime, and other interruptions. Those interested can view this overview of High Availability. If you are interested in having your EUM Server run in High Availability, please contact your account representative and our professional services engineers to discuss the available options.  ... View more

When making a connection using HTTPS, either SSL or TLS encrypts the information being sent to and from the EUM server. The information is encrypted using a cipher or encryption key. The type of cipher depends on the cipher suite being used.   Use Google Chrome and the following steps to determine which cipher suite is used to secure the HTTPS connection with the EUM 'adrum' beacons.  Open Google Chrome and launch Chrome developer tools (ALT+CMD+I) by clicking on View > Developer > Developer Tools in the browser toolbar. Load your EUM-instrumented application in the browser. Click the 'Network' tab in Chrome developer tools and use the search bar to look for the beacon request named 'adrum'. Click on the request, then click the "Headers" tab on the right side of the screen. Copy the request URL. Example:  https://eum.server.com:7002/eumcollector/beacons/browser/v1/EUM-AAB-AUA/adrum Open a new window or tab in your browser and paste the request URL. Open Chrome developer tools in the new browser and click on the "Security" tab. Your cipher information is located under "Connection." Example: ... View more

A load balancer is a device that distributes network or application traffic across a number of servers. Load balancers are used to increase capacity and reliability of applications. When properly configured, F5 iRules utilize a scripting syntax which allows the load balancer to intercept, inspect, transform, and direct inbound or outbound application traffic. In the event the application's source is unable to be modified and all other forms of injection have failed or are not applicable (i.e. assisted injection through Java rules for a PHP-based application), clients with a F5 load balancer can request their network security team configure an iRule to intercept an application's response and inject HTML into the page source necessary for enabling EUM. This is similar to the format that manual injection uses, but HTML is inserted into the webserver's response rather than into the original source code. For instructions on how to build, deploy, and test an iRule, we recommend you consult your F5 support team and network security team as they are most knowledgeable and equipped to handle such a request. From an AppDynanics perspective, you must be properly licensed for EUM and have End User Monitoring (EUM) enabled for an application in your AppDynamics controller UI. Clients who have the limited option of injection via F5 iRules have seen success using a template similar to the iRule listed below. Generic F5 iRule Template (requires further customization) when HTTP_REQUEST { # This is the condition for which requests will be matched against if {[HTTP::uri] contains "segment/in/uri"} { set enableEum 1 } else { set enableEum 0 } # Disable the stream filter for client requests as we are only interested in the server response STREAM::disable # LTM does not uncompress response content, so if the server has compression enabled # and it cannot be disabled on the server, we can prevent the server from # sending a compressed response by removing the compression offerings from the client # HTTP::header remove "Accept-Encoding" } when HTTP_RESPONSE { # Disable the stream filter for all server responses STREAM::disable # Inserts the necessary JavaScript for EUM if {($enableEum == 1) && ([HTTP::header "Content-Type"] starts_with "text/html")} { STREAM::expression { @</title>@</title> <script> window["adrum-app-key"] = "AAB-AA-AUA"; window["adrum-start-time"] = new Date().getTime(); </script> <script type="text/javascript" src="http://cdn.appdynamics.com/adrum/adrum-latest.js"></script>@} # Enable the stream filter for this response only STREAM::enable } } How to use this template 1) Matching Condition - The matching condition in your first "if statement." Change this segment in the above template to match a specific piece of your application. In the template we use the application's URI, however, there are other properties of the application which can be matched up (i.e [HTTP::path], [HTTP::host], etc.).  [HTTP::uri] contains "segment/in/uri"   2) Compression - Does your application use compression? If it does, uncomment the following line from the template. HTTP::header remove "Accept-Encoding" If there isn't any compression, then keep the line commented out. # HTTP::header remove "Accept-Encoding"   3) EUM Application Key - What is your EUM Application Key as assigned in your Controller's UI? This can be found by accessing your EUM Application Configuration via the controller UI. The key is typically eight letters long. Change the example key (AAB-AA-AUA) in the above template to your specific application key. window["adrum-app-key"] = "AAB-AA-AUA";   4) JavaScript Agent Location - Where is the JavaScript agent being hosted? The file (adrum.js or adrum-latest.js) will either need to be hosted with your application or can be hosted in our content distribution network (CDN). If you intend to host the file yourself, update the address between the <script> tags of the iRule template (which is pointing the script src to the AppDynamics CDN). http://cdn.appdynamics.com/adrum/adrum-latest.js  5) Other points to consider In some cases the Stream profile must re-enable response rechunking as documented in https://support.f5.com/csp/article/K6422. Although the above script template is typically successful, every client environment is different. Therefore our team recommends that you consult a trained engineer responsible for managing your F5 load balancer. We also highly recommend testing in a sandbox or development environment before deploying any changes to your production environment.  Results  If properly configured, the iRule matches a condition for your application-specific traffic, the load balancer will inject the EUM-specific source into the response received by the browser allowing the Javascript agent to load in the browser, capture EUM data, and send the associated beacons back to the EUM Server. <script> window["adrum-app-key"] = "AAB-AA-AUA"; window["adrum-start-time"] = new Date().getTime(); </script> <script src="https://cdn.appdynamics.com/adrum/adrum-latest.js"></script> ... View more

Users can debug a browser page with EUM instrumented pages using the JavaScript agent (adrum.js). Within the Google Chrome browser, launch developer tools (ALT+CMD+I) by clicking on View > Developer > Developer Tools in the browser toolbar. Add the string ? ADRUM_debug=true to your webpage's URL and hit enter. Example:   http://URL/page/?ADRUM_debug=true Note: if there is an anchor (#) in the URL, add the above parameter string before the anchor.   Example: http://URL/page/?ADRUM_debug=true#afterAnchor   3. In the browser window, generate load on your web application virtual pages. Note: The easiest way to generate load is by clicking the various links within the browser window which point to the different virtual page(s). This allows for the adrum.js JavaScript agent to capture data.   4. Once a load has been generated on the application, type the following into the Javascript console: ADRUM.dumpLog()  *for v4.2.x and earlier try, ADRUM.logMessages.join("\n") Users can then view their Javascript logs in the console and use for debugging purposes (if needed). Related Links: Customize the Javascript agent Browser real user monitoring  ... View more

As of 4.2.x, it is not possible to export a CSV file from the controller UI for all of the servers being monitored.   As a workaround, a user must capture the raw data and format it using Google Chrome browser, a text editor (our team recommends using TextWrangler or BBEdit, but any text editor with "Find and Replace" capability is fine), and your computer's terminal. The following instructions apply to any Unix-based operating system such as Mac OS X.  In Google Chrome, access the server monitoring user interface from the controller UI.   Launch Chrome Developer Tools (ALT+CMD+I) by clicking on View > Developer > Developer Tools in the browser toolbar. Click on the network tab of Developer Tools, then check the box labeled "Preserve Log".  Refresh the controller UI in the browser and network tab will populate with all the page requests. Once the page is fully loaded, search for a particular network request in the following format: https://[CONTROLLER-URL]/controller/sim/v2/user/machines?appIds=&tierIds=&nodeIds=&format=LITE   Double-click on the request to open a new tab with the desired data in a JSON format. Alternatively, you could select the response tab for this specific request to see the JSON data. Copy the JSON data and paste in a text editor. Use "Find and Replace" to change the data into a CSV spreadsheet using the following steps. Find "," and Replace with  "\n,\n" Find },{ and Replace with }\n,\n{\n Find {" and Replace with {\n" Save the file in the text editor as hosts.txt Open a terminal window and run the following command: cat hosts.txt | grep hostId | sed 's/"hostId":"//g' | sed 's/"/,/g' > hosts.csv The resulting hosts.csv file will contain a column of hostIDs from your controller's list of servers. ... View more

Why can't I see EUM license details from the controller's license page? When viewing the Controller's license page, the user is unable to see the EUM license details.  Troubleshooting when the EUM license details don't appear in the Controller's UI Start by investigating the Controller's ability to communicate with and register the EUM portion of the license with the EUM Server. Although the Controller is attempting direct communication with the EUM Server, the Events Service (Analytics Processor) also plays an indirect role in this communication. The EUM Server relies on the Events Service to be running in order to start up. If the Events Service is not running or the EUM Server cannot properly communicate with the Events Service then the EUM Server will eventually fail to start. If the EUM Server fails to start then any connection attempt from the Controller to the EUM Server will likely not succeed. The bottom line is that all three hosts must be in communication for successful EUM license registration to occur and render EUM licensing information on the Controller's license page. Pull the relevant log files In diagnosing a problem like this it is always a good idea to pull all the relevant log files. I've listed the names of each log file is relevant here, and what host it can be found on. On all three hosts, there should be a directory called "logs" which lives inside the home directory for the associated product. Controller - server.log  Events Service - events-service-api-store.log EUM Server - eum-processor.log   Example In this particular case, I was able to find a log entry from the eum-processor.log file which stated there was an error starting the EUM Processor Server. I've highlighted the key elements in the log snippet below which tell us where to begin our investigation: 06 Dec 2016 17:57:34.681 -0800  main                  AD.ALL                    ERROR   |    Error Starting EUM Processor Server  |    java.lang.RuntimeException: java.lang.RuntimeException: bulk update event type=MobileSessionRecord failed!!!  url=http://localhost:9080/v2/events/MobileSessionRecord/_bulk, key=MGE1OT...  |    {"statusCode":401,"code":"Auth.Unauthorized","message":"The supplied auth information is incorrect or not authorized.","developerMessage":""} Since the EUM Server failed to start, the EUM host could not listen on TCP port 7001, therefore preventing successful connections from the Controller host. The other important details in this log entry tell us that, when attempting authorization with the Events Service at the url http://localhost:9080, the supplied auth information is incorrect or not authorized. Now that we have a starting point, we must configure the correct authorization key for the EUM Server. Solution Update the authorization key used by the EUM Server so that it can communicate with the Events Service. Assuming no other issues exist, the EUM Server should be able to start up. Once we can confirm the EUM Server is started we can then confirm the Controller can properly communicate with and register the EUM license details with the EUM Server. How do I find the correct authorization key needed for EUM Server/Event Service communication? The events-service-api-store.properties file in the conf directory of your Events Service installation is where this authorization key is set. In the majority of cases, the authorization key is a randomly generated UUID. The snippet below shows the property where the EUM Server's authorization (access) key is set. ad.accountmanager.key.eum=c9053630-84e4-4b61-9e49-b092b95c9c95 The example value set for the EUM Server is  c9053630-84e4-4b61-9e49-b092b95c9c95 ​. Now that we know the correct key value, we can go to the EUM Server to update the incorrectly set value. How do I set/update the EUM Server's authorization key? In the eum.properties file which resides in the bin directory of your EUM Server's installation, there is a section dedicated to setting up the communication between the EUM Server and the Events Service. The property analytics.accountAccessKey is the one we are interested in. In the sample below, it appears the access key is  1a59d1ac-4c35-4df1-9c5d-5fc191003441 ​, which doesn't match the authorization key  c9053630-84e4-4b61-9e49-b092b95c9c95  in the conf directory of the Events Service installation example above.  # Analytics server properties analytics.accountAccessKey=1a59d1ac-4c35-4df1-9c5d-5fc191003441 Assuming this is the only issue, you can resolve it by updating the analytics.accountAccessKey property in the eum.properties file so that it uses the ad.accountmanager.key.eum property value from the events-service-api-store.properties file. There are a few steps which must take place. Update the analytics.accountAccessKey value ​in the eum.properties file to c9053630-84e4-4b61-9e49-b092b95c9c95 ​. The results of the above steps should show the eum.properties file with the following values: # Analytics server properties analytics.accountAccessKey=c9053630-84e4-4b61-9e49-b092b95c9c95 Please save the eum.properties file. Please attempt to start the EUM Server from the eum-processor directory like so: bin/eum.sh start & We recommend reviewing the latest eum-processor.log file to ensure the EUM Server starts up properly.  Assuming the EUM Server starts properly we should be able to the correct EUM license details from the Controller's license page Related Links: https://docs.appdynamics.com/display/PRO42/Troubleshoot+EUM+Server+Installation https://docs.appdynamics.com/display/PRO42/Install+a+Split+Host+%28Production%29+EUM+Server https://docs.appdynamics.com/display/PRO42/Configure+the+EUM+Server https://docs.appdynamics.com/display/PRO42/Connect+to+the+Events+Service  ... View more

Question: How do I calculate the size of an EUM JavaScript Agent beacon? Solution: Use Chrome Developer tools to capture application traffic (particularly agent beacons) and use the following formula: Formula: Content-Length / 1024 = Size in KB Example HAR File captured from Chrome Developer Tools (please note the output of the HAR file has been truncated):       {         "startedDateTime": "2016-02-01T10:27:51.549Z",         "time": 26.043999998364598,         "request": {           "method": "POST",           "url": "https://col.eum-appdynamics.com/eumcollector/beacons/browser/v1/ZA-AAB-AZA/adrum",.........             { "name": "Content-Length",               "value": "4861"             }           ],           "queryString": [],           "cookies": [],           "headersSize": 496,           "bodySize": 4861,           "postData": {             "mimeType": "text/plain",             "text": {"vr":"4.2.12.0","dt":"R","rg":"0","es":[{"eg":"0","et":0,"eu":"0://1/2/#3","ts":1481639175118,"mc":{"PLT":1463,"FBT":401,"FET":1062,"DRT":899,"PRT":163,"DOM":1300,"ts":1481639175118,"PLC":1},"mx":{"PLT":1447,"FBT":11,"SCT":7,"DLT":0,"TCP":0,"RAT":4,"FET":1436,"DRT":1256,"DDT":1,"DPT":1255,"PRT":180,"DOM":1267,"ts":1481639175118,"PLC":1},"pr":"0://4/5/6/7/8","pl":"AppDynamics","rt":{"v":2,"ic":{"other":1,"script":8,"link":16,"css":5},"it":{"other":1,"script":2,"link":3,"css":4},"rc":{"other":1,"script":8,"css":18,"svg":1,"font":2},"rt":{"other":1,"script":2,"css":3,"svg":4,"font":5},.........}}} Steps: 1) Open a Chrome Browser window with Developer Tools  2) Make sure Developer Tools is recording and begin to simulate some traffic to your application. 3) Click the network tab in Developer Tools and filter the list of request by name. Use the word "adrum" 4) Select one of the requests and expand the Request Headers section 5) Find the value for "Content-Length" 6) From example above you can see the Content-Length is 4861. Plug this value into the formula listed above. 4861/1024 = approximately 4.74 KB ... View more

Description: I am upgrading my 3-node Events Service cluster from version 4.2.1.3 to 4.2.9.2 using the Platform Admin tool and the upgrade fails. How am I supposed to upgrade my cluster? Platform Admin Output: [appdynamics@controller platform_admin]$ bin/platform-admin.sh start-platform-admin Using MySQL configuration file: /opt/AppDynamics/Controller/platform_admin/../db/db.cnf Starting Platform Admin application Waiting for the Platform Admin application to start...... ***** Platform Admin application started on port 9191 ***** [appdynamics@controller platform_admin]$ bin/platform-admin.sh upgrade-events-service Upgrading Events Service cluster. Events Service upgrade failed. Disable Transient Rebalancing failed Background: 1) 4 RHEL Linux hosts (Controller + 3 Events Service Nodes) 2) Successful Controller upgrade to version 4.2.9.2 3) Disabled all firewalls between the Controller and ES Cluster nodes 4) Cluster health check from Platform Admin Tool yields HEALTHY cluster 5) JAVA_HOME variable is properly set on all hosts 6) Java version 1.7.x [appdynamics@controller platform_admin]$ echo $JAVA_HOME /opt/AppDynamics/Controller/jre/ [appdynamics@node01 ~]$ echo $JAVA_HOME /data/AppDynamics/appdynamics/jre/ [appdynamics@node02 ~]$ echo $JAVA_HOME /data/AppDynamics/appdynamics/jre/ [appdynamics@node03 ~]$ echo $JAVA_HOME /data/AppDynamics/appdynamics/jre/ Solution: Upgrade each Events Service node manually instead of using the Platform Admin tool. Please use the following instructions to complete the manual upgrade: https://docs.appdynamics.com/display/PRO42/Upgrade+the+Events+Service#UpgradetheEventsService-UpgradetheEventsService Please note that you will need to manually start the Events Service on each of the nodes prior to managing/monitoring them with the Platform Admin Tool. ... View more

Problem Description: I upgraded EUM/Events/Controller from 4.2.4.1 to 4.2.10.0 but found some discrepancies with EUM. I found some weird app keys in my console. While troubleshooting, I attempted to restart with some new jvm options, but am now getting a new error: 21 Dec 2016 22:41:59.189 +0000 main AD.ALL ERROR  | Error Starting EUM Processor Server  | java.lang.RuntimeException: java.lang.RuntimeException: bulk update event type=MobileSessionRecord failed!!! url=http://appd-events-service-cluster.example.com:9080/v2/events/MobileSessionRecord/_bulk, key=YmNkMz...  | {"statusCode":401,"code":"Role.Unauthorized","message":"The supplied auth information is for a role which does not have access to this resource.","developerMessage":""} I tried uninstalling EUM and Events but I am receiving this error whenever 4.2.10.0 EUM tries to talk to 4.2.10.0 events that was installed with platform-admin. Troubleshooting Steps: 1. Obtain copy of the  eum.properties file off of EUM Server. 2. Obtain copy of events-service-api-store.properties file from Events Service nodes 3. Obtain values associated with the Controller Settings.  appdynamics.analytics.local.store.controller.key , appdynamics.analytics.server.store.controller.key , and appdynamics.es.eum.key from your Controller's admin.jsp page. 4. Confirm that  ad.accountmanager.key.eum is different than ad.accountmanager.key.controller in your events-service-api-store.properties file. Supporting Files:   Solution: 1. Please update ad.accountmanager.key.eum ​ in your events-service-api-store.properties file so that it doesn't match any of ad.accountmanager.key.controller. Changing one character at the end of the GUID should suffice. 2. Please update appdynamics.es.eum.key in the admin.jsp to use the updated GUID in step 1. 3. Please update analytics.accountAccessKey in your eum.properties file to use the updated GUID in step 1. 4. Restart Events Service cluster via Platform Admin 5. Start EUM Server ... View more