Discussion Feed

As of version 4.3, the admin information URL for on-premise EUM Servers ( http://eum-host:port/eumaggregator/info ) is disabled by default for security reasons.   Users who wish to access this information can start the EUM Server with dev mode by adding the -Deumcloud.mode=DEV JVM parameter to the EUM processor in the JAVA_OPTS startup script.   Example:   Add the following to the  bin/eum-processor(.bat for Windows) DEFAULT_JVM_OPTS=“\ \“-server\” \ \“-XX:+UseConcMarkSweepGC\” \ \“-XX:CMSInitiatingOccupancyFraction=50\” \ \“-XX:+HeapDumpOnOutOfMemoryError\” \ \“-XX:NewRatio=1\” \ \“-Xms1024m\” \“-Xmx4096m\” \ \“-DEUM_COMPONENT=processor\” \ \“-Deumcloud.mode=DEV\” \ \“-Dlogback.configurationFile=bin/logback.xml\” \ \“-Dcom.mchange.v2.c3p0.cfg.xml=bin/c3p0.xml\“   Then restart the EUM Server in order to access the admin information URL. ... View more

When migrating an EUM Server from Windows to Linux, a user might incorrectly assume that the Controller is also migrated, which takes care of the MySQL backup. The  Controller database and the EUM Processor store must be migrated separately.   Users should always do a fresh install of the EUM server on the new machine, and then check the host dependent settings.   Example: In the eum.properties file, modify the following Controller host IP/name properties:   "onprem.dbHost" : This is the controller-db host detail, port 3388 remains unchanged. "analytics.serverHost"* Change this property if you are using the local Events Service that comes embedded inside the Controller, not a standalone installation of the Events Service.   Lastly, users should copy the data from the  ../store directory from the  old machine to the new one. Dependencies on the Events Service and Controller will remain intact.   Step-by-step instructions:   Backup the EUM  ..\store  directory on your Windows machine. Backup the Controller MySQL database on Windows, and restore the db backup on the Linux machine. Install EUM Server on the Linux machine.  Configure all the components to the Linux machine after installation. Change the Event Service and EUM hostnames in the Controller config. Change the IP address in the Controller config.  Restore the directory ..\store backup on the Linux machine.     Related Links: Users on 4.3.x (or earlier version) migrate EUM database on Controller host to 4.4.x EUM host Migrate the Controller EUM Server installation     Published 6/23/2017 ... View more

Symptoms After configuring analytics on the Machine Agent ( monitor.xml and analytics-agent.properties file) for the first time, you see following warning message in logs as you activate the functionality from UI and  no metrics are visible through analytics searches.   [2016-11-17T12:56:42,195+01:00] [WARN ] [pipeline-thread-11 (bt-publish-3)] [c.a.a.a.p.e.EventServicePublishStage] This message was throttled [47] times: Transient error encountered due to the following cause: [Message could not be delivered because the REST resource rejected it]  com.appdynamics.analytics.shared.rest.exceptions.NotAcceptableRestException: Event type [biz_txn_v1] for account [customer1_0fcad495-5e0b-44d7-88eb- 48a7de7025b4] expired on [2016-09-30T23:59:00.000Z]   Diagnosis Since this is a new setup run analytics healthchecks to verify that the Analytics Server and agent are up and running:    http://<analytics_agent_host>:9091/healthcheck?pretty=true http://<event_service_host>:9081/healthcheck?pretty=true   Check the license file to verify units and expiry is correct as is showing in the License screen on UI.   Next, check the Controller db and verify license details are correctly stored in there. Following query should help fetch the details:    mysql> select * from license_module_property where license_module_type='transaction-analytics';  +------------+-----------------------+--------------------------------+----------------+  | account_id | license_module_type | property_name | property_value |  +------------+-----------------------+--------------------------------+----------------+  | 2 | transaction-analytics | data-retention-period | 90 |  | 2 | transaction-analytics | edition | PRO |  | 2 | transaction-analytics | expiry-date | 1506927600000 |  | 2 | transaction-analytics | licensing-model | FIXED |  | 2 | transaction-analytics | maximum-allowed-licenses | 10 |  | 2 | transaction-analytics | number-of-provisioned-licenses | 10 |  +------------+-----------------------+--------------------------------+----------------+  6 rows in set (0.00 sec)     Note:  {mysql> select * from license_module_property where license_module_type='transaction-analytics*'; } In this query, you can use transaction/log/browser analytics based on whatever needs to be checked for your case, rest of the query will remain intact.    Check and confirm that the Event Service end point, access key and global account name are correct in the property file.  Verify the same via the admin UI and the Event Service properties file.   If you try to start Analytics Agent manually  using command, still you see this warning message.   Solution Because this happens when  Controller's new license hasn't synced with the ES, it  kept the old license expiring date even after updating it;   To resolve this issue, you would have  to blow empty the ES cluster and R e-install the event service. Better redownload it too then re install (preferably using   Platform Administration if applicable). ... View more