[GH-ISSUE #2183] ALERT MANAGER #1353

New issue

Open

opened 2026-03-02 02:22:42 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:22:42 +03:00

Owner

Originally created by @brinfotec on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2183

The system is configured to send custom alerts via email, but the alerts are being sent in the default format instead of the customized format defined in the script. The objective is to document the issue and ensure that alerts are sent according to the specified format.

Description of the Bug
A clear and concise description of the problem is that custom alerts configured in the system are being sent in the default format, without applying the customizations defined in the script. Specifically:

Affected System: Monitoring system (RMM) integrated with GLPI.
Email Address: support@brinfotec.com.br
Expected Format: Alerts should be sent in the custom format, as defined by the script. However, they are currently being sent in the default format.
Steps to Reproduce
Configure a custom alert in the RMM system.
Trigger an event that generates the alert (e.g., a monitored service failure).
Observe the email received in GLPI via the support@brinfotec.com.br address.
Verify that the email is in the default format, without the expected customizations.
Expected Behavior
The system should send alerts in the custom format defined in the script, ensuring that the email content matches the output of the script. For example, the expected format is:

ERROR DETECTED!

CLIENTE: BRINFOTEC
SITE: Blumenau
AGENTE: BRINFOTEC
SEVERITY OF ERROR: BRINFOTEC
TIME OF ERROR: BRINFOTEC
DESCRIPTION OF ERROR: BRINFOTEC
However, the current output in GLPI shows the default format, such as:

BRINFOTEC, Blumenau, BRINFOTEC - BRINFOTEC - POLÍTICA PADRÃO - Memory Check - Warning Threshold: 85% Error Threshold: 95% Failed
BRINFOTEC, Blumenau, BRINFOTEC - BRINFOTEC - POLÍTICA PADRÃO - Memory Check - Warning Threshold: 85% Error Threshold: 95% Failed - Average memory usage: 86%, Warning Threshold: 85% Error Threshold: 95%
Screenshots
If applicable, add screenshots to help explain the problem:

Current Email Format in GLPI:

Expected Email Format (Script Output):

Additional Context
The issue occurs specifically when the alert is sent to GLPI via the support@brinfotec.com.br address.
The script responsible for sending the custom alert is correctly configured, as verified through testing:
python
#!/usr/bin/env python3

import os

output = f"""
ERROR DETECTED!

CLIENTE: {os.getenv('client_name')}
SITE: {os.getenv('site_name')}
AGENTE: {os.getenv('agent_hostname')}
SEVERITY OF ERROR: {os.getenv('alert_severity')}
TIME OF ERROR: {os.getenv('alert_time')}
DESCRIPTION OF ERROR: {os.getenv('alert_message')}
"""

print(output)
Despite the script being correctly configured, the alert is still being sent in the default format.

Originally created by @brinfotec on GitHub (Mar 31, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2183 The system is configured to send custom alerts via email, but the alerts are being sent in the default format instead of the customized format defined in the script. The objective is to document the issue and ensure that alerts are sent according to the specified format. Description of the Bug A clear and concise description of the problem is that custom alerts configured in the system are being sent in the default format, without applying the customizations defined in the script. Specifically: Affected System: Monitoring system (RMM) integrated with GLPI. Email Address: support@brinfotec.com.br Expected Format: Alerts should be sent in the custom format, as defined by the script. However, they are currently being sent in the default format. Steps to Reproduce Configure a custom alert in the RMM system. Trigger an event that generates the alert (e.g., a monitored service failure). Observe the email received in GLPI via the support@brinfotec.com.br address. Verify that the email is in the default format, without the expected customizations. Expected Behavior The system should send alerts in the custom format defined in the script, ensuring that the email content matches the output of the script. For example, the expected format is: ERROR DETECTED! ---------------- CLIENTE: BRINFOTEC SITE: Blumenau AGENTE: BRINFOTEC SEVERITY OF ERROR: BRINFOTEC TIME OF ERROR: BRINFOTEC DESCRIPTION OF ERROR: BRINFOTEC However, the current output in GLPI shows the default format, such as: BRINFOTEC, Blumenau, BRINFOTEC - BRINFOTEC - POLÍTICA PADRÃO - Memory Check - Warning Threshold: 85% Error Threshold: 95% Failed BRINFOTEC, Blumenau, BRINFOTEC - BRINFOTEC - POLÍTICA PADRÃO - Memory Check - Warning Threshold: 85% Error Threshold: 95% Failed - Average memory usage: 86%, Warning Threshold: 85% Error Threshold: 95% Screenshots If applicable, add screenshots to help explain the problem: Current Email Format in GLPI: ![Image](https://github.com/user-attachments/assets/d5fc7e1f-07f5-42fe-b3e4-6d51afccd34b) Expected Email Format (Script Output): ![Image](https://github.com/user-attachments/assets/33dc8207-ac4f-4630-847a-f5374b72ef39) Additional Context The issue occurs specifically when the alert is sent to GLPI via the support@brinfotec.com.br address. The script responsible for sending the custom alert is correctly configured, as verified through testing: python #!/usr/bin/env python3 import os output = f""" ERROR DETECTED! ---------------- CLIENTE: {os.getenv('client_name')} SITE: {os.getenv('site_name')} AGENTE: {os.getenv('agent_hostname')} SEVERITY OF ERROR: {os.getenv('alert_severity')} TIME OF ERROR: {os.getenv('alert_time')} DESCRIPTION OF ERROR: {os.getenv('alert_message')} """ print(output) Despite the script being correctly configured, the alert is still being sent in the default format. ![Image](https://github.com/user-attachments/assets/bb6afffc-5dda-404c-8dc2-976b1bd58dbd) ![Image](https://github.com/user-attachments/assets/4ab15e55-8ff0-4823-a773-1d559c3d3fd7)