Enric Obiols
2013-09-30 09:06:19 UTC
Enric Obiols [http://community.zenoss.org/people/eobiols] created the discussion
"Definition of Device and Service Status different than the Zenoss Core ones."
To view the discussion, visit: http://community.zenoss.org/message/74788#74788
--------------------------------------------------------------
Dear All,
We are exploring the feasibility of monitoring Devices and Services (SW modules) using Zenoss Core in our System with a particular state machine different than the Zenoss one.
Being in Production State, Zenoss defines the following Device / Service Status by means of the severity field: CLEAR (green), DEBUG (grey), INFO (blue), WARNING (yellow), ERROR (orange) and CRITICAL (red). See sect 7.1.1.3 of Zenoss_Core_Administration_02-062013-4.2-v06.pdf.
These status/states do not match with the ones of our system which are the following ones with the associated colour.
State                                  Color
Idle                                     Yellow
Ready                                Olive green
Active                                Green
Warning                            Light green
Test                                    Purple
Unlaunched                      White
Alarm                                 Red
Alarm Acknowledge       Orange
Connection Lost              Brown
Maintenance                   Dark Blue
Absent                               Cyan
Since Zenoss states are already defined in sect 7.1.1.3 of Zenoss_Core_Administration_02-062013-4.2-v06.pdf, I assume that defining a new set of states is not feasible or easy.
-Â Â Â Â Â Â Â Please, confirm.
Therefore, we were thinking about the feasibility of defining substates within the Zenoss States. For example, defining the substate âIDLEâ within the Zenoss âCLEARâ state. This is, CLEAR.IDLE. At screen level, we would like to display only the substate information. For instance âIDLEâ using our colour code (yellow for IDLE).
We initially thought about using the plugin text output / agent text output to introduce this Zenoss state plus the substate information.
-       Could you please let us know if it is possible defining 11 states (idle,⊠absent) different than the Zenoss one?. If so, how it can be done?.
-       In case, the answer to the previous question is affirmative, please, clarify the mechanism to define the associated colours (yellow, âŠ, cyan) at MMI level (Zenoss screen).

Best Regards,
Enric Obiols
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74788#74788]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Definition of Device and Service Status different than the Zenoss Core ones."
To view the discussion, visit: http://community.zenoss.org/message/74788#74788
--------------------------------------------------------------
Dear All,
We are exploring the feasibility of monitoring Devices and Services (SW modules) using Zenoss Core in our System with a particular state machine different than the Zenoss one.
Being in Production State, Zenoss defines the following Device / Service Status by means of the severity field: CLEAR (green), DEBUG (grey), INFO (blue), WARNING (yellow), ERROR (orange) and CRITICAL (red). See sect 7.1.1.3 of Zenoss_Core_Administration_02-062013-4.2-v06.pdf.
These status/states do not match with the ones of our system which are the following ones with the associated colour.
State                                  Color
Idle                                     Yellow
Ready                                Olive green
Active                                Green
Warning                            Light green
Test                                    Purple
Unlaunched                      White
Alarm                                 Red
Alarm Acknowledge       Orange
Connection Lost              Brown
Maintenance                   Dark Blue
Absent                               Cyan
Since Zenoss states are already defined in sect 7.1.1.3 of Zenoss_Core_Administration_02-062013-4.2-v06.pdf, I assume that defining a new set of states is not feasible or easy.
-Â Â Â Â Â Â Â Please, confirm.
Therefore, we were thinking about the feasibility of defining substates within the Zenoss States. For example, defining the substate âIDLEâ within the Zenoss âCLEARâ state. This is, CLEAR.IDLE. At screen level, we would like to display only the substate information. For instance âIDLEâ using our colour code (yellow for IDLE).
We initially thought about using the plugin text output / agent text output to introduce this Zenoss state plus the substate information.
-       Could you please let us know if it is possible defining 11 states (idle,⊠absent) different than the Zenoss one?. If so, how it can be done?.
-       In case, the answer to the previous question is affirmative, please, clarify the mechanism to define the associated colours (yellow, âŠ, cyan) at MMI level (Zenoss screen).

Best Regards,
Enric Obiols
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74788#74788]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]