Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Files building up in the StreamedResults folder

Files building up in the StreamedResults folder

Created by Adrian Cook, last modified by MindTouch on Jun 23, 2016

Views: 139 Votes: 2 Revisions: 3

Overview

The files are building up in c:\ProgramData\Solarwinds\Collector\StreamedResults, most commonly in c:\ProgramData\Solarwinds\Collector\StreamedResults\VIM.VMwareVCenter.Statistics.Api.

Environment

NPM 10 and later

Cause 

The files are the Virtualization polling files that are saved in that directory before getting compressed and sent to MSMQ and then to the SQL database. If the files are stacking up, then the SQL may have issues keeping up. There is latency in the connection from the NPM server to the SQL database, or you may be polling too much for the server.

Resolution

Warning:

  • Consult your System Administrator before performing the following procedure.
  • SolarWinds strongly recommends that you only edit the PollingController.config file as instructed. Any additional modifications may result in system performance issues or may create an error state.
  • Save a copy of the original PollingController.config file to your local drive as a backup file, in case you need to roll back later.
     
  1. Go to c:\Program Files (x86)\Common Files\SolarWinds\Collector and locate the file PollingController.config.
  2. Open the PollingController.config file in any text editor.
  3. Add an option into appSettings and set stream threshold to 10 MB similar to the following:
    <appSettings>
    <add key="StreamThreshold" value="10000000"/>

    Note: The default is 4 MB. Increasing to 10 MB makes the compression easier.
  4. Restart the collector services.
Last modified

Tags

Classifications

Public