I also thought about that, but I am keeping that as a last resort. But that 
would require me to push a script to all my 2500+ servers. 

On Tuesday, March 3, 2020 at 8:46:27 PM UTC+5:30, Murali Krishna Kanagala 
wrote:
>
> I would write a small shell script that tries to write to the nfs mount  
> path and writes the status to a file which can be read by the text file 
> collector. And schedule that shell script cron. I think this is the easiest 
> solution.
>
> On Tue, Mar 3, 2020, 9:12 AM Yagyansh S. Kumar <[email protected] 
> <javascript:>> wrote:
>
>> Already enabled the nfs and nfsd collectors. Till now I haven't found 
>> anything that can accurately give me the information about NFS hang.
>> Correct me if I am wrong, but I don't think it is a good indicator of NFS 
>> hang as there may be times where no activity is happening on the NFS, but 
>> that does not mean that NFS is hanged. (eg. I have 25 NFS mounts on one of 
>> my servers, some of them are used rarely, so we won't find any substantial 
>> IO on those mounts, but I need to know whether they are accessible or not). 
>> Still, thanks for the suggestion, will try it out once.
>>
>>
>> On Tuesday, March 3, 2020 at 8:35:03 PM UTC+5:30, Murali Krishna Kanagala 
>> wrote:
>>>
>>> Try enabling the nfs options in the node exporter config. It will spit 
>>> out some metrics about the nfs status. 
>>>
>>> Also look at the disk IO metrics from node exporter and if you see no 
>>> activity which indicates the nfs is not doing anything.
>>>
>>> On Tue, Mar 3, 2020, 7:10 AM Yagyansh S. Kumar <[email protected]> 
>>> wrote:
>>>
>>>> I want to check if the NFS is hanged(i.e whether it is accessible from 
>>>> the server or not, and if yes then what is the response time it is 
>>>> getting). I know using the mountstats and nfs collector we have a lot of 
>>>> metrics for NFS, but haven't found any that can tell me every time the NFS 
>>>> hangs correctly.
>>>> Thanks in advance.
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Prometheus Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/prometheus-users/06929518-d3b5-4c2f-9490-b08cc664d26b%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/prometheus-users/06929518-d3b5-4c2f-9490-b08cc664d26b%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Prometheus Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/prometheus-users/1dda60cc-0b20-47da-87ff-4f1c76ce076f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/prometheus-users/1dda60cc-0b20-47da-87ff-4f1c76ce076f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/3822b8a0-697f-4efe-87ab-5a3f90de0786%40googlegroups.com.

Reply via email to