Server Management Suite

Hi all,
  i must config a metric for control ICMP availability for different device in my network.
I create an agentless policy that use a metric ICMP Agentless with 300sec for Polling Interval and Timeout on 4sec.

I must read from monitormetricdata the value of single policy and create report adhoc with crystal reports.

The duration/Period between a value to another is more than 300sec.

why?

thanks a lot

Danilo Zappa

Hi Danilo,

You mention above that you are reading from the monitormetricdata and if i understand you say that you see a larger duration-period between values.  

I would recommend using the Monitor Views rather than tables to do this since it will allow you the ability to analyze the data better since the table contains all metric data and not just ping.  It may be the case that you are seeing multiple metric type values.

Two views you could use are:

vMonitorMetricData
vMonitorAllMetricData 

Best Regards,

hi Joseph,

My problem is that i set a polling interval of 180sec on a metric and in monitormetricdata there are values only every 3600sec.

example:   
metric agentless with instancekey 77 (Ping)

in monitormetricdata i have timestamp, instancekey, numvalue, strvalue and duration

i have set polling on 180 for metric 77,

PROBLEM: in duration of instancekey 77, i have 3600sec not 180sec

i cant accept a time of 1hour for control state of my machine

how i can reduce this period?

thanks

Danilo

Hello Danilo,

I would suggest in this case to contact Symantec support for further assistance on this.  I believe you may not be interpriting the values in the MonitorMetricData correctly as this table has links to other tables so all of the information is not available in this single table.  I would suggest using the views as mentioned above as this will conbine those tables to help see the values better.  For example Instance in this table is a link to another table with the referrence to the instance name and so on.

Best Regards,

Hello Danilo,

Just checking if where able to the answer to this or is the same problem occuring?

Thanks,

Hi Joseph,
  today i saw the informations in vMonitorMetricData and vMonitorAllMetricData and are easier to use for reports, thanks.
But my problems remains.

I have create an agentless ping metric associated to metric collect rule.
In a metric i set 180sec as pollininterval and 15sec as timeout.

When i control vmonitorallmetricdata the duration is 3600 and not 180. why? where is the problem?

another question:
- why some  policies are associated correctly to my server and another no?
In vMonitorAllMetricData i view only several policies associated to my server. There is a timeout? Can i force a sync in this time?

Danilo

Hi Danilo,

The reason why you see duration value 3600 instead of 180 is most likely because remote monitoring server is configured to close logs every 60 minutes. You can check that by going to Home -> Monitoring And Alerting -> Monitor -> Settings -> Remote Monitoring Server Settings, 'Data Collection' tab, 'Close logs every X Minutes' setting.

Remote Monitoring Server polls ping metric accoring to the configured polling interval (180 seconds), but if the value has not changed since last time, the metric value is not logged. This is done to minimize size of the logs that need to be stored. After the logs are closed, they are uploaded to server for processing. Eventually server processes the logs and stores the values in the database. The processing of logs is done on per log basis, so if the ping metric does not change its value for 60 minutes there's going to be a single entry for this metric in the log and as a result this value will be stored with appropriate duration (3600 in your case).

With this said, it's important to note that data in vMonitorAllMetricData is not a simple log of metric polling results - it's pre-processed data that is organized for the purposes of reporting historical data in historical performance viewer. Specifically the Duration field bsically specifies how long the metric's value remained unchainged since the time specified in Timestamp field.

 

I'm not quite clear on what exactly you are asking in your other question. Could you please give me an example of your situation - this should help me better understand your question and hopefully answer it.

 

Best regards,

Vadim

Hi Vadim,

thanks for your reply. I understood the problem and i have mantained 'Close logs every X Minutes' in 60 min for reduce log problem.

I have another question.

I must collect via Ping Metric, state of a router in my network.

I create metric, rule and policy and associate this to Resource with my router IP address.

In Hystorical Monitor Graph i view my Router and its informations but not in vMonitorAllMetricData, why?

Where altiris store information of Resource Metric Agentless? In vMonitorAllMetricData view only computer agent-based or agentless metric.

 

thanks a lot

 

Danilo Zappa

Hi Danilo,

I assume that you try to find records in vMonitorAllMetricData with ResourceGuid equal to resource GUID of the router. If this is the case then you are looking at the wrong field. The field you want to use is SourceGuid - it's the resource GUID of the monitored device, so the following query should give you records from vMonitorAllMetricData for your router:

 

SELECT * FROM [vMonitorAllMetricData] WHERE [SourceGuid] = '<router resource GUID>'

 

Hope this helps.

 

Best regards,

Vadim