[ZBXNEXT-6674] Tag based mapping between problems and services Created: 2021 May 20  Updated: 2024 Apr 10  Resolved: 2021 Oct 17

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 6.0.0alpha1, 6.0 (plan)

Type: New Feature Request Priority: Trivial
Reporter: Rostislav Palivoda Assignee: Andrejs Verza
Resolution: Fixed Votes: 3
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File SLA_tab_indicator.png     PNG File Screenshot from 2021-07-13 16-17-15.png     PNG File Screenshot from 2021-07-13 22-32-32.png     PNG File Screenshot from 2021-07-14 13-06-20.png     PNG File Screenshot from 2021-07-14 14-11-29.png     PNG File Tags_tab_indicator.png     GIF File add_child_service_non_clickable.gif     GIF File back_from_edit_mode.gif     GIF File back_from_kiosk.gif     GIF File broken_tag_value_filter.gif     GIF File checkbox_issues.gif     GIF File multi_level_filtering_absence.gif     GIF File reset_from_edit_bug.gif     GIF File service_delete_error.gif    
Issue Links:
Causes
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
ZBXNEXT-6675 Frontend changes for tag based mappin... Specification change (Sub-task) Closed Alexander Shubin  
ZBXNEXT-6689 Schema And Upgrade Patch for Tag base... Specification change (Sub-task) Closed Dmitrijs Goloscapovs  
ZBXNEXT-6707 Reload service cache on signal Specification change (Sub-task) Closed Dmitrijs Goloscapovs  
ZBXNEXT-6714 Make Service Manager Configuration Sy... Change Request (Sub-task) Closed Dmitrijs Goloscapovs  
Team: Team A
Sprint: Sprint 76 (May 2021), Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021)
Story Points: 10

 Description   

Current implementation of services was designed long time ago, it is rather limited and has significant limitations. Major limitations are:

  • scalability: it does not scale well, also bad user experience when number of services exceeds few hundreds
  • hard to configure: mapping based on triggers does not work well and requires significant effort
  • very limited visualization: no graphical representation of services, no good reporting
  • limited SLA calculation rules
  • no alerting in case of service status changes
  • user permissions: all or nothing

Proposed functionality proposes new way of mapping problem events and service, thus making configuration and maintenance of services much more straight forward.

 Comments   
Comment by Alexander Shubin [ 2021 Jul 22 ]

Implemented in:

Comment by Brian van Baekel [ 2021 Jul 27 ]

As it seems ZBXNEXT-334 is not covered here, or am I missing something in the alpha release?

Having multiple maintenance settings is really problematic, would be extremely nice if ZBXNEXT-334 is included in the 6.0LTS release as well..

Comment by Dimitri Bellini [ 2021 Jul 27 ]

Hi Brian,
i think is a good idea to solve the ZBXNEXT-334 scenario, a customer ask about it last week...
Thanks so much

Comment by Andrejs Verza [ 2021 Oct 13 ]

Documentation updated:

Generated at Sat Apr 19 03:59:00 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.