You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using for some time the Telegram integration of Falcosidekick and I've noticed in many cases that events are not sent to the Telegram channel because the message length exceeds the maximum allowed (4096) by the Telegram API.
This triggers an error on Falcosidekick end which seems logically correct, but we would miss out on potentially important information as it's the main channel for alerts in my organization.
Reaching that limit is common when we run our penetration tests and it's critical to get alerts as soon as anything happens.
PoC
We simply need to trigger any alert with a long enough message to reach the limit:
We can read the error message in the Falcosidekick logs:
Apr 09 00:00:00 x falcosidekick[x]: 2024/04/09 00:00:00 [ERROR] : Telegram - header missing (400): {"ok":false,"error_code":400,"description":"Bad Request: message is too long"}
Apr 09 00:00:00 x falcosidekick[x]: 2024/04/09 00:00:00 [ERROR] : Telegram - header missing
Feature
As this is a limitation of the Telegram API, It would be great to have a feature that truncates the message to the maximum allowed length OR to have a feature that sends the message in multiple parts (this would eventually lead to a ratelimit issue on the Telegram API).
Additional context
This issue might also be happening in other integrations of Falcosidekick just like Discord, but I haven't tested it yet.
The text was updated successfully, but these errors were encountered:
I'm not a Telegram user and didn't implement this output in falcosidekick myself. This is a good point to notice, thanks.
Truncating the message seems the better choice, but it's not so easy. I'll work on something asap, and see if this limitation also occurs for other chat message systems.
I confirm this issue happens is other outputs, for eg, falcosidekick-UI. I proposed a PR to truncate the long output fields when the global length of the payload is > 4096.
Motivation
I've been using for some time the Telegram integration of Falcosidekick and I've noticed in many cases that events are not sent to the Telegram channel because the message length exceeds the maximum allowed (4096) by the Telegram API.
This triggers an error on Falcosidekick end which seems logically correct, but we would miss out on potentially important information as it's the main channel for alerts in my organization.
Reaching that limit is common when we run our penetration tests and it's critical to get alerts as soon as anything happens.
PoC
We simply need to trigger any alert with a long enough message to reach the limit:
We can read the error message in the Falcosidekick logs:
Feature
As this is a limitation of the Telegram API, It would be great to have a feature that truncates the message to the maximum allowed length OR to have a feature that sends the message in multiple parts (this would eventually lead to a ratelimit issue on the Telegram API).
Additional context
This issue might also be happening in other integrations of Falcosidekick just like Discord, but I haven't tested it yet.
The text was updated successfully, but these errors were encountered: