search

louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
57.45k stars 5.19k forks source link

Please add an ability to monitor a file / drive / share drive etc. #2819

Open evildronepilot opened 1 year ago

evildronepilot commented 1 year ago

⚠️ Please verify that this feature request has NOT been suggested before.

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Please add an ability to monitor:

  1. A file in such a way so the system can report if the file has been deleted.
  2. A drive / folder has been deleted
  3. SMB / Win Share Drive is not available

✔️ Solution

At the moment I can't see any option to monitor the above and I would see quite few applications for it in the production environment.

❓ Alternatives

n/a

📝 Additional Context

I had a situation with a SQL server when the drive letter has changed the databases become unavailable. This has happened 2 times for some strange reasons only MS would know... The feature might also be useful to monitor a AD credentials and blips in the user access control... This kind of feature can also be used to check if the software on the presentation server has been removed by monitoring the presents of a config files etc.....

johntdyer commented 1 year ago

I feel like the ability for Kuma to execute a script for a check would cover this which is covered by https://github.com/louislam/uptime-kuma/issues/2645

evildronepilot commented 1 year ago

Maybe but I would like to se things to stay simple... Place a file on the SMB share or MS sharedrive and point a monitor at it.... script can do "more" but for a cost of KIS

CommanderStorm commented 1 year ago

@evildronepilot this seems like a duplicate of https://github.com/louislam/uptime-kuma/issues/2000 Can you please edit your feature request to make this more distictive or close this issue?

6twenty commented 1 year ago

@CommanderStorm I'm not OP, but in my mind this is still a distinct feature request - #2000 is about monitoring that an SMB share is available (by specifying the server URL, share path, and SMB version) whereas this PR is about monitoring that a file path exists - i.e. that a share is mounted and accessible. This also exposes other monitoring options whereby a file can simply be deleted in order to fail the test - it doesn't have to be a file mounted on an SMB server.

CommanderStorm commented 1 year ago

Is being available and functional not the same issue? (=> I think these should be merged via a comment in #2000) Said monitor being able to delete local files sounds like a different monitor though.

6twenty commented 1 year ago

I don’t think they’re the same thing - an SMB share might be available, but has been unmounted for some reason. A file check would fail using this PR but pass using #2000.

Re deleting files - sorry I wasn’t clear earlier; I didn’t mean that the monitor could delete files, but that some other process could do so causing the file to become missing. The monitor would then fail because it can no longer see the file.

susnick commented 1 week ago

This feature would be nice, I have NFS mounts that randomly break when live migrating a VM to a different hypervisor. When this happens, my application crashes because a file is not accessible. After the automated restart everything works fine, but id like to know ahead of time.