What JVM version are you using?  The symptoms look similar to those described here. ... View more

The basic approach you describe should be fine, but you need to set the details the agent will use to connect to the controller. If you have not somehow editted these into the controller-info.xml in your dockerfile, you will need to pass additional system properties or environment variables to your container. To verify that this is indeed the issue, you can look in the agent log file within the container. Also, note that node name need to be unique within a tier.  You may want to look at auto node naming. ... View more

It looks as if you may have the machine agent in "server visibility" mode wthout a server visibility license available. You can see how to turn server visibility on (or by inference, off) here. ... View more

I have not tested, but you could try a rule which matches /pages/cases and configure the following split: Apply a custom expression on HTPServletRequest getQueryString().matches(\.*BehaviorListener\.\\d+-caseOverviewForm-caseOverviewResultPanel-casesBody-cases-\\d+-specialAttentionCell\.*) If my regex-fu is right, this will result in 2 BTs called name.true and name.false where name.true is the class of BT you're trying to get at ... View more

So is the problem statement that you want a BT for HTTP requests that hit the /pages/cases URL ONLY if a parameter of the form you provided exists? ... View more

What Business Transactions would you like to be tracking as a result of the rule you're trying to create and the example links you provided? ... View more

Since the majority of IIB is implemented in native code, not java, it is not possible to instrument it with the java agent, I'm afraid. Have you looked at the IIB machine agent extension? ... View more

Hippolyte, Can you please elaborate on what you mean by "custom application features"?  Can you provide an exampe of such a feature in your context; how are your features identified? I am pretty certain the answer will be yes, but I want to make sure I am answering the right question. Warm regards, Peter. ... View more

Historical nodes do not disappear until the node retention period has expired, as documented here: https://docs.appdynamics.com/display/PRO43/Historical+and+Disconnected+Nodes ... View more

Could you post the full agent logs? It may be easier to handle this through a support ticket. ... View more

Note the underlying issue here is fixed in v4.2.4 and v4.3 v4.3.8.7 and v4.4+ of the agent.  Can I ask what version you are running? Also, in v4.3.4+ internal agent errors are no longer counted against the application totals. ... View more

Eric, The way the controller handles historical nodes is documented here: https://docs.appdynamics.com/display/PRO43/Historical+and+Disconnected+Nodes This node property was introduced in v3.7 I will file a ticket to consolidate this information and mention the node property on the properties page. Warm regards, Peter ... View more

The event data stored by analytics is not held in MySQL, so you need not worry on that front. Based on your other comments though, I am just not convinced that trying to implement your rules within AppDynamics is the correct architectural approach to solve this specific problem Maybe you could apply your rules in code and publish the failure count via a JMX MBean?  You could use AppD to monitor the MBean and alert on the breaches that way? ... View more

So presumably, you have a regular expression (referred to as 'regular-expression' below) that you would run on a string field, and when it matches that is indicative of a mention of religion. On that assumption, if you collected transaction analytics data from all transactions that could contain mention of religion, you could then use ADQL to identify the offending ones.  e.g. SELECT count * FROM transactions WHERE segments.userData.inputText REGEXP('regular-expression') You could use this query to create a metric that you could alert on if non zero using a health rule in the usual way. This would probably be the best way to approach your problem using the AppDynamics platform. ... View more

OK, can you give an example of some inputs and a rule? And what should happen if the rule is violated?  SImply an alert, or should the application behaviour change in case of a violation? ... View more

This should be possible using our analytics product.  Can you give an example of a concrete use-case you want to implement?  If so, I can try and point out the right set of platform features to use to achieve it. ... View more

Srinand, The SDK is part of the agent, so there is no additional install necessary to use its APIs If you incorporate the code from the sample in the doc page you linked into your application, it should run fine with no need for additional dependencies on the classpath, so long as the agent is loaded into the JVM with -javaagent Once your application has parsed the HTTP request and has the data you wish to collect in variables, it is a simple matter to add this data to snapshots and/or transaction analytics data using the addSnapshotData API as illustrated. I hope this helps? Warm regards, Peter ... View more

I'm afraid it is not possible to selectively ignore exceptions based on the BT context at this time. ... View more

It seems that the out of the box instrumentation is not following your transactions end to end in this case. This could either be because the agent is missing a thread handoff within a process, or an inter-process handoff, either at the producer or consumer side. Since your inter-process handoffs are JMS, the producer calls (JMS send calls) are likely to be instrumented, meaning the agent is probably either missing your downstream JMS consumers, or some internal thread handoffs. Thread handoffs within Camel often need  <include filter-type="STARTSWITH" filter-value="org.apache.camel/"/>" added to the <fork-config> section in the agent's app-agent-config.xml; you could try and add this and see if this solves the issue. If not, the best bet is to work through this with an engineer via a support ticket.  It will be helpful if you attach agent debug logs from the upstream and downstream systems that should correlate.  Collect DEBUG level logs on the com.singularity package while some load that should be correlated is run. ... View more

Do you see the JVM reporting if you look at the 'Tiers and Nodes' dashboard within your application? Is there any load running though your application? Given that you're running in jetty, I assume your load is handled by servlets.  Is that true? If you see the node and there is load running then it is possible that you need to configure non-standard entry points, this is very likely to be necessary if your application is not implemented using the servlet API ... View more

Does the user-id running jetty have permission to write to the AGENTDIR/v4.x.y.z/logs/ directory? What happens if you log in as this user and run: java -javaagent:AGENTDIR/javaagent.jar -Dappdynamics.agent.nodeName=test -Dappdynamics.agent.tierName=test -Dappdynamics.agent.applicationName=test -version ... View more

What would you want to happen in your application if one of your validations failed? ... View more