In this answer I can see there is ways to get the status of the tailing processor on a box. Only problem is it looks like it does not correctly report the status of .gz files.
What we are seeing for status on each file (Regardless of indexing status) is:
https://XXX.orl.voxeo.net:9976/services/admin/inputstatus/TailingProcessor:FileStatus
/rsanx/logs/test2/master-orl-2010-05-04-0400-orl121.gz
file position 0
file size 880427
parent /rsanx/logs
percent 0.00 ### NOTE THIS SAYS 0% - YET I CAN FIND RESULTS FOR THIS FILE
type finished reading ### NOTE THIS SAYS FINISHED
Is there any way to get more insight of the status of the processing gz files (perhaps querying fishbucket?)
My inputs.conf is configured as below:
[monitor:///rsanx/logs]
disabled = false
followTail = 0
index = default
sourcetype = voxeo_hosted_file
In short, no, there is currently no way to get more details into archive processing status.
Generally whenever we hand the URL to the TailingProcessor:FileStatus endpoint, we point out that it is absolutely a prototype feature. The endpoint was used to provide some hints about what the TailingProcessor activities during its 4.1 rewrite - therefore the results are sometimes a bit inaccurate, but generally correct. Generally users are instructed to supplement this endpoint with DEBUG level logging in splunkd.log.
The ArchiveProcessor has not yet been retrofitted to provide this endpoint with status updates. If you'd like to see this sooner rather than later, I'd recommend filing an enhancement request.
For now, consider this endpoint to be something that just provides hints. In your example above, the status means that this file has been 1) seen and 2) handed off to the ArchiveProcessor, so it's out of the TailingProcessor's hands.
In short, no, there is currently no way to get more details into archive processing status.
Generally whenever we hand the URL to the TailingProcessor:FileStatus endpoint, we point out that it is absolutely a prototype feature. The endpoint was used to provide some hints about what the TailingProcessor activities during its 4.1 rewrite - therefore the results are sometimes a bit inaccurate, but generally correct. Generally users are instructed to supplement this endpoint with DEBUG level logging in splunkd.log.
The ArchiveProcessor has not yet been retrofitted to provide this endpoint with status updates. If you'd like to see this sooner rather than later, I'd recommend filing an enhancement request.
For now, consider this endpoint to be something that just provides hints. In your example above, the status means that this file has been 1) seen and 2) handed off to the ArchiveProcessor, so it's out of the TailingProcessor's hands.
Thanks for the answer. Maybe not what I wanted but I can now stop looking 😉