Replies: 3 comments
-
|
The issue you're experiencing with service warnings from Checkmk not displaying in Keep's Alert history was previously identified and addressed. The problem was that service alerts from Checkmk were always shown with a 'Resolved' status in Keep's alert table, which has been fixed in Keep through PR #3111. To resolve this issue, ensure that your Keep instance includes this fix. Additionally, verify that the Checkmk provider is correctly configured to map service alerts and host alerts based on their respective fields. This includes setting up the webhook and mapping severities and statuses correctly as per the Keep documentation [1][2]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
-
|
I saw in issue #3111 that the Alert table status column issue was resolved. But this issue is a different problem, maybe they are related but the situations that users encounter are not the same. |
Beta Was this translation helpful? Give feedback.
-
|
solved with clearing the cache of the browser. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
When I look closely at the Alert history in the Alert panel in Keep, I see that the information sent from checkmk is blank, I think it is a bug, please help me review this issue.
This problem only occurs in services in checkmk and not in hosts in checkmk
To Reproduce
Steps to reproduce the behavior:
But the Host's history is still displayed correctly.
Expected behavior
I think, if it works properly, the Alert history section should display all news reports from checkmk on Keep. Please verify and double check for me.
Screenshots
Additional context
I observed that the problem is only caused by service warnings from checkmk, but host warnings from checkmk are still working properly.
Beta Was this translation helpful? Give feedback.
All reactions