[ZBXNEXT-3307] Request of improvement for IT Services Created: 2016 Jun 15  Updated: 2021 Sep 08  Resolved: 2021 Sep 08

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.2.13, 2.4.8
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: Alessandro Sgolacchia Assignee: Unassigned
Resolution: Won't fix Votes: 1
Labels: database, triggers, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

IT Services



 Description   

Proposal for improvement of IT Services (want to know if I can throw away "impact mgt suite" and use Zabbix, instead. Moreover, this solution could be compliant with every CMDB):

a) IT Services structures should have <component_name> as Primary Key
b) The link between TRIGGERS and IT Service COMPONENTS should be in a new trigger FIELD, where one can indicate the "IMPACTED IT COMPONENT"
c) IT Services structures should manage CHILDS and TRIGGERS all together
d) IT Services components could be off a "Status Computation Model", as for instance: Simple, Cluster, Weighted Cluster, etc.., which reflect the way Zabbix calculate the component "status"
e) Relationships between components could be defined out of a Model: Direct, Increasing, Decreasing, etc..



 Comments   
Comment by Aleksandrs Saveljevs [ 2016 Jun 20 ]

Could you please elaborate a bit on what problems does your proposal attempt to solve, both technically and from a high-level perspective?

Comment by Alessandro Sgolacchia [ 2016 Jun 24 ]

It's not a problem, it's a suggestion for improvement.
IT Services is not so useful in the state it is, because of some limitations.
Nevertheless, it is a very powerful tool.
In most cases, this will overcome easily third party "Service Management Tools", just adding a few (listed) features.
Not meaning for 2.x, think instead at 3.x.

Comment by Dmitrijs Goloscapovs [ 2021 Sep 08 ]

Services functionality was majorly revised in ZBXNEXT-6800, which includes most of proposed improvements (implemented in slightly different way).

Generated at Thu Apr 25 16:25:05 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.