Last updated on JANUARY 26, 2017
Applies to:Oracle Communications Indexing and Search Service - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
We have Nagios checks for activity in iss-indexsvc.log.0 (and maybe some others).
They are done by Nagios running a Perl script which does "tail -r $logfile | head -n 50" and parses the output and then looks at the time stamps on those last 50 lines.
This occasionally has run afoul of some blocks of messages in the indexsvc which can be longer than 50 lines, so we increased it to 200.
Is there any reason why it would be useful to look at the timestamps on those messages *in* the file rather than simply looking at the last update timestamp *on* the file?
It seems to me this could be done *MUCH* more efficiently with the "find" command, or "ls -l", or Perl functions to examine the last update time of the file.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms