Telegram Webhook Notifications

[senati]

I configured the Telegram bot to send messages about the backup job and manual backup, but I'm not receiving them on Telegram.
When I send the test message, I receive it successfully.

I would just like to receive notification whether the backup was successful or not.

Could you help me with the solution?

 

[masterzingaya]

Confirmed. I got the same behaviour. Seems when is a job where multiple VM/LXC are on the same node (finished with an error or successful). I tested at the office 8 node cluster (proxmox 8.3.3) and at home with a single node (proxmox 8.3.3).

BTW, thanks! I wanted to know if is possible (and how) with Telegram and I found your post.

 

[senati]

I managed to resolve the error, I just had to reduce the content of the message, Telegram has a character limit.

 

[masterzingaya]

Good to know. Though I use webhook to send info to Zabbix. I don't think it has any limitation but I'll try.

 

[Agathold]

I managed to resolve the error, I just had to reduce the content of the message, Telegram has a character limit.

Hi! How did you manage to reduce the content of the message?

 

[aabraham]

I managed to resolve the error, I just had to reduce the content of the message, Telegram has a character limit.

Thank you for posting your solution. This could be helpful to others, too.

 

[Meister Mopper]

Hi! How did you manage to reduce the content of the message?

I would also be very interested in that.

 

[Agathold]

As a temporary solution, you can edit the /usr/share/pve-manager/templates/default/vzdump-body.txt.hbs file (after creating a backup copy).

The contents of the file look like:

{{error-message}}
Details
=======
{{table guest-table}}
Total running time: {{duration total-time}}
Total size: {{human-bytes total-size}}

Logs
====
{{logs}}

Delete lines in the file:

Logs
====
{{logs}}

In this case, the backup report will not contain detailed logs about each VM. In my opinion, this is not always necessary in reports.

It is important to remember that this file may be overwritten during a system update!!!