Normally this problem comes from the population of Operation Agent from HP OM.
I enfort to confirm this situation, however I would like explain a little bit the "possible situation".
This error comes from Operation Agent cannot report performance metrics to HP OM. If SiteScope is reporting correclty data to HP OM or BSM, please do not take to much attention to this error. In theory, the 2 types of integration in BSM are not affected from this error.
If finally you confirm this Operation Agent is from HP OM and not from SiteScope, the steps to fix this are:
1- Delete event Integration.
2- Reinstall Operation Agent from SiteScope tools.
3- do the integration again.
I know is little bit tricky uninstall and install the integrations, but is the only way to fix the problem.
"HP Support If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution."
we are seeing the very same error messages in our error.log on two different SiteScope machines. on both machines we have the following integrations active:
1. BSM integration for samples and toloplogy as per SAM (System Availability Management)
2. Event and Performance integration via the OM Agent into BSM/OMi. Means we are sending events from SiteScope to BSM via the agent and we use Performance Graphing in BSM to display performance data from all the SiteScope monitors.
In the past we were seing chunks of 500 samples being dropped in the log file. Based on this we have increased the sample queue size from 2000 to 4000 in SiteScope settings. With this change now the error message is only showing that chunks of 100 are being dropped.
No generic data integration is configured on the system. Only the two pretty standard integrations described above.
We are having some strange behavior in BSM Service Health that certain status updates for SiteScope monitors are not being received. Meaning the status for certain HI/KPI is outdated (Critical) even though SiteScope has the status OK for the monitors. Certain of these status updates are more than half a year old? So BSM is not receiving or displaying the correct status based on the samples received.
This error has to do with OA metric integration probably, it says generic data as they use same mechanism. If no generic data integration in place then is definitively OAs CODA component issues. In case you have enabled metric integration to OA make sure there is a consumer like PM or BSM >> PMi reading from CODA, otherwise the Q will overflow. Notice this has nothing to do with metrics reported to BSM for CI status and reports as this goes via different channel.
tibornad, as you are using PMi you may check OA's system.txt log file and SiS/logs/oa_metric_integration.log to check if there are issues with CODA.
Kenneth Gonzalez HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
after disabling the option "Enable HP Operations Manager metrics integration" in the Integration Preferences in SiteScope the errors are not longer showing up in the logs.
just for clarification purpose i have the following question:
in the past with the option "Enable HP Operations Manager metrics integration" enable in the Integration Preferences the agent on the SiteScope machine was reporting metrics to CODA which was then used in BSM for performance graphing purpose. At least this is my understanding. with the current release of BSM not the metrics are not longer reported to CODA but directly stored in the BSM Profile DB. Correct? So that's why it is possible to disable this option and still have performance data in BSM since BSM is pulling the data directly from the DB. so disabling the option in SiteScope Integration Preferences does not have any impact at all on the graphing capabilities.
i was not able to find any reference in the documentation where this was properly described and also the options in SiteScope are pretty misleading.
but based on the fact that the errors are not longer in the logs i assume this is correct.