I was toying with the idea of a modeler in which a component had subcomponents. IE you have an application as a component, and that application might have say two (or more) HTTP Listeners as subcomponents of the application, where I might want to trend HTTP stats on each listener.
Or another example might be a SQL Server where databases are the components, and tables are subcomponents of the database.
I found this: http://community.zenoss.org/message/36249 so the concept of subcomponents looks easy enough to pull of, but I'm curious how would subcomponents be displayed in the UI? Would/Could they be nested beneath the component?
Any one done something like this, have any screen shots of how it looks?
I did something like that for my IBM MQ zenpack, basically the subcomponents and components show up in the GUI as components of the device:
here the MQQueue and MQChannel are subcomponents of their MQManager (you can see in the screen)
Thanks, I had actually seen those screen shots, and it didnt register to me that they were subcomponents. Did you by any chance look into having the queues nest beneath managers in the UI. I'm curious how involved that might be.
I totally get how the subcomponents are linked via the relationships, but I'm interested in presenting them in the same hierachy on the component section. I'm curious what the level of effort might be, but it is good to see more than one person has a zenapck with subcomponents. With a couple of examples I must just be able to figure it out