Notifications and logging

[nealeydee]

Pre-submission checks

• I have searched both open and closed issues and confirmed this doesn't already exist
• I have checked the roadmap and this isn't already planned
• This feature aligns with the project's scope (RClone management)

Feature Description

Firstly, thank you for your hard work. Çok teşekkür ederim.
Below are some of my ideas for future enhancements of the headless version (but potentially applicable to all versions).

I am currently running headless and would like to enable notification on job failure and job success. As this is headless - the notifications need to get outside of the server which is headless.

So two features to request:

Proposed Solution

• Monitoring of Rclone logs - identify successes and failures.
• Send the corresponding Log message to Telegram:
  curl -s -X POST https://api.telegram.org<YOUR_BOT_TOKEN>/sendMessage -d chat_id=<YOUR_CHAT_ID> -d text="Rclone Task Completed: $(tail -n 5 /var/log/rclone.log)" for "Rclone Task Completed".

Of course, this would require adapting the UI to allow for specifying the BIT TOKEN and CHAT ID.

This is one idea. An e-mail message could be a great way of sending an notification. An MQTT message could also be another great addition.... with somewhere to configure MQTT server, authentication, topic etc. (Although the topic could be generated from the sync Job name):

1. Send "Started" message

mosquitto_pub -h <BROKER_IP> -t "rclone/status" -m "Sync Started: Google Drive"

2. Run the actual rclone command

rclone sync /local/path remote:path --log-file=/tmp/rclone.log

3. Check exit status and send result

if [ $? -eq 0 ]; then
mosquitto_pub -h <BROKER_IP> -t "rclone/status" -m "Sync Success"
else
mosquitto_pub -h <BROKER_IP> -t "rclone/status" -m "Sync Failed: $(tail -n 1 /tmp/rclone.log)"
fi

For the client version, these may be less necessary - but I see people requesting status in tray icon etc. Perhaps by having an holistic approach to notifying and log management, the app could become a lot more useable.

Feature Category

Other

Applicable Versions

• Desktop (GUI application with window)
• Headless (Web server accessed via browser)
• Portable (Standalone executable)
• All versions

Mockups/Screenshots

No response

Technical Considerations

No response

Additional Context

No response

[Hakanbaban53]

Rica ederim, ne demek :)

This is actually a really solid idea. You are totally right, especially for the headless mode. It is a pain to check logs constantly just to see if a backup finished or failed.

Since the app is the one actually spawning and controlling the rclone processes, it is pretty easy for me to catch the exit codes (success vs failure) and grab the last few lines of the log, just like you showed in your examples.

I think I can add a "Notifications" tab to the settings. I will probably start with Webhooks (since they work with Discord, Slack, and custom scripts) and Telegram since it is easy to set up. MQTT is also a great idea for Home Assistant users, so I will keep that in mind too.

I just need to work on the UI for saving those API tokens securely, but I am definitely adding this to the roadmap.

Thanks for the code snippets by the way, that saves me some research time! 🚀