
Release Notes for Zenoss Ser-
vice Dynamics Version 4.1.1
13
<tal:block tal:repeat="item esa/causes">
Impact Chain: ${item/impactChain}
Device: ${item/evt/device}
Component: ${item/evt/component}
Severity: ${item/evt/severity}
Time: ${item/evt/lastTime}
Message:
${item/evt/message}
<a tal:attributes="href item/urls/eventUrl">Event Detail</a>
<a tal:attributes="href item/urls/ackUrl">Acknowledge</a>
<a tal:attributes="href item/urls/closeUrl">Close</a>
<a tal:attributes="href item/urls/eventsUrl">Device Events</a>
</tal:block>
To use solely the most probably cause, use tal:define and a Python expression:
<tal:block tal:define="topcause python:esa['causes'][0]">
Impact Chain: ${topcause/impactChain}
Device: ${topcause/evt/device}
Component: ${topcause/evt/component}
Severity: ${topcause/evt/severity}
Time: ${topcause/evt/lastTime}
Message:
${topcause/evt/message}
</tal:block>
1.7. Reporting Problems and Providing Feedback
To contact Zenoss Customer Support, go to the support portal at:
https://support.zenoss.com
1.7.1. Product Documentation Feedback
Zenoss welcomes your comments and suggestions to help us improve our product documentation. Please send
your comments to:
1.8. Defects Fixed in this Release
See the document titled "Zenoss Service Dynamics Resolved Defects" (appended to these release notes) for
the list of defects that were resolved in this release of Resource Manager.
Kommentare zu diesen Handbüchern