The most common cause of the "machine agent" appearing in the Controller UI but no .NET node appearing in the Flow Map is that no Business Transaction traffic executed on the node in the selected time range.
If this is IIS, make sure that there is HTTP traffic running through it.
In the case where the .NET application executes logic that's not triggered by web traffic, it's typically necessary to define one or more entry points for custom Business Transactions.
Regard,
Brian Wheeldon
I have several windows services that I am trying to instrument, but cant seem to figure out how to. I have read the available documentation, but still not clear. All 13 windows services use the same .exe file, which I have defined in the config file. In the AppD UI, I all see a Machine Agent Tier(which isnt the name i want for the tier anyway), but nothing is being instrumented.
Here's what the config file looks like - what am i missing? How do I name the tier(in the UI) as SIKOMS Windows Service?
<?xml version="1.0" encoding="utf-8"?>
<appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<controller host="xxx" port="xxx" ssl="true" enable_tls12="true">
<application name="SIKOMS" />
<account name="xxx" password="xxx" />
<proxy host="xxx="xxx" />
</controller>
<machine-agent />
<app-agents>
<IIS>
<applications>
<application path="/" site="Default Web Site">
<tier name="" />
</application>
</applications>
</IIS>
<standalone-applications>
<standalone-application executable="D:\sikoms\applications\SIKWindowsServices\SIKWindowsServices.exe" command-line="-x">
<tier name="SIKOMS Windows Service" />
</standalone-application>
</standalone-applications>
</app-agents>
</appdynamics-agent>
Any help would be greatly appreciated.
Hi Raymond,
Sorry to say that is yet to be fixed and we confirm this is in pipeline but no ETA on fix version as of now. Hope that answers your query.
This is documented as known issues at:
We request you to try Clyde suggestion in above post in logging changes to see if it helps for the interim, Also check if we are doing REST API automation calls:
<Controller_dir>/appserver/glassfish/domains/domain1/config/logging
com.singularity.ee.controller.beans.model.LDAPAuth
Hello,
It's been over a year since we updated our agents installed on our Windows Tomcat instances. Which agent I need to download to get the most current version?
Contents of the currently installed appagent.jar MANIFEST.MF file:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.8.2
Created-By: 1.6.0_39-b04 (Sun Microsystems Inc.)
Implementation-Vendor: AppDynamics Inc.
Implementation-Version: Server Agent v3.8.4.0 GA #2014-06-30_13-26-26
r5dc2d8d219673e698b0b455657ac469bc8b59337 4-3.8.4.next
Contents of the currently install javaagent.jar MANIFEST.MF file:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.8.2
Created-By: 1.6.0_39-b04 (Sun Microsystems Inc.)
Implementation-Vendor: Appdynamics Inc
Implementation-Version: Server Agent v3.8.4.0 GA Build Date 2014-06-30
13:33:39
Premain-Class: com.singularity.ee.agent.appagent.AgentEntryPoint
Main-Class: com.singularity.ee.agent.appagent.AgentEntryPoint
Agent-Class: com.singularity.ee.agent.appagent.AgentEntryPoint
Boot-Class-Path: javaagent.jar
Can-Redefine-Classes: true
Can-Retransform-Classes: true
Any help is appreciated, thank you!
Hi!
i have issue custom event by create policy and assign action alert call batch file write log and custom event idenfy type name custom and properties serverity="ERROR" and Type=CUSTOM, send url request from web pages rul http://localhost:8293/machineagent/event?type=error&summary=TEST009 and view event custom show on dashboard but don't action alert write log file.
picture1 = Policy
picture2 = send url request from web pages rul http://localhost:8293/machineagent/event?type=error&summary=TEST009
Thank You.
Hi , I have done basic set up of appDynamic for Vert.X application and when i starting the application , its showing the "Started AppDynamics Java Agent Successfully."But i am not able to see the application node in dash board of appDynamic .
I have configured all of the things which mentioned at https://docs.appdynamics.com/display/PRO42/Use+Environment+Variables+for+Java+Agent+Settings
Clould you please tell me what i am missing here apart from here ?
Install Directory resolved to[/home/ec2-user/AppDynamics-Java-Agents/appDynamic]
Full Agent Registration Info Resolver found system property [appdynamics.agent.applicationName] for application name [Content_Repo]
Full Agent Registration Info Resolver using selfService [false]
Full Agent Registration Info Resolver using selfService [false]
Full Agent Registration Info Resolver using application name [Content_Repo]
Full Agent Registration Info Resolver using tier name [Undefined_Tier]
Full Agent Registration Info Resolver using node name [Undefined_Node]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver is running
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver found system property [appdynamics.agent.applicationName] for application name [Content_Repo]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using selfService [false]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using application name [Content_Repo]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using tier name [Undefined_Tier]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Full Agent Registration Info Resolver using node name [Undefined_Node]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[DEBUG]: AgentInstallManager - Full Agent Registration Info Resolver finished running
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Agent runtime directory set to [/home/ec2-user/AppDynamics-Java-Agents/appDynamic/ver4.2.3.0]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: AgentInstallManager - Agent node directory set to [Undefined_Node]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: JavaAgent - Using Java Agent Version [Server Agent v4.2.3.0 GA #11860 rb5a53a88334f0663d0b2eaf32315abd0f9dbabb4 38-4.2.3.next-build]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: JavaAgent - Running IBM Java Agent [No]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: JavaAgent - Java Agent Directory [/home/ec2-user/AppDynamics-Java-Agents/appDynamic/ver4.2.3.0]
[Thread-0] Fri Sep 02 06:54:33 EDT 2016[INFO]: JavaAgent - Java Agent AppAgent directory [/home/ec2-user/AppDynamics-Java-Agents/appDynamic/ver4.2.3.0]
Agent Logging Directory [/home/ec2-user/AppDynamics-Java-Agents/appDynamic/ver4.2.3.0/logs/Undefined_Node]
Running obfuscated agent
Started AppDynamics Java Agent Successfully.
Hi Vikas,
As noted in the link you cited, Hystrix monitoring is supported out of the box.
In the event that you are missing a downstream call that's launched from a Hystrix thread, you should be able to expose that thread's activity by modifying:
$AGENT_HOME/<version>/conf/app-agent-config.xml under section <fork-config>:
<include filter-type="STARTSWITH" filter-value="com.netflix.hystrix/"/>
<exclude filter-type="STARTSWITH" filter-value="com.netflix.hystrix.strategy.properties.HystrixPropertiesChainedArchaiusProperty"/>
<exclude filter-type="STARTSWITH" filter-value="com.netflix.hystrix.HystrixCommandProperties"/>
Regards,
Brian Wheeldon
Hi,
The sintax is right, you need to take care of the command-line attribute:
<standalone-application executable="D:\sikoms\applications\SIKWindowsServi
You need to provide de attribute to distinguish between different services provided by the same application executable, in the same path. If your services are in different paths, do not include command-line.
As the docs says, run the following from an elevated rights cmd.exe:
tasklist /m "mscor*"
Verify your services are in the list. If not, they aren't .NET services, so they couldn't be instrumented.
Then take a look at the command line of the service (using services.msc) and complete the entry in config.xml. Restart the AppDyn Coordinator service and the service to be instrumented. Wait 1, 2 minutes to the controller to get updated, your new tier is created and visible on the GUI.
An example of multiple services in one tier, with different paths:
<standalone-applications><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR2\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR3\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR4\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application></standalone-applications>
Your last resort is looking at the agent log, it will tell you what's going on inside it.
Hope it helps, regards,
Luis
Hi,
Before updating agents, verify your controller version. In AppDynamics the controller should have the major version, every agent should have an equual/lower version. The version is visible in the lower side of the logon screen:
or with a browser/curl you could read the server status and your current version:
curl http://controller-ip:8090/controller/rest/serverstatus<?xml version="1.0" encoding="UTF-8"?><serverstatus vendorid="" version="1"><available>true</available><serverid></serverid><serverinfo><vendorname>AppDynamics</vendorname><productname>AppDynamics Application Performance Management</productname><serverversion>004-002-005-001</serverversion><implementationVersion>Controller v4.2.5.1 Build 37-4.2.5.next-build Commit 03b1074a2cf7999047b67187eca7fbb54d1068bb</implementationVersion></serverinfo><startupTimeInSeconds>61</startupTimeInSeconds>
If you're behind the latest version, my recommendation is to upgrade the controller. Go to http://download.appdynamics.com/ and get the latest versions (4.2.5.2) . Controller upgrade is easy, provided you have a backup, see https://docs.appdynamics.com/display/PRO42/Upgrade+the+Controller.
After upgrading, upgrade the agents downloading the new version, copy configuration in controller-info.xml and restart them. Keep in mind the agents from version 4.1 & up require you provide account-name and account-access-key in controller-info.xml or in the command line.
Hope it helps, regards,
Luis
Hi,
Are you in Java or .NET ?. A method invocation data collector (MIDC) could help.
Do you have access to the WS client code ?. If yes, you're on the right path, look at the code and locate the service method and its parameters.
Then create a new MIDC, describe the class, method and parameters in the dialog (Configuration/Data Collectors). Don´t forget to target the MIDC to new transactions and existing ones. Save your changes, and wait for new snapshots.
You could also start a new diagnostics session on the BT(s) that use the method, to verify your setup is right besides the thresholds of slow/very slow.
Hope it helps, regards,
Luis
Hi,
Did you look at the Tiers & Nodes screen ?. Your application was created, now you have to name your tier & node. Please confirm they are there. If not, share with the community your agent*.log.
Hope it helps (if so click on kudos).
Regards,
Luis
Hi,
It was a full or partial snapshot ?. If partial, it's the answer. Partial snapshots only caught the latest calls, besides AppDynamics show you the entire call duration causing the snapshot. May be a diagnostics session on the business transaction could help you isolate the problem.
Hope it helps, if so click on kudo.
Regards,
Luis
Hi,
curl is your way. Other option is using the Python REST SDK, https://github.com/tradel/AppDynamicsREST, and the Java flavor in https://github.com/Appdynamics/RestMetricQueries
Since usually we feed data from AppDynamics to view/analyze in other platforms like ELK (Elastic/Logstash/Kibana), the logstash http poller is our best friend, https://www.elastic.co/blog/introducing-logstash-http-poller.
Hope it helps, regards,
Luis
Thank you Luis for the the kind reply,
Yes the nodes have been created but the metrics are not coming for the vert.x application and for jar application i am getting the metrics.
Both are running using the same app dynamic java agent . I have attached the vert.x application's app dynamic agent logs here and let me know if you need any other information .
Could you please help me out for getting the metrix for vert.x application as well.
Thanks in advance,
Praveen
I am just trying to install the Agent and get it connected to Controller. Unfortunately, the step where we can Test the Controller Connection fails. What should I be entering for "Account Access Key" in the .Net Configuration window?
Do i need to enable "Enable SSL" ?
I am getting this error when "Enable SSL" is turned ON
Controller communication failed. Details: The operation has timed out
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level.
If I turn that OFF, I get this error.
Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Can someone help please?
Never mind, I was able to figure this out.
I am trying to monitor IIS Connection Pool statistics. So wanted to add the Windows Performance Counters using App Dynamics Extension Manager,
I am having two issues.
1. Not able to install "AppDynamics Extension Service", attaching the screen shot of the error message.
2. AppDynamics Extension Performance Counter Configuation - Not able to get any configuraton for .NET Data Provider for Oracle. When I select that option I am not getting any Performance Counter Name to select. I am attaching screen shot of this as well.
Any help on this greatly appreciated.
I got this working by following a similar set of instructions for New Relic from https://dzone.com/articles/including-java-agent
In summary, you need to include the agent with the Spring Boot application (I imported it into my local Maven repository as it isn't registered in Maven Central) and register the Premain-Class as the snippet from my pom.xml shows.
<profile><id>appdynamics</id><dependencies><dependency><groupId>org.springframework.boot</groupId><artifactId>spring-boot-starter-web</artifactId></dependency><dependency><groupId>com.appdynamics</groupId><artifactId>appdynamics-agent</artifactId><version>${appdynamics-version}</version></dependency></dependencies><build><plugins><plugin><groupId>org.springframework.boot</groupId><artifactId>spring-boot-maven-plugin</artifactId></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-dependency-plugin</artifactId><version>2.10</version><executions><execution><phase>prepare-package</phase><goals><goal>unpack-dependencies</goal></goals><configuration><includeArtifactIds>appdynamics-agent</includeArtifactIds><outputDirectory>${project.build.outputDirectory}</outputDirectory></configuration></execution></executions></plugin><plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-jar-plugin</artifactId><version>2.5</version><configuration><archive><manifestEntries><Premain-Class>com.singularity.ee.agent.appagent.AgentEntryPoint</Premain-Class><Can-Redefine-Classes>true</Can-Redefine-Classes><Can-Retransform-Classes>true</Can-Retransform-Classes></manifestEntries></archive></configuration></plugin><plugin><groupId>org.springframework.boot</groupId><artifactId>spring-boot-maven-plugin</artifactId><configuration>
<mainClass>YOUR_SPRING_BOOT_MAIN_CLASS_IN_HERE</mainClass></configuration></plugin></plugins></build></profile>
Once the JAR is built, add the javaagent in the usual way, it'll still pickup the configuration from the agent installation directory.
I'm getting the same error in on-premise trial. Could you please help me to get rid of it? Thanks.