The folks at Globility have been very kind to release back to the Ignite Realtime community their improvements to the Openfire monitoring plugin.
They have merged the monitoring plugin with the open archive plugin by@ Stefan Reuter and have sucessfully combined chat and group chat archiving (from monitoring) as well as XEP-0136 Message Archiving support (from open archive) removing all redundant and duplicated code. The monitoring graphing and statistics pages work just fine as before.
A change to the database schema of the Monitoring plugin was made to support the XEP-0136 spec and auto-upgrade DB scripts have been provided to handle the database upgrade for all the supported DBs as best as possible.
Latest build (1.3.0) of the plugin is attached. Any bugs please file in JIRA against leonroy
I have tested it against the latest version of OfChat (Chrome extension) web client as a drop-in replacement to the open archive plugin for chat history and it works ok.
Good news. I hope this pluginās bugs have been fixed in the process, or at least we have whom to send the reports to I always had doubts suggesting this plugin to users as it have stopped working for me few times with no reason and there were more reports in the forums.
Is this jar already useable for a clustered setup? I tried it and the monitoring tabs donāt appear. Iām not sure if it is an issue with my setup or not.
Glad to hear the new pluginās working better for you all.
TBH the monitoring plugin has always had issues displaying some of the tabs, even with Openfire 3.6.4. Iām not sure why, but at a basic level weāre focusing on getting the core, auto chat archiving and xep-0136 support to be bullet proof.
Please file any bugs in JIRA though and weāll try to fix them ASAP.
In the meanwhile weāll take a look at the below as a high priority:
Since installing the new monitoring plugin, when archving Group Conversations the participants name in the chat body comes up as ānullā
Hi all, known issue that 1.3.0 did not save messages properly. Please see the following topic for 1.3.1 which resolves the issue (it is Openfire 3.8 only though):
I think this is because ofMessageArchive table is redesigned, separating resource from JID. The label on jsp page displays resource which the plugin should get from toJIDResource instead of toJID.