The amount of noise/clutter in the IMPS etatrans log may have impact while you are tracing a data related challenge.
To help mask this challenge, you may set the log level from default of 7 to log level 3, but this will still return data that you may not be interested in seeing.
I have created a "function" to act as an alias for the 'imps' userID, that will reduce the clutter to a minimal, and find the correct active file.
See if this has value for your own environment.
Avoid the noise - IMPS etatrans alias/function "tap"
| ANA Technology Partner |
remove preview |
 |
| Avoid the noise - IMPS etatrans alias/function "tap" |
| Monitoring use-cases within solutions that use various logs can be onerous when there is "noise" or low-value events in the logs. For provisioning use-cases, we prefer to focus on the "CrUD" use-cases and actions. The CA/Symantec Identity Manager solution has a mid-tier component, IM Provisioning Server, that captures quite a bit of information useful for monitoring for success/failure. |
| View this on ANA Technology Partner > |
|
|
Add to imps .bash_profile then logout/login and test with the "tap" alias.
Update the grep command as needed to exclude key phrase that have no value for your testing.
function tap () {
cd $ETAHOME/logs
a=$(ls -rt $ETAHOME/logs | grep etatrans | tail -1)
pwd
echo "Tail current log file with exclusions: "$a
tail -F $a | grep -v -e ":LDAP" -e ":Config" -e "AUDITCONFIG" -e ":EtaServer" -e ":Bind " -e ":Unbind " -e ":Search "
}
export -f tap
Cheers,
A.
------------------------------
Alan Baugher
ANA Technology Partner (anapartner.com)
------------------------------