-
Type:
Change Request
-
Resolution: Won't fix
-
Priority:
Trivial
-
None
-
Affects Version/s: 2.2.13, 2.4.8
-
Component/s: Server (S)
-
Environment:IT Services
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..