MKP Parameters in Checkmk 2.4

Hi there,

I have an MKP (SIGNL4) and when I add this one in Checkmk 2.4.0p4 it seems I cannot configure the parameter:

It says a field is empty which it is not:

Without migrating the existing parameter I get the following error:

An unexpected error occurred:

Internal Server Error: TypeError: not all arguments converted during string formatting. Crash report generated. Please submit.
Refresh the page to try again. If the problem persists, reach out to the Checkmk support.

Details
CmkError: Internal Server Error: TypeError: not all arguments converted during string formatting. Crash report generated. Please submit.

GET http://192.168.2.99/checkmk4/check_mk/api/1.0/objects/notification_parameter/a85eb313-4590-4c73-bb21-97191c4d85ea
STATUS 500: INTERNAL SERVER ERROR

Crash report: http://192.168.2.99/checkmk4/check_mk/crash.py?crash_id=eb92ab8c-47a1-11f0-b6d4-080027f22a9c&site=checkmk4

CmkError: Internal Server Error: TypeError: not all arguments converted during string formatting. Crash report generated. Please submit.
    at $_.getError (http://192.168.2.99/checkmk4/check_mk/cmk-frontend-vue/assets/main.js-DMhO1VyL.js:69:327)
    at $_.raiseForStatus (http://192.168.2.99/checkmk4/check_mk/cmk-frontend-vue/assets/main.js-DMhO1VyL.js:68:3241)
    at Object.getData (http://192.168.2.99/checkmk4/check_mk/cmk-frontend-vue/assets/main.js-DMhO1VyL.js:98:34565)
    at async Object.getData (http://192.168.2.99/checkmk4/check_mk/cmk-frontend-vue/assets/main.js-DMhO1VyL.js:98:35712)
    at async Promise.all (index 0)
    at async c (http://192.168.2.99/checkmk4/check_mk/cmk-frontend-vue/assets/main.js-DMhO1VyL.js:98:31516)

Do you have any idea how to fix this in the MKP file?

SIGNL4 is natively available as a notification channel in Checkmk and this works fine.

Also, the GUI part of the MKP is marked as deprecated:

I understand the config parameters should not be Python anymore but YAML. Can you please point me to a documentation or sample for this YAML configuiration?

Thanks a lot

Ron

Just a quick and stupid thought: Can you re-type the value in the input field, where it complains?

1 Like

Yea, good idea to try that but I think I tried before and I tried it again now but it did not work.
I also created a new notification rule with the same result.