Getting Data In

Status of tailing gz files

zscgeek
Path Finder

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
0 Karma
1 Solution

amrit
Splunk Employee
Splunk Employee

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.

View solution in original post

amrit
Splunk Employee
Splunk Employee

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.

zscgeek
Path Finder

Thanks for the answer. Maybe not what I wanted but I can now stop looking 😉

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...