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

SIGNL4 Notification Plugin Update #603

Closed
wants to merge 7 commits into from
Closed

SIGNL4 Notification Plugin Update #603

wants to merge 7 commits into from

Conversation

rons4
Copy link
Contributor

@rons4 rons4 commented Jun 27, 2023

Thank you for your interest in contributing to Checkmk!
Consider looking into Readme regarding process details.

General information

This is an update of the SIGNL4 notification plugin for better support for service alerting and two-way status updates.
We are the provider of SIGNL4.

If you should have any questions please just let me know.

rons4 and others added 4 commits January 7, 2021 16:34
# Fixed Range Check

I realized that SIGNL4 notifications fail in beta 3 with "Details for Status Code are not defined -- 201: Created". However, 201 should be success.

The reason seems to be that the line:
if status_code in status_code_range:
returns true for 200 and 299. But the line
if status_code_range[0] <= status_code <= status_code_range[1]:
returns true for any value between 200 and 299.

The change should make sure that all 2xx status codes are processed as success.

I hope this makes sense and I did not miss anything.
Updated SIGNL4 notification plugin for better support of service alerting and two-way status updates.
Updated SIGNL4 notification plugin for better support of service alerting and two-way status updates.
@github-actions
Copy link

github-actions bot commented Jun 27, 2023

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@rons4
Copy link
Contributor Author

rons4 commented Jun 27, 2023

I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA.

@rons4
Copy link
Contributor Author

rons4 commented Jun 27, 2023

recheck

3 similar comments
@rons4
Copy link
Contributor Author

rons4 commented Jun 27, 2023

recheck

@rons4
Copy link
Contributor Author

rons4 commented Jun 27, 2023

recheck

@rons4
Copy link
Contributor Author

rons4 commented Jun 28, 2023

recheck

cmk/notification_plugins/signl4.py Show resolved Hide resolved
cmk/notification_plugins/signl4.py Show resolved Hide resolved
cmk/notification_plugins/signl4.py Show resolved Hide resolved
@rons4
Copy link
Contributor Author

rons4 commented Oct 25, 2023

Sorry for the confusion. I checked the code again and we don't just use the service description for matching, we already use a combination of several values.

"X-S4-ExternalID": "Checkmk: "
+ host_name
+ "-"
+ host_problem_id
+ "-"
+ service_problem_id
+ service_desc_id_part,

We use this for matching and for sending updates from our side (SIGNL4) back to Checkmk.

I hope this is fine then.

@makanakoeln
Copy link
Contributor

merged today. Thanks for contributing

@github-actions github-actions bot locked and limited conversation to collaborators Oct 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants