Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The alarm cannot be triggered according to the specified rule. #6684

Closed
cxposition opened this issue Dec 20, 2024 · 3 comments
Closed

The alarm cannot be triggered according to the specified rule. #6684

cxposition opened this issue Dec 20, 2024 · 3 comments

Comments

@cxposition
Copy link

Bug description

Set memory alarms. The alarm rules are as follows:
Image
The corresponding alarm chart is as follows:
Image
In this case, alarms are recorded only when the alarm is created and when the query-service service is restarted. It is unknown whether the fault is caused by the alarm rule configuration or back-end code processing. The alarm history is as follows:
Image

Expected behavior

When the threshold is always greater than the alarm value, a message is periodically sent to the channel.

How to reproduce

1.Create a webhook channel.
2.Create metrics-based memory alarms.
3.Observe the alarm triggering frequency and webhook email sending.

Version information

  • Signoz version: 0.61.0
  • Browser version: 131.0.6778.140(chrome)
  • Your OS and version: centos7
  • Your CPU Architecture(ARM/Intel): intel
@cxposition cxposition changed the title 告警规则长期低于告警阈值只在重启服务时触发告警,没有按照设定的周期触发告警 The calculated value of the alarm is always lower than the alarm threshold. The alarm is triggered only when the service is restarted Dec 20, 2024
@cxposition cxposition changed the title The calculated value of the alarm is always lower than the alarm threshold. The alarm is triggered only when the service is restarted The calculated value of the alarm is always below the alarm threshold, and the alarm is triggered only when the alarm rule is created and the service is restarted. Dec 20, 2024
@cxposition cxposition changed the title The calculated value of the alarm is always below the alarm threshold, and the alarm is triggered only when the alarm rule is created and the service is restarted. The alarm cannot be triggered according to the specified rule. Dec 20, 2024
@srikanthccv
Copy link
Member

When the threshold is always greater than the alarm value, a message is periodically sent to the channel.

When the alert moves to the firing state, a notification will be sent, now, if the alert still remains in the firing, no new notification will be sent for the next repeat interval (4 hours). This is expected behaviour, as your value is always above the threshold.

@cxposition
Copy link
Author

When the threshold is always greater than the alarm value, a message is periodically sent to the channel.

When the alert moves to the firing state, a notification will be sent, now, if the alert still remains in the firing, no new notification will be sent for the next repeat interval (4 hours). This is expected behaviour, as your value is always above the threshold.

Thank you very much for your answer.

@srikanthccv
Copy link
Member

Closing since your question is answered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants