Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..
800 views

How to resend all events to OMi

Jump to solution

Hello,

 

How to resend all events to OMi?

To resend the current monitor status.

The issue is that OA failed (event storms) or firewall issue SiS -> OMi.

 

Best regards,

Georgi

 

 

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi Georgi,

it's my understanding that SiteScope sending an event simply means it writes a line into the integration log file
(HPSiteScopeOperationsManagerIntegration.log, you might wanna check KM01739445 for details),
which then is analyzed / post-processed by one of the prolicies deployed.

This is an excerpt of one of my systems:

2017/08/12 11:59:57:375 CRITICAL SiteScope SiteScope:sov02bac17.eu.hpecorp.net:SG_Test_SIS_bac17:CPU sov02bac17 sov02bac17.eu.hpecorp.net Metric 'utilization' changed status from 'warning' to 'error' Metric 'utilization' crossed 'utilization == 100' with value '100' CPU utilization sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization:Unknown:CRITICAL sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization SiteScope:7:600248 Unknown:Unknown:100 SiteScope@@sov02bac17.eu.hpecorp.net SiteScope:7:600253 http://sov02bac17...Ljja0DKaN7 SiteScopeMonitor:200980909:200980915 1         

2017/08/12 12:04:57:372 MINOR SiteScope SiteScope:sov02bac17.eu.hpecorp.net:SG_Test_SIS_bac17:CPU sov02bac17 sov02bac17.eu.hpecorp.net Metric 'utilization' changed status from 'error' to 'warning' Metric 'utilization' crossed 'utilization > 90' with value '99' CPU utilization sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization:Unknown:MINOR sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization SiteScope:7:600248 Unknown:Unknown:99 SiteScope@@sov02bac17.eu.hpecorp.net SiteScope:7:600253 http://sov02bac17...Ljja0DKaN7 SiteScopeMonitor:200980909:200980915 1         

As long as the entries haven't been deleted out of the file, you could use some scripts to extract the event information out of the file and "manually" (by calling opcmsg or alike) resend the events to OMi.

Greetings
Siggi

Customer Support
Micro Focus

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

View solution in original post

5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi Georgi,

it's my understanding that SiteScope sending an event simply means it writes a line into the integration log file
(HPSiteScopeOperationsManagerIntegration.log, you might wanna check KM01739445 for details),
which then is analyzed / post-processed by one of the prolicies deployed.

This is an excerpt of one of my systems:

2017/08/12 11:59:57:375 CRITICAL SiteScope SiteScope:sov02bac17.eu.hpecorp.net:SG_Test_SIS_bac17:CPU sov02bac17 sov02bac17.eu.hpecorp.net Metric 'utilization' changed status from 'warning' to 'error' Metric 'utilization' crossed 'utilization == 100' with value '100' CPU utilization sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization:Unknown:CRITICAL sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization SiteScope:7:600248 Unknown:Unknown:100 SiteScope@@sov02bac17.eu.hpecorp.net SiteScope:7:600253 http://sov02bac17...Ljja0DKaN7 SiteScopeMonitor:200980909:200980915 1         

2017/08/12 12:04:57:372 MINOR SiteScope SiteScope:sov02bac17.eu.hpecorp.net:SG_Test_SIS_bac17:CPU sov02bac17 sov02bac17.eu.hpecorp.net Metric 'utilization' changed status from 'error' to 'warning' Metric 'utilization' crossed 'utilization > 90' with value '99' CPU utilization sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization:Unknown:MINOR sov02bac17.eu.hpecorp.net:6d04a2c4-44fd-4e5f-86ca-5f1624fd1c8f:utilization SiteScope:7:600248 Unknown:Unknown:99 SiteScope@@sov02bac17.eu.hpecorp.net SiteScope:7:600253 http://sov02bac17...Ljja0DKaN7 SiteScopeMonitor:200980909:200980915 1         

As long as the entries haven't been deleted out of the file, you could use some scripts to extract the event information out of the file and "manually" (by calling opcmsg or alike) resend the events to OMi.

Greetings
Siggi

Customer Support
Micro Focus

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

View solution in original post

Highlighted
Respected Contributor.. Respected Contributor..
Respected Contributor..

Hi Siggi,

Thanks!

 

opsmsg has only one policy when Application =SiteScope.

Its parsing is not like the SIS one.

 

It could be possible to force the OA to read the file from the beginning but this will create event storm again .

Also the data format is old and I think OMi GW has a filter by data..

 

SiS has to have internal database recording when the evet is send or not ??? maybe once on state change and no need of database.

But when we do integration to OMi. SiS is forced to update all states. We needed this to be triggered manually,

 

Best regards,

Georgi

 

 

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Hey,

I recall doing something like this a while back. I believe the solution to resend all was to stop SiS, delete the .dyn files from the SiteScope/groups folder, and simply restart. To my knowledge the system then looses it's stati - and any change will be treated as a new event - thus resending all.

It was a while back though, you might want to test this on a non-prod environment.

regards

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

Hello

Those suggestions works for you? 

If not, you can open a new support case in the OMi team, they are the chosen ones to review the OA problems.

Plase let us know your results

Regards

Jose Garita

0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

According to Support the correct method is setting "Manually send first event" by ´Global search and Replace´.
Unfortunately my experience is that this doesn´t work (tried it on 11.24, 11.33 and 11.40). Setting "Manually first event" on a single monitor works fine, and is very useful. But when set on a bulk of monitors, there are none or very few of the monitors that actually produce events.

 

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.