topic Re: Health Rule Custom Metric in AppD Archive

Health Rule Custom Metric

CommunityUser — Wed, 29 Apr 2015 16:10:38 GMT

Hi,

I added a health rule on a custom metric. After that the historical data of this metric was not available anymore.

Is this behaviour normal?

Regards,

Thomas

Re: Health Rule Custom Metric

Arun_Dasetty — Wed, 29 Apr 2015 17:00:43 GMT

Hi Thomas,

We confirm we do not expect such behavior as defining Health rule should not be affecting old data, can you send the screenshots from UI depicting the issue and relevant controller server.log, database.log for clarity on this to assist you further?

Regards,

Arun

Re: Health Rule Custom Metric

CommunityUser — Thu, 30 Apr 2015 07:44:22 GMT

Hi Arun,

I made some screenshots, but for security reasons I have to obfuscate some parts.

here the metrics are available:

Now I configure a health rule:

After that, the metric browser looks like this:

And after a while, the metric starts "fresh". But all old data seems lost.

I also added a part of the server.log from the corresponding timeslot.

From my point it looks like only custom metrics are involved.

Regards,

Thomas

Re: Health Rule Custom Metric

Arun_Dasetty — Thu, 30 Apr 2015 11:25:58 GMT

Hi Thomas,

We do not locate any specific errors as we are not aware of the metric id:

Can you provide complete archive of server.log for logs covering period before defining HR and after issue reproduced and also provide the output of below command issued at controller myql prompt:

mysql> select * from metric where name like %Monitor|<shaded metirc name>|availability%" \G;

Regards,

Arun

Re: Health Rule Custom Metric

CommunityUser — Mon, 04 May 2015 07:55:41 GMT

Here the result from the sql statement:

mysql> select * from metric where name like '%Monitor|<shaded metirc name>|availability%'\G
*************************** 1. row ***************************
id: 46922
version: 0
name: Custom Metrics|URL Monitor|<shaded metirc name>|Availability
name_sha1: 833f30a384423235263c53479dba2454b102388b
created_on: 1429708479936
application_id: 10
is_virtual: 0
agent_type: MACHINE_AGENT
time_rollup_type: CURRENT
cluster_rollup_type: INDIVIDUAL
hole_handling_type: REGULAR_COUNTER
account_wide_metric_id: NULL

I hope this helps.