Discussion Feed

Question What if you see a case using EUM where you are not seeing all the expected Pages/Ajax requests?    For example, you observe that the Pages/Ajax grid only shows a few requests, even though in the Browser snapshots view you can see many more types.   Answer   Check that your search filters are not restricting what you see.   ... View more

Question How does the priority of Custom Pages (Web EUEM/Browser RUM) and business transaction naming work?    Answer The priority schemes are different in these two cases. For business transactions, the higher number is the higher priority whereas for EUM page naming the lower number is the higher priority. ... View more

This may indicate that the agents are not correctly configured. Begin troubleshooting by looking at the server.log file. All log files for Controller are located in the <Controller_Installation_Directory>/logs folder.   Error Message Solution Error receiving metrics (node not properly modeled yet: Could not find component for node: This error means the app agent tried to upload metric data for a specific node, but the node does not belong to any tier. Nodes must belong to tiers and these tiers must belong to a business application in order to receive metric data for that node. See AppDynamics Concepts. Received Metric Registration request for a machine that is NOT registered to any nodes. Sending back null! This error indicates that the Controller received a registration request for metrics for a Machine Agent that listed a machine ID not yet associated with any node. Configure the Machine Agent to associate with the correct application, tier, and node. See Install the Standalone Machine Agent. Agent upload blocked, as its reporting a time well into the future.  The App Agents attempt to report metric data using Controller time. The agents retrieve the time from the Controller every five minutes and report times using a skew of the local machine time, if different. If for some reason the App Agent reports metrics that are time-stamped ahead of the Controller time, the Controller rejects the metrics. To avoid this event, ensure that the system times for the machine on which the Controller is running and the machines for the app agents are in synchronization.   ... View more

Note: All SAAS customers are required to be on 4.4.1+ for GDPR compliance.     Issue  Timeout error while installing Controller v4.3.x on-premises.   Solution If you encounter this issue, try increasing the timeout period. Pass a custom timeout value as a command-line argument to the installer in the following format:   -Vad-timeout-in-min=<timeout>   The ad-timeout-in-min value sets the timeout for both starting and stopping the Controller processes. If you are performing a silent install with the response file, add the ad-timeout-in-min parameter to the installation response file with values for the new timeout periods.   Background Timeout errors typically occur when the startup time exceeds the default startup timeout period. While installing the Controller, the installer attempts to start up the Controller application server and database. At first database startup, the installer attempts to create the database schema, tables, and other artifacts needed by the Controller. By default, the installer waits 45 minutes for the app server or database to start. When installing a medium or large profile Controller or into certain types of environments such as virtual machines, the time it takes to start up the system can exceed the default startup timeout period. In this event, the installer aborts the installation and presents an error message indicating that the Controller could not be started in the allotted timeout window.   Note: Controllers v4.4.x and higher that are installed with Enterprise Console do not experience this error. The Enterprise Console has a longer default timeout period of 2 hours. The timeout parameter is therefore no longer valid since the Controller is installed through the Enterprise Console starting v4.4.x.   ... View more

This article describes how policies and health rules behave depending on which entities/objects are used in the configuration.   You can specify affected entities, such as nodes and tiers, in both Health rules and policies. It is important to understand how various combinations of "affected entity" selections affect the overall policy behavior.   Here are some examples to illustrate the interactions.   Health Rule Examples Health- Rule-1 (HR1) specifies a health rule violation (HRV) on Tier-1 when metric-1 > 0. Health-Rule-2 (HR2) specifies a HRV on all nodes in Tier-1 when metric-1 > 0. Health-Rule-3 (HR3) specifes a HRV on any node in Tier-1 when metric-1 > 0. When the policy/health rule engine detects that metric-1 is greater than 0 for one of these health rules, the resulting events are different for each combination as shown in this table:   Health Rule Example Affected Entity Metric Resulting Events when metric-1 > 0 HR1 Tier-1 metric-1 > 0 1 HRV event for the tier only. HR2 all nodes in Tier-1  metric-1 > 0 1 HRV for each violating node in the tier. No HRV event for the tier. HR3 any node in Tier-1 metric-1 > 0 A single HRV event for the tier and all violating nodes in the tier   Policy Examples When you configure your alerting policies  based on the above health rules, the corresponding policies will fire alerts as follows: Policy Example Affected Object Result Policy-1 Tier policy fires the alert for HR1 Policy-2 node policy fires the alert for HR2 or HR3   This behavior is by design and provides flexibility for deciding when alerts are needed. For, example what does it mean for a tier to be unhealthy? Depending on the specific metric that is used, you can decide the tier is unhealthy even if all the nodes are healthy. Here are some examples of using different metrics with each type of health rule:   HR1 Metric-1 = active database connections > X (some number). You would use this configuration because you are concerned with the total number of connections for the tier not the # of connections for each node. HR2 Metric-1 = memory utilization % > 80%. Here you want to know if the HRV occurs on any node because it may indicate a problem on that specific node, although the others are healthy. HR3 Metric-1 = calls per minute > X. Say you are using a load balancer in round robin fashion. If the load on one node is higher than the others, you might have a problem with the load balancer, so you would want to alert if any node has a HRV.   Policy Matching Combination Examples This table specifies the result of using different combinations of event type, health rules, and objects in the Policy configuration.    Policy Configuration Example Event Type Health Rule Object specified in Policy Result - Policy Fires 1 Health Rule Violation Started - Critical Slow transaction * any *any Policy fires when any health rule violates at the critical level or any transaction is slow for the application. In other words, any slow transaction on any tier or any health rule violation at the critical threshold causes this policy to fire. 2 Health Rule Violation Started - Critical Slow transaction Health Rule-1 Health Rule-2 *any Policy fires for a slow transaction or for a violation of Health Rule-1 or Health Rule-2 for any object across the application. This policy example fires even if the object specified in the health rule configuration is a specific tier or node or set of nodes. The "Any Object" configuration in the policy causes the policy engine to ignore the objects specified in Health Rule-1 and Health Rule-2. 3 Health Rule Violation Started - Critical Slow transaction *any Tier 1 This policy fires for any slow transaction on Tier 1 or for any Health Rule Violation Started - Critical event on tier 1 for any health rule. 4 Health Rule Violation Started - Critical Slow transaction Health Rule-1 Health Rule-2 Tier 1 This policy fires for a slow transaction or any Health Rule Violation Started - Critical event on tier 1 for Health Rule-1 or Health Rule-2. Note, if you were to configure Health Rule-1 or Health Rule-2 for any node in Tier 1 this policy would never fire. ... View more

Question How can I use AppD4DB to alert if a database instance goes down? This is not for when an OS goes down. We want to know if SQL Server crashes, for example.   Answer Set up a Custom SQL Alert like this:     If the SQL Connection is successful and it can run a query then it will return a 1. If it fails then you will get an email containing the exception.   For example, here is the alert history:   This is the contents of the default alert:   ... View more

Symptoms You encounter an issue with the POST to /eumcollector/beacons.   JS error is "Request header field X-TS-AJAX-Request is not allowed by Access-Control-Allow-Headers". Diagnosis Research revealed that Access-Control-Allow-Headers is a CORS property.   For this scenario, there were two app environments: APP1 and APP2. EUM data was being seen in APP1 but not in APP2. Verified that the adrum.js and adrum-ext.[ver].js match except for app key. Both apps were hitting the same load balancer, F5. Only APP2 has SSO enabled via WebSphere + Active Directory.   Solution Turns out that this was an F5 configuration error, even though "everything's the same for both environments" with regard to F5.   Customer was running the Application Security Manager module on F5. It's supposed to be transparent, not do anything. The F5 team disabled the ASM view on APP2 because it was disabled on APP1. This fixed the CORS problem affecting the call to /eumcollector/beacons. ... View more

You can assign multiple MIDCs to the same class and method or multiple information points to the same class and method. However, y ou cannot assign more than one type of interceptor to the same class and method in a .NET application.   For example, defining an information point or a method invocation data collector (MIDC) on the same class and method that is already instrumented as an entry or exit point .       ... View more

JDBC connection pool metrics are not configured out-of-the-box for GlassFish.   To configure them, uncomment the JDBC connection pool section and provide the relevant information in the following file:   <agent_home>/ver<version_number>/conf/jmx/servers/glassfish-v2-jmx-config.xml   Uncomment the following section and follow the instructions provided in the file. <!-- The following config can be uncommented to monitor glassfish JDBC connection pool. Please set the name of the connection pool (not the datasource name) and enable monitoring for the JDBC Pools on glassfish admin console. --> <!-- <metric mbean-name-pattern="com.sun.appserv:type=jdbc-connection-pool,category=monitor,name=<set the name of pool>,*" category="JDBC Connection Pools"> <attribute-counter-mappings> <attribute-counter-mapping> <attribute-name>numconnused-current</attribute-name> <counter-name>Connections In Use</counter-name> <counter-type>average</counter-type> <time-rollup-type>average</time-rollup-type> <cluster-rollup-type>individual</cluster-rollup-type> </attribute-counter-mapping> <attribute-counter-mapping> <attribute-name>numconnused-highwatermark</attribute-name> <counter-name>Max Connections Used</counter-name> <counter-type>observation</counter-type> <time-rollup-type>average</time-rollup-type> <cluster-rollup-type>individual</cluster-rollup-type> </attribute-counter-mapping> <attribute-counter-mapping> <attribute-name>numpotentialconnleak-count</attribute-name> <counter-name>Potential Leaks</counter-name> <counter-type>observation</counter-type> <time-rollup-type>average</time-rollup-type> <cluster-rollup-type>individual</cluster-rollup-type> </attribute-counter-mapping> <attribute-counter-mapping> <attribute-name>averageconnwaittime-count</attribute-name> <counter-name>Avg Wait Time Millis</counter-name> <counter-type>observation</counter-type> <time-rollup-type>average</time-rollup-type> <cluster-rollup-type>individual</cluster-rollup-type> </attribute-counter-mapping> <attribute-counter-mapping> <attribute-name>waitqueuelength-count</attribute-name> <counter-name>Current Wait Queue Length</counter-name> <counter-type>observation</counter-type> <time-rollup-type>average</time-rollup-type> <cluster-rollup-type>individual</cluster-rollup-type> </attribute-counter-mapping> </attribute-counter-mappings> </metric> ... View more

In some situations, JMX metrics from GlassFish are not reported. Also, some metrics may not be enabled by default. Try this solution:   Confirm that JMX monitoring is enabled in the GlassFish server.  Navigate to the  <agent_home>/ver<version_number>/conf/jmx/ directory.  Copy the attached XML into an mbean-servers.xml file in that directory.  You should see a new JMX node in the metrics tree. ... View more