Bhanu_Prakash Valued Contributor.
Valued Contributor.
562 views

CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Hi,

There is an instruction in the CO 3.02 install guide : "AlarmFilterByText must be set to apply filtering on the alarms to be monitored."

Are the Alerts generated only when filter is set on ovconfget?

Example: AlarmFilterByText=Host connection and power state

Does this forward only "Host connection and power state" alerts and ignore the rest?

I wanted to understand , If the value "AlarmFilterByText" is NOT set on ovconfget, does it still forwards alerts to HPOM? --> Forward All alerts as filter is not set?

Thanks in advance.

 

 

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Hello,

 

Alarm status changed events are collected if you have the following line in the file /opt/OV/newconfig/OVPM/smepack/VCENTER/data/VIEventTypes.cfg:

AlarmStatusChangedEvent

Note that this line is commented out by default in the file.

 

If you deploy the policy vPV-EventMonitor with the parameter AlarmFlag set to true, then the collected alarms are also forwarded to OMi/OMx/OMW. Note that this parameter is set to false by default.

If AlarmFilterByText is empty (default value), all the alarms are forwarded.

If AlarmFilterByText is not empty, then only the alarms matching the filter are forwarded.

Assume the following three example alarms:

Alarm ''Virtual machine memory usage'' on vm211A changed from Green to Yellow
Alarm ''Virtual machine cpu usage'' on vm211A changed from Green to Red
Alarm ''Test alarm for CPU usage'' on vm120A changed from Green to Yellow

The part between quotes is the 'alarm name' as it also appears in the vSphere client.

If you are interested to forward the first two alarms only, you would enumerate their 'alarm names' in the AlarmFilterByText parameter of the policy, seperated by a comma:

AlarmFilterByText=Virtual machine memory usage,Virtual machine cpu usage

The third alarm (or any other alarm) will not match the filter and will therefore not be forwarded.

 

 

Thanks,

Thierry.

 

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Hello,

 

Alarm status changed events are collected if you have the following line in the file /opt/OV/newconfig/OVPM/smepack/VCENTER/data/VIEventTypes.cfg:

AlarmStatusChangedEvent

Note that this line is commented out by default in the file.

 

If you deploy the policy vPV-EventMonitor with the parameter AlarmFlag set to true, then the collected alarms are also forwarded to OMi/OMx/OMW. Note that this parameter is set to false by default.

If AlarmFilterByText is empty (default value), all the alarms are forwarded.

If AlarmFilterByText is not empty, then only the alarms matching the filter are forwarded.

Assume the following three example alarms:

Alarm ''Virtual machine memory usage'' on vm211A changed from Green to Yellow
Alarm ''Virtual machine cpu usage'' on vm211A changed from Green to Red
Alarm ''Test alarm for CPU usage'' on vm120A changed from Green to Yellow

The part between quotes is the 'alarm name' as it also appears in the vSphere client.

If you are interested to forward the first two alarms only, you would enumerate their 'alarm names' in the AlarmFilterByText parameter of the policy, seperated by a comma:

AlarmFilterByText=Virtual machine memory usage,Virtual machine cpu usage

The third alarm (or any other alarm) will not match the filter and will therefore not be forwarded.

 

 

Thanks,

Thierry.

 

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Bhanu_Prakash Valued Contributor.
Valued Contributor.

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Version: HPE Cloud Optimizer Version: 03.02.004

Policy Setup: AlarmFlag=true, AlarmFilterByText=True

ovconfget:

[eaagt]

AlarmFilterByText=Virtual machine CPU usage,Virtual machine memory usage, VKernel VM Disk Latency

[CPUMonitor]
ShortTermPeak=0
VMCPUReadyUtilizationThreshold=0.1
VMMotionThreshold=0

[HostKernelLatency]
KernelLatencyThreshold=0
ShortTermPeak=0

There are alarms on events database:

ex:  

2017-11-10 06:38:38 | 618 | | Alarm ''Virtual machine CPU usage'' on testvm002 changed from Yellow to Red

2017-11-10 07:08:38 | 254 | | Alarm ''VKernel VM Disk Latency'' on testvm003 changed from Green to Yellow

These alarms are not forwarded to OM

However I could see other alerts like: VM moved to off state, FS Alerts,

please advice...

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Hello,

 

Take care to remove extra spaces in front of and after the commas in AlarmFilterByText (I see there is an extra space before the word VKernel).

The troubleshooting from here would depend on which OM instance you are using (OMi, OML, OMW?) and we'll need to make sure that you have the latest integration bits. Also, what is the version of your vPV-EventMonitor policy?

Do the corresponding VMs exist as CIs in RTSM or nodes in the node bank? If you don't have recent integration bits and hotfixes, the discovery can be a bit tricky.

Is your policy interval aligned on the collection interval? If not, then you can miss a fair percentage of events.

My first approach would be to verify the event flow on the CO server. You can enable debug mode for the policy by setting the debug parameter to value 2. With recent integration bits, you should get policy logging into /var/opt/OV/log/vPV-EVentMonitorLog.txt. You can also enable tracing for the relevant OA processes:

ovconfchg -ns eaagt -set OPC_TRACE_AREA ALL

ovconfchg -ns eaagt -set OPC_TRC_PROCS opcmona,opcmsga

ovconfchg -ns eaagt -set OPC_TRACE TRUE

You will need to generate new AlarmStatusChangedEvents after setting these trace options and then wait for more than 2 collection intervals (best would be 4-5 intervals) before collecting the trace.

The files /var/opt/OV/log/vPV-EVentMonitorLog.txt and /var/opt/OV/tmp/OpC/trace will enable us to verify how far the agent goes into processing the alarm.

I would advise pursuing this through a support case.

 

Thanks,

Thierry.

 

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Bhanu_Prakash Valued Contributor.
Valued Contributor.

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

 AlarmStatusChangedEvent alerts exists in both the logs

/var/opt/OV/log/vPV-EVentMonitorLog.txt  

/var/opt/OV/tmp/OpC/trace

AlarmStatusChangedEvent| 2017-11-10T15:48:14+05:00| 423e9db8-8ca4-a579-4b4e-a1c7998c0f7b| Test2016STDv802| Test2016STDv802| Alarm ''VKernel VM CPU Utilization'' on Test2016STDv802 changed from Green to Red

11/10 17:27:39.094 opcmona(160357:160376)[mon]: OvEpGenAdvMonMetric::AddInstance [52] [AlarmStatusChangedEvent| 2017-11-10T17:13:36+06:00| 423e9db8-8ca4-a579-4b4e-a1c7998c0f7b| Test2016STDv802| Test2016STDv802| Alarm ''VKernel VM CPU Utilization'' on Test2016STDv802 changed from Green to Red]

However these are not carried / forwarded to OM

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: CO to HPOM Alerts : AlarmFilterByText

Jump to solution

Hello,

 

These trace extracts show that the alarm is loaded into the policy, but don't tell us how it got processed.

Are you seeing any trace entry from process opcmsga related to this alarm?

If yes, then the problem is after CO and needs to be troubleshooted accordingly.

This can be better addressed through a support case.

 

Thanks,

Thierry.

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.