cpuTarget in user.properties seems to be ignored

Follow

Paul Smith

• November 10, 2017 02:47

I have configured the cpuTarget property in user.properties to be:

targetCPU=20

 

Following the documentation from: https://help.sumologic.com/Manage/Collection/06Set-the-Collector-CPU-Usage-Target

 

When I review the collector.log, I see instead:

2017-11-10 13:38:06,351 +1100 [WrapperSimpleAppMain] INFO  com.sumologic.scala.collector.monitoring.CollectorResourceMonitor - Initializing CPU Resource Monitor with a target of None

This seems to come out whether I have targetCPU set or not.

I see no other logs like the ones mentioned in the help article (e.g. 'Resource consumption $current% is lower than $target%") .

 

This leads me to believe the targetCPU is not being picked up.

running SumoCollector-19.209-5.x86_64 RPM on a Linux Oracle Linux 6.3 on a 48 core physical machine.  

0

• Official comment

  

  Raghu Murthy

  • November 10, 2017 17:11
  • Edited

  Hi Paul,

  If you review the doc relating to user.properties (different one than the one you referenced :-( ), there is a column which is titled "Can it be changed after installation" and that column for targetCPU setting states "No, use the Collector Management API to modify"

   https://help.sumologic.com/Send-Data/Installed-Collectors/05Reference-Information-for-Collector-Installation/06user.properties

  To push the change with immediate effect there are two ways to change this collector attribute , one is to

   

  - do it via the UI via Manage Data -> Collection -> Identify the collector -> then Edit Collector to change the setting.

   

  - the second way to do it is via the API using the Put Method to update the collector setting of "targetCpu".

  https://help.sumologic.com/APIs/01Collector-Management-API/Collector-API-Methods-and-Examples#Update_a_Collector

   Also note if the API is used having the setting labelled as "targetCPU" instead of the correct entry of "targetCpu" would likely matter

  Hope that helps.

  Regards

  Raghu Murthy

   

   

  Permalink

Please sign in to leave a comment.