|
|
| Subject: | tales expression for component attribute |
| Author: | Nathan Hathaway |
| Posted: | 2016-08-16 10:16 |
Hi all,
I've been working on my firstzenpack to monitor some odd devices we have at work.I've got my modeler plugins working properly but I cant seem to pass componentattributes gatherd by the pluginto a bash script that I've built for perfomance monitoring.
Is there a tales expression (or should I be using something else)that can be used with a command datasource to get attributes from a component It seems simple enoughto get the device attributes ${here.mangeIp} I just havn't found (or missread) documentation to get component attributes.
Any help would be greatly appriciated.
| Subject: | Re: tales expression for component attribute |
| Author: | John Boyle |
| Posted: | 2016-08-26 12:31 |
Mrfred101,
I posted a link to your question on our IRC Chat channel. If you have not joined that here is the information. Another great way to engage with our community. Cheers! - JB
The #zenoss channel is a great way to participate in a live-chat with other Zenoss users. On occasion, our developers will drop by and join the chat.
John Boyle
Zenoss Community Engineer/Manager
jboyle@zenoss.com
Twitter: @BrandFlair
| Subject: | Component Tales |
| Author: | [Not Specified] |
| Posted: | 2016-08-26 12:42 |
Mrfred101,
In a component template that I recently wrote I was able to use ${here/
| Subject: | Do you have a copy of the |
| Author: | Jane Curry |
| Posted: | 2016-08-31 04:45 |
Do you have a copy of the ZenPack Developers' Guide https://github.com/ZenossDevGuide/DevGuide Instructions in the README for downloading it. Have a look specifically at Chapter 12, "Collecting Performance Data"; 12.3 details collecting component performance data.
It really depends on how many values you are collecting per component as to how complex the code is. If you are just collecting one value for each component then you should be able to simply specify the command to run, passing your ${here/
Make sure that the name of the template is identical to the name of the component object you created. See the DirFile ZenPack example -https://github.com/ZenossDevGuide/ZenPacks.community.DirFile for sample code - it also uses COMMANDs to get performance data.
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | The Dev guide is a great |
| Author: | Jay Stanley |
| Posted: | 2016-09-01 09:45 |
The Dev guide is a great resource to get you started. Hit us up in IRC as well for quick questions if you are confused.
For reference, when using tales in Zenoss.. "here" is the current object. So, if you are editing a device template, here is the device. If you are editing a template on a component, here is the component.
| Subject: | Delayed response |
| Author: | Nathan Hathaway |
| Posted: | 2016-09-17 07:09 |
I just wanted to say thanks for the replies. I've never been a fan of posts where the OP never responds back so I just wanted to update a little. I haven't had a chance to test the suggestions yet as work got crazy and we had to set this project aside for now. I hope to get back to it in the next week or so once we can stabilize our IT dept workload. I'll respond back once I've had a chance to work on this .
As a side note, Jane, Thank you for putting together that development guide. I had been using it before I posted and it has been a real help for me in other parts of the zenpack. I've been skipping around through it and have probably missed some details I needed to get this working. I plan to work through some of the examples as I get some free time (is there such a thing in our world)
Again Thank you for the responses
Nathan H
| < |
Previous Monitor IBM Rack mount and blade server |
Next tales expression for component attribute |
> |