Product(s):	APM Implementation and Performance Management
	Version(s):	7.11
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem

No matter the polling schedule if the On Prem Agent cannot collect readings an ODC On Prem Reading Request, a new reading request will be created every minute and not according to the schedule. The problem here is that although this could be caused by user error it brings down ODC service.

The kinds of user errors that can cause this problem:

1.) configure an Indicator with ODC data source and tag and then switch the ODC data source
2.) manually edit the tag to something that does not exist

When this happens the On Prem Agent will not be able to collect readings and the reading requests will start accumulating very quickly. One wrong Indicator will cause these reading requests to accumulate for ones that are correctly configured too because the agent cannot handle the volume of Reading Requests in a timely manner.

Solution -  Fixed in 7.12.1

Created VSTS156022 - ODC Service creates unwanted pending reading requests when OnPrem Agent fails to provide reading. This is being reviewed for repair in a future release.

Workaround is to stop the service, find the offending ODC Indicators and remove them from the polling schedule and then restart the service. The offending indicators can then be fixed and put onto a new polling schedule for testing. We don't recommend testing using the existing polling schedules because you don't want to increase the backlog of reading requests should the offending indicators not be fixed.