|
The first specifications draft is available at https://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-2033
|
|
The initial implementation according to the specifications draft can be found in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033
<dimir> UPD, latest one: https://git.zabbix.com/projects/ZBX/repos/zabbix/commits?until=refs%2Fheads%2Ffeature%2FZBXNEXT-2033_349
|
|
[F] Added possibily to add media type "Remedy Service" via frontend and API. See dev branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033
<dimir> UPD, latest one: https://git.zabbix.com/projects/ZBX/repos/zabbix/commits?until=refs%2Fheads%2Ffeature%2FZBXNEXT-2033_349
|
|
(1) [F] CMediaType:
- CMediaType create/update validation on Super Admin permissions must be inside validateCreate() and validateUpdate()
- $mediaTypes = zbx_toArray($mediaTypes); must be before validation and inside validateCreate() this is not needed
- CMediatype.php:362 - better to use API::getApi()->select(), also output fields must be specified
- CMediatype.php:362 - require to get data once for all media types
- validation on description length must be after validate on unique
- if we get data from database will be good to write prefix in variables names, for example $dbMediaTypeExists = $this->get(array(...
- CMediatype.php:517 - validateRequiredFieldsByType() will be good rename to checkRequiredFieldsByType() to keep API naming
- CMediatype.php:522 - variable $requiredFieldsByType can be defined with all keys at once
- messages in validation on require field in validateCreate() and validateUpdate() are different
- CMediatype.php:439 - will be good if variable $mediaTypesDb rename to $dbMediaTypes
- CMediatype.php:464 - not sure that validation on description size is need, if need, with one error message will be enough
iivs RESOLVED in r40985
Eduards CLOSED
|
|
(2) [F] New function fieldToString() must be renamed. Inside this function value from getRequest('type') must be passed as function parameter.
iivs RESOLVED in r40986
Eduards CLOSED
|
|
(3) [F] Why "localhost" is default value for Remedy Service URL and Proxy in create event?
iivs it was due to data submitting, because we use same fields.
RESOLVED in r41069
Eduards REOPEN, Suggest instead of javascript templates used data-* attributes to set default values and active use disable/enable, show/hide javascript methods
iivs Instead of data-* attributes, I make it possible with new fields and 'ViewSwitcher'.
RESOLVED in r41182
Eduards REOPEN, Password field broken in edit mode (see mediatype-passwd.png)
- duplicate code in js can be removed using trigger('change')
- redundant variable $cmbTypeRow in administration.mediatypes.edit.php:50
- media_types.php:141-187 can be optimized
- redundant empty lines in CMediaType API
- please compare strings in strict mode
iivs RESOLVED in r41303
Eduards REOPEN
Undefined index: passwd [ in /home/zabbix/www/ZBX-TESTING/frontends/php/media_types.php:182]
iivs RESOLVED in r41329
Eduards CLOSED
|
|
(4) [F] "Change password" button must have the same style like in user password change.
iivs RESOLVED in r41567
Eduards CLOSED
|
|
Created a prototype script to import CI RefconID values into host inventory tag field. (import.pl attached)
|
|
(5) [F] A new field should be added to media type configuration - Services mapping. It will point to a value mapping used to map Remedy services to Zabbix groups and should be stored into media_type.smtp_email field.
iivs RESOLVED in r42248
Eduards REOPEN
- please return previous code of parameters defining in save action, it was more correct. At now for several variables value defines two times.
- will be good to set size (255) of new field in "new TextBox()"
iivs
Width is strandart size like other input fields and maxlength 255 is already by default. Nothing to change there.
Reverted some changes : RESOLVED in r42274
Eduards CLOSED
|
|
(6) [F] Implemented Remedy ticket creation and update when acknowledging events through frontend. Added Remedy ticket information in event details page.
RESOLVED in r42797-r42827
Eduards REOPEN
- CZabbixServer.php:164,182 - input arrays must be defined as array input parameter
- acknow.php:191 isset($event) - this is bad coding style to somewhere define variable and somewhere with isset() check if it exist (discussed with Sasha)
- acknow.php:137 - redundant code $remedyService = reset($remedyService);
- acknow.php:148 - please rename $mediaQuery to $ticket
- acknow.php:150 - if server return error will be good to display it
- acknow.php:155 - redundant check if exist array field "error" isset($mediaQuery[$eventId]['error'])
- acknow.php - if action is "save" we query server two times instead of one
iivs RESOLVED in r43029
Eduards REOPEN
- acknow.php - $ticketLink also must be defined in the beginning
iivs RESOLVED in r43050
Eduards
- acknow.php:264 - undefined index if ticked for actual eventid doesn't exist
- links to outside ticked system must be open in new window (discussed with Pavel)
iivs I will not receive undefined index, since server will return all indexes including existing event. If ticket is not created, simply 'externalid' will be empty, but eventid will still exist, because we open page from existing event. That's why I used line 261 to make it easier to access returned ticket data.
Links in new windows RESOLVED in r43062
Eduards CLOSED
|
|
(7) [F] Please define in specification ZBX_SOCKET_REMEDY_TIMEOUT value
iivs Specification updated.
I also changed default timeout to 10 seconds like on server side.
RESOLVED in r43039
Eduards CLOSED
|
|
(8) It user don't want to update ticked and stay in acknowledge page label changes to "Create ticked"
iivs I moved Remedy service operations to special class. I also added assignee and status in acknowledge and event details page.
RESOLVED in r43075-r43100, code refactoring and checkbox reset as we discussed in r43101-r43103
Eduards CLOSED
|
|
(9) [F]
- tr_event.php:124 - redundant reset
- tr_event.php:145 - redundant isset on error
- in aknowledge page ticket is called "Ticked" but in event details page "Ticked ID". Will be nice to call it also simply "Ticked". Specification also must be updated. Discussed with Pavel.
iivs RESOLVED in r43063
Eduards CLOSED
|
|
(10) [F] After unsuccessful acknowledgement of event (server error), checkbox is displayed. Also 10 seconds timeout connection is sometimes not enough. Timeout is now set to 20 seconds.
RESOLVED in r43114
See minor improvement on error message handling ir r43126 and (12) for additional error message fix.
Eduards CLOSED
|
|
Hello, sorry about this newbie question, but what i need to do to use this integration on my installed Zabbix 2.2.2 ? Do you have any procedure to install? Thank you so much.
|
|
You would need to build server, take frontend from this development branch (svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033). But the initial version is tailored for a specific use case, so it's not ready for general use.
|
|
(11) [F] Non super-admins can't get own mediatype due to permission limitations
iivs RESOLVED in r43607
Eduards CLOSED
|
|
(12) [F] If Zabbix server is offline, error message is displayed at the bottom. Function hasErrorMessages is wrongly written with inverse meaning.
Added better error message display and fixed function hasErrorMessages.
RESOLVED in r43593
Eduards CLOSED
|
|
(13) [F] Populate "Summary" field in Remedy Service with trigger name instead of trigger status
wiper I believe they want to see trigger name and event status. Currently it displays trigger status, so acknowledging a problem event of trigger that is already in OK state gives 'OK' subject, which is wrong.
iivs I also changed display of checkbox to not show when in OK state and no ticket was created.
RESOLVED in r43609, changed trigger status to event status in r43636
Eduards CLOSED
wiper At the end they decided to have only trigger name in incident summary. REOPENED
iivs RESOLVED in r43791
Eduards CLOSED
|
|
(14) [F] Link to Remedy Service is defined in two places. One in Administration > Media type configuration and second in defines. Both are different. Second one points to ticket. Get base http link from media type configuration and add additional params from defines.
iivs RESOLVED in r43611
Eduards REOPEN
Undefined indexes if media type Remedy Service URL is "localhost"
Undefined index: scheme [acknow.php:131 → CRemedyService::init() in /home/zabbix/www/ZBX-TESTING/frontends/php/include/classes/remedy/CRemedyService.php:70]
Undefined index: host [acknow.php:131 → CRemedyService::init() in /home/zabbix/www/ZBX-TESTING/frontends/php/include/classes/remedy/CRemedyService.php:76]
wiper I also got this error when opening acknowledge window by user without defined Remedy media
iivs Note that it should start with http and end with slash, to work properly.
RESOLVED in r43792, r43795 (added media check fo specific user and it media is enabled)
Eduards CLOSED
|
|
(15) [F] display "Create ticket" when incident status is "Closed" or "Cancelled"
iivs RESOLVED in r43675, r43677
Eduards CLOSED
|
|
(16) [F] Require to check media type status
iivs RESOLVED in r43792, r43795 (added media check fo specific user and it media is enabled)
Eduards REOPEN
CRemedyService.php:80 - We can't call zbx_toHash() because 'userid' in this array is not unique
$mediaType['media'] = zbx_toHash($mediaType['media'], 'userid');
iivs We decided to get first active media. RESOLVED in r44154
Eduards CLOSED
|
|
(17) [I] Proxy compilation error
RESOLVED in r43803
asaveljevs Proxy does not compile by itself, without server:
$ mk
make[3]: *** No rule to make target `../../src/libs/zbxmedia/libzbxmedia.a', needed by `zabbix_proxy'. Stop.
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
asaveljevs Why do we need libzbxmedia.a for proxy? REOPENED.
wiper No, but it was decided to keep it simple instead of reorganizing trapper code into server/proxy specific parts.
asaveljevs Since the branch does not represent a generic solution for now, it was decided to leave as is for now. WON'T FIX.
|
|
(18) If a host does not have inventory turned on, it tries to send a Remedy alert, but fails and error message is empty.
wiper RESOLVED in r44258. Also added few more error messages.
|
|
(19) Enabled feature list in Zabbix server log file should probably include Remedy support, same as Ez Texting.
wiper RESOLVED in r44688
|
|
(20) The order of table "ticket" fields is different between dbschema.c and upgrade patch. Also, "triggerid" field in the patch references "triggers" table, whereas in dbschema.c it does not. Finally, the default value settings for "externalid", "clock", and "new" are different, too.
wiper RESOLVED in r44220
|
|
(21) The "Comments" section for remedy_get_service_by_host() does not seem to be relevant anymore.
wiper RESOLVED in r44223
|
|
(22) There may be multiple events in the same seconds, that is why "events" table contains both "clock" and "ns". For this reason, multiple tickets may be created in the same second. Why "ticket" table only has "clock", but no "ns"?
wiper The clock is used in two cases:
1) passed to frontend to display incident creation date/time
2) used to find the last created incident for a specific trigger/event
In the first case we don't need ns, but in the second case theoretically even ns might not be enough. Maybe we should change the logic by simply picking the last incident by ticketid.
wiper After discussion it was decided that adding ticketid to order (clock,ticketid) will be enough to satisfy the second case.
RESOLVED in r44687
|
|
(23) In function remedy_create_ticket(), "loginid" should be escaped.
wiper RESOLVED in r44228
|
|
(24) When previous incidents for a trigger have been resolved, a new incident is created even when a Remedy action is disabled.
asaveljevs This happened because there was another action that sent a message to all media, not just email. WON'T FIX.
|
|
(25) Please take a look at my code review changes in r44122. Mostly style, but some minor bugs, too.
wiper thanks, CLOSED
|
|
(26) Zabbix_server crashes - in "alerter [sending alerts](zbx_remedy_process_alert+0x67)".
wiper Backtrace:
8414:20140406:212523.592 === Backtrace: ===
8414:20140406:212523.605 10: /usr/local/sbin/zabbix_server: alerter [sending alerts](print_fatal_info+0x10b) [0x468d1b]
8414:20140406:212523.605 9: /usr/local/sbin/zabbix_server: alerter [sending alerts]() [0x4695bf]
8414:20140406:212523.605 8: /lib64/libc.so.6(+0x32bf0) [0x7f38f85afbf0]
8414:20140406:212523.605 7: /usr/local/sbin/zabbix_server: alerter [sending alerts]() [0x46dc93]
8414:20140406:212523.605 6: /usr/local/sbin/zabbix_server: alerter [sending alerts](zbx_remedy_process_alert+0x67) [0x46edb7]
8414:20140406:212523.605 5: /usr/local/sbin/zabbix_server: alerter [sending alerts](execute_action+0x98) [0x41ab88]
8414:20140406:212523.605 4: /usr/local/sbin/zabbix_server: alerter [sending alerts](main_alerter_loop+0x26e) [0x41b11e]
8414:20140406:212523.605 3: /usr/local/sbin/zabbix_server: alerter [sending alerts](MAIN_ZABBIX_ENTRY+0x972) [0x41a202]
8414:20140406:212523.605 2: /usr/local/sbin/zabbix_server: alerter [sending alerts](daemon_start+0x1b2) [0x468292]
8414:20140406:212523.605 1: /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f38f859bc36]
8414:20140406:212523.606 0: /usr/local/sbin/zabbix_server: alerter [sending alerts]() [0x414b99]
Objectdump fragment:
if (0 == strcmp(status, ZBX_REMEDY_STATUS_RESOLVED))
46dc84: 48 8d 3d 0a 3d 06 00 lea 0x63d0a(%rip),%rdi # 4d1995 <__PRETTY_FUNCTION__.21996+0x1185>
46dc8b: b9 09 00 00 00 mov $0x9,%ecx
46dc90: 48 89 c6 mov %rax,%rsi
46dc93: f3 a6 repz cmpsb %es:(%rdi),%ds:(%rsi)
46dc95: 0f 85 0d 03 00 00 jne 46dfa8 <remedy_process_event+0x4d8>
wiper Judging from the above apparently there can be a case when HelpDesk_Query_Service can return incident data without status field. Probably the best would be to handle as canceled incident.
wiper RESOLVED in 44235
wiper Treating such situation as canceled incident might not be a good idea (until it's clear why and how often such situation might happen). In this case it would be better to treat is as an error. Waiting for more input from client.
REOPENED
wiper It was decided to fail the incident update if Query_Service did not return status field. RESOLVED in r44268
|
|
(27) [S] server should use custom HPD_Incident_Interface_Create_Monitor_WS interface when creating a new incident to provide Service Class field. This field is taken from host inventory serialno_b field, where it is imported with an external script similarly to reconid field.
RESOLVED in r45433
|
|
Remedy development changes merged development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_224 based on 2.2.4 version.
|
|
(28) Zabbix server is continually crashing in alerter - /usr/local/sbin/zabbix_server: alerter [sending alerts](zbx_remedy_process_alert+0x67) [0x473a37]. It can be related to a maintenance window of the BMC server.
wiper It appears that the server got an incident without status field again. I remember fixing it before, but did not apply the check to all possible places. RESOLVED in r51496
|
|
Remedy related server changes merged to 2.4.4 and available at svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_244
|
|
(29) [F] Merge Remedy related frontend changes to at svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_244
iivs RESOLVED in r52462
|
|
what is the status of this ticket? how was it resolved? what is being done to resolve it? Personally auto-generated tickets from monitoring events is often more trouble than it's worth. I'd rather see the ability to link to a remedy incident creation screen from inside Zabbix. It would be great if zabbix auto-populated the incident creation form, but final decision to send to remedy should be a person's.
|
|
Currently it's done as separate project. The plan is to merge it into main trunk in some form, but the current implementation is based on customer specific configuration - it's not quite clear how to generalize it.
Regarding the second question - I think https://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-2033#Acknowledging_events answers to it. Shortly - there is an option to create/update incident by acknowledging an event in Zabbix.
|
|
Patched in remedy support to v3.0.3 (server side) in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_303
|
|
(30) [F] Integrated Remedy service into 3.0.3 in svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_303 r60642
|
|
good morning sorry for the inconvenience but could you give me a hand have to do my open zabbix called the remedy could give me more details of how you did
|
|
Zabbix 3.0.3: it is not possible to open event's details if remedy integration media is enabled:
[Sat Sep 10 12:45:20 2016] [error] [client 10.10.10.10] PHP Fatal error: Class 'CUIWidget' not found in /www/zabbix/tr_events.php on line 115, referer: http://zabbix_server/zabbix/events.php?filter_set=1&triggerid=267980&source=0&stime=20160910120752&period=3600
|
|
Sirs, good evening
I'm having trouble creating the media type that is selected as shown in the image Type: "Remedy Services" could help me please.
|
|
Hello, kelion!
Would you please give us more details about the problem you're experiencing and steps how to reproduce the promblem? Because the image is almost 3 years old and it's built on Zabbix 2.2.
|
|
Hello good Morning,
I have installed zabbix 3.0.5 precise integral with the remedy so that when events occur in zabbix open tickets in the remedy.
I saw here that you had to be creating a type of media with the following data
Remedy Service URL - the URL of Remedy web service (smtp_server)
User name - the Remedy Service user name (username)
Password - the Remedy Service user password (passwd)
Proxy - the proxy connection string (smtp_helo)
Company name - the Company name (exec_path)
Network group - the name of group mapped to Remedy 'Networks & Telecomms' service CI (smtp_email)
I tried to create via zabbix api but when I create it comes in the format of the email media, not with the items you need.
Plus the goal and that there is an event in zabbix open a new ticket in the remedy.
|
|
Currently Remedy support is not merged in the main branches because of custom development. The latest branch is based on Zabbix 3.0.3 version (svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_303). But it's quite possible Remedy incident creation would fail because of specific field requirements.
|
|
Good afternoon, going to thank I was able to create the type of media based on svn: //svn.zabbix.com/branches/dev/ZBXNEXT-2033_303, the tip I was not able to access until downloading the client Tortoisesvn we will be testing from here a few days. Thank you for the help.
|
|
(31) [F] Add a way for users to check incident status without being able to create/update incidents.
This will be done by checking user media severity. The incident information will be displayed with any severity settings, while the user will be allowed to update incident only when corresponding media serverity has been set. For other users the update checkbox will be disabled.
iivs RESOLVED in r64682
|
|
Hi,
Was anyone able to make this work properly and interface Zabbix with ITSM ?
I have installed a POC with v3 of Zabbix and copied the frontend from this branch to the POC and I am able to see the media type and configure it..
I think there are a couple of things to add in the database and maybe some other things I am missing.
Can we have overall steps to make this work ? This is currently a show stopper for my company to use Zabbix as I need to integrate to ITSM to open incidents..
I am about to make my own scripts but if I can make this work, even if it is in developement, it would help me a lot.
|
|
Integration is done, closing the issue.
We will keep the integration it up to date on customer request basis - we create new JIRA issue for each invoice statement.
Next migration to 3.2.5 is under ZBXNEXT-3767.
|
|
Where can I get a copy of this frontend as I need to look at ITSM integration through web services from a client also will it work on 3.2.11
I have looked all over and cannot find a copy of the frontend
Thanks
|
|
Hello, vlam! You can find it in branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-2033_32
It should work for 3.2.11.
|
|
Thanks Ivo, got and installed it
When I use it I get an error "Unsupported media type [101]"
Where can I look for waht can be the cause of this?
Thanks
|
|
Remedy support is based on specific customer requirements and is available only in dev branches. So for it to work You need to use the dev branch version.
|
|
Thanks Andris
One last question though, If I have an existing 3.2.11 running in the environment and I compile from the dev code will that effect my existing data as my DB for this client is on 500GB and a years data?
Thanks
|
|
It won't work on existing databases because ticket table will not be created by automatic database upgrade patches. This development was forked from v2.2 - so only v2.2 database would be successfully upgraded.
If you manually create ticket table, then it would work, but the 3.2 remedy integration branch is based on 3.2.7 - so any 3.2.7-3.2.11 fixes would be lost.
And finally I'm not sure that it would work with your remedy setup because of specific remedy fields and their contents. At leat that is easy enough to check - create fresh installation from remedy dev branch and check it it works for you.
|
|
I made a clone of my system and started the process but when I do my make I get the following
Making all in zbxdbhigh
make[3]: Entering directory `/root/ZBXNEXT-2033_32/src/libs/zbxdbhigh'
make[3]: *** No rule to make target `dbschema.c', needed by `libzbxdbhigh_a-dbschema.o'. Stop.
make[3]: Leaving directory `/root/ZBXNEXT-2033_32/src/libs/zbxdbhigh'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/ZBXNEXT-2033_32/src/libs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/ZBXNEXT-2033_32/src'
make: *** [all-recursive] Error 1
My command for configure was:
./configure --enable-server --enable-agent --with-mysql --with-net-snmp --with-libcurl --with-libxml2
Is there something that I am missing?
Thanks
|
|
After configure you have to manually do make dbschema before make all. Only in latest version it's done automatically.
|
|
Thanks Andris
I got all installed and configured on my side, from what I see all looks good. When sending an action via this media is there a specific structure that the action default message should have?
also when testing is there some how to a way to have it send to logs to see iff it works or not?
Lastly does it use API or does it use SOAP?
Thanks
|
|
No special structure for action subject/body.
You can switch debug logging and check End of remedy_query_ticket() ..., End of remedy_create_ticket() ... and End of remedy_modify_ticket() ... log records.
|
|
Thanks for that
I get the following when I look in the logs but I am not sure where the problem is at this stage. I do know I do net get a inc no from ITSM but is my message being send successfully to ITSM if you look at the logs?
107482:20180830:131502.672 In zbx_remedy_process_alert()
107482:20180830:131502.672 In remedy_process_event()
107482:20180830:131502.683 End of remedy_get_ticket_by_eventid():FAIL
107482:20180830:131502.684 In remedy_get_ticket_by_triggerid() 13491
107482:20180830:131502.693 End of remedy_get_ticket_by_triggerid():FAIL
107482:20180830:131502.695 In remedy_get_service_by_host() Automated
107482:20180830:131502.696 End of remedy_get_service_by_host():Server & Storage (OI-f9bee1dac03044f894ed43937bdc52dc)
107482:20180830:131502.696 In remedy_create_ticket()
107482:20180830:131503.492 End of remedy_create_ticket():FAIL 'Cannot retrieve incident number from Remedy response'
107482:20180830:131503.492 End of remedy_process_event():FAIL
107482:20180830:131503.493 End of zbx_remedy_process_alert():FAIL
107482:20180830:131533.524 In zbx_remedy_process_alert()
107482:20180830:131533.524 In remedy_process_event()
107482:20180830:131533.525 End of remedy_get_ticket_by_eventid():FAIL
107482:20180830:131533.525 In remedy_get_ticket_by_triggerid() 13491
107482:20180830:131533.525 End of remedy_get_ticket_by_triggerid():FAIL
107482:20180830:131533.526 In remedy_get_service_by_host() Automated
107482:20180830:131533.527 End of remedy_get_service_by_host():Server & Storage (OI-f9bee1dac03044f894ed43937bdc52dc)
107482:20180830:131533.527 In remedy_create_ticket()
107482:20180830:131533.599 End of remedy_create_ticket():FAIL 'Cannot retrieve incident number from Remedy response'
107482:20180830:131533.599 End of remedy_process_event():FAIL
107482:20180830:131533.599 End of zbx_remedy_process_alert():FAIL
107482:20180830:131603.614 In zbx_remedy_process_alert()
107482:20180830:131603.615 In remedy_process_event()
107482:20180830:131603.616 End of remedy_get_ticket_by_eventid():FAIL
107482:20180830:131603.617 In remedy_get_ticket_by_triggerid() 13491
107482:20180830:131603.618 End of remedy_get_ticket_by_triggerid():FAIL
107482:20180830:131603.619 In remedy_get_service_by_host() Automated
107482:20180830:131603.620 End of remedy_get_service_by_host():Server & Storage (OI-f9bee1dac03044f894ed43937bdc52dc)
107482:20180830:131603.621 In remedy_create_ticket()
107482:20180830:131604.206 End of remedy_create_ticket():FAIL 'Cannot retrieve incident number from
Remedy response'
107482:20180830:131604.206 End of remedy_process_event():FAIL
107482:20180830:131604.206 End of zbx_remedy_process_alert():FAIL
107482:20180830:131734.227 In zbx_remedy_process_alert()
107482:20180830:131734.227 In remedy_process_event()
107482:20180830:131734.228 End of remedy_get_ticket_by_eventid():FAIL
107482:20180830:131734.228 In remedy_get_ticket_by_triggerid() 13491
107482:20180830:131734.229 End of remedy_get_ticket_by_triggerid():FAIL
107482:20180830:131734.229 End of remedy_process_event():SUCCEED
107482:20180830:131734.229 End of zbx_remedy_process_alert():SUCCEED
Thanks
|
|
This did not go to any version branch, no official Zabbix version contains this implementation, reopening.
|
|
I really would like to know why this hasn't been addressed into latest releases... 
|
|
Is it possible to use this in version 5?
|
|
When will this integration be available? This would be very nice to have.
|
|
Another upvote
A customer of ours is asking if this integration is possible
|
|
Following up to see when this maybe available. when will this be added?
|
|
Another upvote.
We also have a customer asking for this.
|
|
Another upvote
|
|
Hi All,
Do we have an intergration of zabbix with BMC Helix for auto ticketing
zabbix version: 6.2
|
Generated at Thu Jul 17 09:43:11 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.
import.pl
mediatype-passwd.png
proxy upgrade issue.txt
Team INT