[ZBXNEXT-5416] Decommission of Jabber and EZText mediatypes Created: 2019 Sep 10  Updated: 2019 Oct 28  Resolved: 2019 Oct 28

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: None
Fix Version/s: 4.4.0alpha3, 4.4 (plan)

Type: Change Request Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Martins Valkovskis
Resolution: Fixed Votes: 0
Labels: eztexting, jabber
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Causes
caused by ZBXNEXT-510 create a new media type for Ez Texting Closed
caused by ZBXNEXT-5386 Support of webhooks for actions Closed
caused by ZBXNEXT-2902 Media type : use of a loadable module Closed
caused by ZBXNEXT-1060 remove eztexting media type Closed
caused by ZBXNEXT-2842 Alternative jabber library Confirmed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-5420 (frontend) Decommission of Jabber and... Change Request (Sub-task) Closed Alexander Vladishev  
Team: Team D
Sprint: Sprint 56 (Sep 2019)
Story Points: 0.5

 Description   

1. Remove support of EzTexting and Jabber media types
2. If used then replace them with media type Script with all relevant parameters preserved and empty or dummy script name.
3. Make this information visible in release notes
 
Scope of DB migration - move mediatypes and all parameters to exteranl scrip, db cleanup from unused fields. Creation of scripts is out of scope.



 Comments   
Comment by Alexander Vladishev [ 2019 Sep 11 ]

Available in dev branch feature/ZBXNEXT-5416-4.3

Comment by dimir [ 2019 Sep 11 ]

Suggestion from community. Why not leave Jabber support in server code, without offficially supporting it? People that are using it now could continue doing it so building manually libiksemel library.

Comment by Alexander Vladishev [ 2019 Sep 11 ]

But then we need to leave Jabber support both in the user interface and in the API code. Otherwise, it will be impossible to configure it. Better use scripts to send messages to Jabber.

You also need to take into account that in packages we are not support Jabber library.

Comment by Alexei Vladishev [ 2019 Sep 11 ]

Dimir, keeping dead unsupported code in the main codebase is not good. We've been there, it has never worked well.

Comment by Denis Golius aka Terry Filch [ 2019 Sep 11 ]

But what about https://support.zabbix.com/browse/ZBXNEXT-5372 ?

Comment by Alexei Vladishev [ 2019 Sep 11 ]

Denis, sorry I don't get what you are asking.

Comment by Denis Golius aka Terry Filch [ 2019 Sep 11 ]

I mean, that Zabbix Team will add import/export for media types instead supporting Jabber/etc old media types in Zabbix Core?

Comment by Alexei Vladishev [ 2019 Sep 11 ]

Denis, both ZBXNEXT requests are fully independent and will be delivered in Zabbix 4.4.

Comment by Mikhail Grigorev [ 2019 Sep 11 ]

There is a fork of the iksemel library that is developing
https://github.com/timothytylee/iksemel-1.4
but unfortunately most of the CentOS, Debian, Ubuntu distributions use the original and old library, most likely they are not aware that there is a fork.

Comment by Glebs Ivanovskis [ 2019 Sep 11 ]

Dear palivoda, regarding Description.

2. If used then replace them with media type Script with all relevant parameters preserved and empty or dummy script name.

What kind of error messages this dummy script will result in? "Cannot send notification: script 'dummy' not found"?

I think preserving media types will help produce better error messages when deprecated media types are used.

Comment by Glebs Ivanovskis [ 2019 Sep 11 ]

Dear cherts, 0 stars, 1 watcher (repository owner), 1 open issue and 1 closed issue — I wouldn't call it "developing".

Comment by Alexander Vladishev [ 2019 Sep 14 ]

Available in:

Comment by Alexander Vladishev [ 2019 Sep 24 ]

Updated documentation:

Comment by Glebs Ivanovskis [ 2019 Sep 24 ]

If these media types are present in your existing installation, during the upgrade they will be replaced by a script media type with all relevant parameters preserved.

This phrase leaves an impression that user has nothing to worry about. One may think "No Jabber, but at least there is a script media type and all the parameters are preserved. Seems fine!" I think Upgrade Notes should be very explicit about the fact that notifications via Jabber and EZText will stop working.

Comment by Martins Valkovskis [ 2019 Sep 24 ]

Thanks, the updated wording is clear that the notifications via Jabber/EZ Texting will not work any more.

Generated at Fri Mar 29 13:14:39 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.