+1
Assuming that the performance related messages (availability took too
long... metric collection took too long...) get logged at INFO or WARN,
I don't see a reason to inform the user that a job that runs every 30
seconds actually ran.
--
Larry O'Leary
I think these can bow go to DEBUG. We don't want recurring
messages at
30s intervals.
On 11/18/2013 6:17 AM, Thomas Segismont wrote:
> Hi everyone,
>
> In the agent log file, there are three recurring log messages for
> availability and measurement:
>
> ======
> 2013-11-18 11:19:37,640 INFO [InventoryManager.availability-1]
> (rhq.core.pc.inventory.AvailabilityExecutor)- Scan Starting: Mon Nov
> 18 11:19:37 CET 2013
>
> 2013-11-18 11:19:37,648 INFO [InventoryManager.availability-1]
> (rhq.core.pc.inventory.AvailabilityExecutor)- Scan Ended : Mon Nov
> 18 11:19:37 CET 2013 : Scan [startTime=1384769977640,
> endTime=1384769977647, runtime=7, isFull=false, isForced=false,
> numResources=119, numGetAvailabilityCalls=7, numScheduledRandomly=0,
> numPushedByInterval=6, numAvailabilityChanges=0, numDeferToParent=0]
>
> 2013-11-18 11:19:56,192 INFO [MeasurementManager.sender-1]
> (rhq.core.pc.measurement.MeasurementSenderRunner)- Measurement
> collection for [5] metrics took 18ms - sending report to Server...
> ======
>
> AvailabilityExecutor messages used to be at DEBUG level.
>
> Do we still need these messages at INFO level? They make the agent log
> file grow quickly.
>
> Regards,
> Thomas
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel