WesleySmith
New Member
Progress Version: 10.2B06
Hi All,
As part of our upgrade process we ask our customers to run with LOG-MANAGER enabled for the first couple of weeks after go-live.
The reason for this is when LOG-MANAGER is run with no entry types enabled it captures unexpected, Progress generated errors.
These logs are then returned to us so we can analyse the contents and investigate and fix any issues that they have had which were not identified during our QA testing phase.
This has proved to be very useful but we are now having internal discussions about whether LOG-MANAGER should just be left enabled permanently and one of the questions being asked is "What is the overhead of running LOG-MANAGER with no entry types enabled?"
If it is minimal we could let it run permanently but if its a larger overhead we may need to remain as we are.
Does anyone know the answer to this?
Hi All,
As part of our upgrade process we ask our customers to run with LOG-MANAGER enabled for the first couple of weeks after go-live.
The reason for this is when LOG-MANAGER is run with no entry types enabled it captures unexpected, Progress generated errors.
These logs are then returned to us so we can analyse the contents and investigate and fix any issues that they have had which were not identified during our QA testing phase.
This has proved to be very useful but we are now having internal discussions about whether LOG-MANAGER should just be left enabled permanently and one of the questions being asked is "What is the overhead of running LOG-MANAGER with no entry types enabled?"
If it is minimal we could let it run permanently but if its a larger overhead we may need to remain as we are.
Does anyone know the answer to this?