Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
02-28-2020
03:41 PM
- edited on
05-14-2020
11:57 PM
by
Claudia.Landiva
The Events Service should have its own Java Agent and Machine Agent.
To monitor the hardware health of the Events Service nodes, this example uses a Machine Agent installation. For more details, see the AppDynamics Machine Agent installation documentation.
Link each Machine Agent with either:
The unique host ID configuration option enables the linking.
Complete the following procedure:
uniqueHostId
value that you configured in the vmoptions
file. For example: -
Dappdynamics.agent.uniqueHostId=EventsService01
<machine-agent-home>\conf\controller-info.xml
such that <unique-host-id>EventsService01</unique-host-id>
corresponds to that value.
/opt/appdynamics/events-service = <Events-Service-Home>
/opt/appdynamics/AppAgent = <AppAgent-Home>
Item |
Example Data |
hostname |
|
port |
|
account name |
|
access key |
|
name of the APM application that monitors the Events Service |
|
controller-info.xml
file.<controller_host>, <controller_port>
, <account_name>
, <access_key>
to AppAgent <AppAgent-Home>/conf/
or the relative directory to be <AppAgent-Home>/conf/controller-info.xml
events-service.vmoptions
file under <Events-Service-Home>/processor/config>
-javaagent:<AppAgent-Home>/javaagent.jar
in the events-service.vmoptions
file./bin/events-service.sh stop
./bin/events-service.sh start -p ./conf/events-service-api-store.properties &
AppAgent
file to access from within the Elasticsearch process. Create the <Events-Service-Home>/conf/elasticsearch.policy
file:grant codeBase "file:<AppAgent-Home>/-”
{
Permission java.security.AllPermission;
};
<Events-Service-Home>/conf/elasticsearch.vmoptions
file.<Events-Service-Home>/conf/events-service.vmoptions
filevmoptions
file for Elasticsearch by editing the <Events-Service-Home>/conf/events-service-api-store.properties
property as follows:ad.es.jvm.options.name=elasticsearch.vmoptions
elasticsearch.vmoptions file
.-javaagent:<AppAgent-Home>/javaagent.jar
-Dappdynamics.socket.collection.bci.enable=true
-Dappdynamics.agent.tierName=EventsService-Elasticsearch
-Dappdynamics.agent.nodeName=Elasticsearch01
-Djava.security.policy=<Events-Service-Home>/conf/elasticsearch.policy
-Djava.security.policy
.-javaagent:<AppAgent-Home>/javaagent.jar
-Dappdynamics.socket.collection.bci.enable=true
-Dappdynamics.agent.uniqueHostId=EventsService01
-Dappdynamics.agent.tierName=EventsService-API
-Dappdynamics.agent.nodeName=API01
bin/events-service.sh stop
bin/events-service.sh start -p conf/events-service-api-store.properties &
#[1] bin/events-service.sh start -p conf/events-service-api-store.properties disown %1
View the logs from their typical locations, shown in the following table:
Log |
Location |
API store |
|
Elasticsearch |
|
Java Application Agent |
|
Run troubleshooting commands when you encounter common problems.
Problem |
Command |
When Elasticsearch is starting, you see vm.max_map_count errors |
|
If the system starts running out of descriptors, check /etc/security/limits.conf |
Substitute the name of the user running Elasticsearch for the asterisk ("*")
|
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form