Facebook: You can now post direct to our Facebok page!

You can now post direct to our Facebok page! If you have any questions please ask!
Posted by Protocol - Infrastructure Monitoring on Monday, 14 December 2015

Alerts owned by NNMi stuck in HPOM

I previously mentioned on the blog (http://tiny.cc/protocolblog) about a strange problem where I see alerts owned in...

Posted by Protocol - Infrastructure Monitoring on Wednesday, 27 January 2016

The Optimized HP Operations Bridge

Consolidated IT Operations with the HP OpsBridge

NNMi alerts owned by opc_adm in HPOM

Have a current weird problem, where I see alerts owned in HPOM by opc_adm due to the web services integration of NNMi with HPOM.

I can't see it documented anywhere (as usual so often with these things!).  HP support are investigating.

If anyone else has any experience of this please share your tips.

Thanks,
Dave

uCMDB Contracts

Wanted - uCMDB Consultants who have either held SC or DV Clearance or have current SC/DV Clearance for contract roles with HP.

Contact me for more details.

Thanks,
Dave

Zabbix 6m Contract

It’s initially a 6 month contract, Candidates MUST hold valid sc clearance & it Is paying a very competitive rate based in Salisbury.

Contact me for further details if you are interested.

Thanks,
Dave

Logfile Monitoring Delays?

Monitoring logfiles using a policy with hundreds and hundreds of conditions can cause HPOM's logfile encapsulator (opcle) to run into problems.

I have seen delays in message receive time on the HPOM manager in numerous HPOM installations, sometimes hours behind the original logfile alert time, which is obviously unacceptable in production monitoring environments.

HP support couldn't offer much help, but a few key principles can help reduce this problem and hopefully eradicate it completely.

1. Try and ensure the logfile being monitored is named specifically, or if using a command to generate a list of logfiles, try and make sure this list is small
2. Try and keep the number of policy conditions to a minimum where possible
3. Try and ensure as much suppression is placed at the top of the logfile monitoring policy to ensure opcle matches and drops unncessary text as soon as possible (thereby freeing it up to parse additional lines)
4. Consider changing the environment variable which allows opcle to read multiple lines at a time - for example OPC_LE_MAX_LINES_READ
5. Review the logfile polling period

Hope this helps.
Dave

New HP Account Manager

1st meeting with the new HP account manager today, really beneficial! Had some bad experiences in the past with account managers, so hope this relationship proves to be more mutually satisfying!