Hey!
I’ve created an App for Check_MK and Mobile/Desktop devices.
DISCLAIMER: This requires lql-api installed on you’r check_mk server.
See it’s feature set in this video 
Download it here please open issues/feature requests on github issues.
4 Likes
Thank you @jochum !
Looks very promising and lql-api is great 
1 Like
I do not want to be a party pooper, but I think when developing an application, I would stick to the Checkmk REST API as much as possible. Also, how is the connection to Livestatus secured? Are you using the built-in encryption?
1 Like
@robin.gierse thanks for answering. You should use HTTPS for encryption for authentication we use check_mk’s http authentication.
Yes, in my Video I’m not using HTTPS because I don’t have a public IP here for letsencrypt.
About REST-API:
LQL-API is much more powerfull than REST-API but to be true, it’s been a while that I checked the docs of REST-API.
About LQL-API:
LQL-API is an HTTP/S bridge to the Livestatus socket, it uses the same authentication as check_mk by parsing the site’s Apache Httpasswd.
LQL-API is installed as https://monitor.fdqn.com/“site”/lql-api/
Okay, that resolves my concerns about transport encryption. 
I am not a developer, so I could not tell, which one is more powerful or fit for the job, or whatever you want to call it. My point is: The REST API is supported by us as the vendor, while installing things into a site would not be supported (it probably works, but can break during updates and could void commercial support).
That is all I got here, I was just airing some thoughts. You got a cool project going on and I do not wanna steal your thunder. Good luck and happy monitoring! 
P.S.: Usually third-party components should be installed into $OMD_ROOT/local/.
lql-api is not an omd component as it requires your systems Apache config to be altered. While thinking, that could be made possible.
Can you please clearify if lql-api will void commercial support?
I’ve just released v0.0.3 of letscheck:
- No more hard requirement on lql-api.
- Add’s notifications, this optional feature requires LQL-API on the Server!
- Lot’s of small bugfixes.
Downloads:
- letscheck: is available on Github Releases
- lql-api: is also available on Github Releases
EDIT: Released v0.0.5 with a bugfix.
1 Like
So in general Checkmk is very extensible and there are plenty of extensions out there. We as a company obviously cannot support those. So we only support the main product. If you have commercial support and need to open a ticket, we might require you to remove all third-party components at least temporarily to be able to troubleshoot the issue and understand, if it is a Checkmk issue or something in a third-party component.
TL;DR: Third-party components do not flat out void support, but they can become relevant in the troubleshooting process.
2 Likes
Hello Rene,
Looks quite interesting, thank you for your work. As soon as REST API is fully supported for iOS we definitely will have a look. Some hints how the code comes to the mobile device would also be helpful because I have no idea about iOS stuff.
keep going!
Michael
Thanks for you’r interest!
Can you please try one of the Desktop options from v0.0.5
I realy need feedback, LQL-API is NOT REQUIRED but currently the only available option to get notifications.
@robin.gierse thanks for detailed answer. So if i understand it right - install LQL-API and have maybe difficulties in troubleshooting.
Robin could you ask you’r Team why the “log” table isn’t available in REST-API? This is the one and only reason for LQL-API now.
Thanks,
René
After I replaced the CheckMK logo with something else payed Apple about 120 € for a developer license and have some testers I can Publish letscheck to the AppStores (Android/iOS/Windows/Mac).
2 Likes
The new Logo is done…
What do you guys think?
EDIT: it’s a draft
Regarding the logo:
The colours used seem to reference to colours used in the Checkmk brand, but the green is different. Which is good, since they don’t want you to Use these graphics as part of your own product, business, or service’s name
See: The Checkmk brand
The logo might work in dark mode, but if you want to use on light background, you might be in trouble losing part of the L. This can be fixed by putting the L completely inside the square.
And if you are willing to tweak with the L, maybe you can twist it counter clockwise a bit, so it also looks like an okay check mark. 
Make logo completely into a vector graphic for easy scaling. And you can use it as a custom font or svg, and then even use it inside your app when stuff is okay. 
2 Likes
I thought about having different icons per Theme, will rethink that.
I love that, many many thanks!
It’s already an export, sadly I can’t upload it here. I uploaded it into my repo
2 Likes
Hi Rene, many thanks for all the effort and money you spent on this.
I checked today Apple Appstor but didnt found letscheck. Do I need to look for a different name?
Thanks
Michael
Hey Michael,
there’s no release in the Stores yet.
Kind regards,
René
1 Like
LetsCheck is now available as PWA:
IMPORTANT: You need to enable CORS on you’r Checkmk proxy for this to work.
LetsCheck is available for Download here
1 Like
Just out of personal interest—since we discussed this via private message about two years ago—are you still planning to monetize this app and generate revenue as you mentioned back then? Or have you changed your mind and decided to keep it 100% open-source and free forever, with no additional paid features?
I’m asking to better understand whether your app might be a viable alternative to the bot we currently develop, maintain, and open-source within our company. If your app is guaranteed to remain open-source and free, it would be silly for us to continue investing effort in maintaining our bot when we could simply use yours.
Thank you!