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

Receiving alert messages with Feishu is very slow #145

Open
Bennu-Li opened this issue May 13, 2022 · 3 comments
Open

Receiving alert messages with Feishu is very slow #145

Bennu-Li opened this issue May 13, 2022 · 3 comments
Assignees

Comments

@Bennu-Li
Copy link
Contributor

Bennu-Li commented May 13, 2022

Using curl to access the /api/v2/alerts interface to send notifications to Feishu, it takes about 40 seconds. I also tried using prometheus alertmanager as the sender, it's also slow.
Is this normal and what can be done to improve it?

@Bennu-Li Bennu-Li changed the title Receiving alert messages with Fishu is very slow Receiving alert messages with Feishu is very slow May 14, 2022
@DesistDaydream
Copy link

This is a normal phenomenon. NM is asynchronous. When an alarm is received, it will be pushed to the Provider, and then the Dispatcher will pull the alarm from the Provider and perform notification operations in multiple stages.

@benjaminhuo
Copy link
Member

@wanjunlei Do we have a wait period before actually sending the alert to feishu ?

@wanjunlei
Copy link
Collaborator

The following situations can cause delays.

First, the Notification Manager handles the incoming alerts with a batch processing mechanism.
The incoming alerts will not be processed immediately but will be cached for a period of time, the default is 1 minute. So this will cause a delay of no more than 1 minute. You can change this time follow this.

kubectl edit nm notification-manager

And change the spec.batchMaxWait.

Second, if you send notifications to Feishu users or departments, it will have an indeterminate delay. The reason is that sending notifications to the user is an asynchronous operation, and the Feishu server determines this delay.

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

4 participants