cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Deepanshu.Grover
AppDynamics Team (Retired)

Symptoms

Inside Analytics Advanced search using ADQL when a metric is created on search output, the metric data is not changed when the search query is changed hence reports different data.

 

For example: Making a change to an Advanced Transaction Analytics Saved Search which had a saved Metric, and the Metric continued to return results of the old query.

Specifically, going from a broad search:

SELECT count(*) FROM bt_resp_time_4 WHERE Datacenter = 'XYZ' AND CustomerName = 'XYZ' AND PassFail = 'Pass'


 to a more exclusive one:

SELECT count(*) FROM bt_resp_time_4 WHERE Datacenter = 'XYZ' AND CustomerName = 'XYZ' AND ApplicationName = 'Web Store' AND BT = 'Login' AND PassFail = 'Pass'


The results went from ~200 requests to ~20 per minute on the Advanced Query, but the counts for the saved Metric stayed the same.

Diagnosis

This behavior is seen because the metric data once created is persisted inside db and can't be modified only by just changing the associated search query. 

Solution

The only way to sort it out is to delete the Metrics using the old search query, and re-create them with the same names.

This will enforce the new search query to persist in db with the same name.

Version history
Last update:
‎09-07-2018 01:09 PM
Updated by:
Join Us On December 10
Learn how Splunk and AppDynamics are redefining observability


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here