This commit [Remove unused code · Checkmk/checkmk@80dcaab · GitHub] removed several open_ and close_ functions which I use in my own dashlets. In the 2.3-branch no alternative for these functions is available.
That’s the problem with using functions that are normally not available over some type of API. I had also such problems with function used for checks.
In the end you have to define your own replacements or workarounds.
And without code examples no one can say if there are workarounds already existing.
Hello Andreas,
Then I hope there will be a dashlet API soon. For endusers a drap&drop dashboard is ok, but how should developers build new dashlets for even better dashboards when functions are dropped every version. This happend from 2.0 to 2.1, 2.1 to 2.2 and now again. And it took me some time to find the “documentation”. A werk would have been a better way of telling customers what changed. At least for me the werks were the first source of information to find out what happend.
Greetings
Stefan
Hello Stefan!
As you know, previously there were no supported and stable developer API for both checks and dashlets. For this reason, starting with Checkmk 2.0 the overhaul of the Check API started, with Checkmk 2.3 bringing the v2 check API and well specified APIs for graphing: Update to version 2.3.0.
We are cleaning up APIs as part of this effort. A big problem for many developers were subtle changes to APIs that were never well specified, and changes such as this one are, unfortunately, necessary, for consistent further development.
The dashlet APIs are expected to go through the progress of transformation as well with cleanups having taken place to allow for an easier porting of our dashlets to new APIs in the future.
Nevertheless, we checked with our colleagues and if you are planning to participate in the Checkmk Conference this year, we might try to come up with some workaround solution at the developer clinic.
Hello Sara,
Looking forward to the conference now. Ticket is ordered.
Greetings
Stefan