Steps to create bundle with create-analytics-bundle scirpt:

http://zenpackers.readthedocs.io/en/latest/analytics/create-analytics-bundle.html

  1. Setup your aliases in the ZP

    • ensure all aliases are unique per device and component

  2. Setup your labels in each component:

    _properties = BaseComponent._properties + (
{'id': 'path', 'label': 'Full Path', 'type': 'string', 'mode': ''},
{'id': 'replication', 'label': 'Replication', 'type': 'string', 'mode': ''},
{'id': 'did_status', 'label': 'DID status', 'type': 'string', 'mode': ''},
)
  1. Model a device that has all possible components available.

Note

Note you must have a device fully modelled and with all the aliases in place to get the measures to come out!

  1. You can also simplify creation of the bundle in the Makefile: https://github.com/zenoss/ZenPacks.zenoss.CiscoAPIC/blob/develop/GNUmakefile#L29 https://github.com/zenoss/ZenPacks.zenoss.Microsoft.HyperV/blob/develop/GNUmakefile https://github.com/zenoss/ZenPacks.zenoss.Microsoft.HyperV/blob/develop/get_aliases_dsv.xsl
  2. In order to control what properties and aliases get created in the bundle, see the reportables information in Reportables: Modify what is Reported .
  3. Run the create-analytics-bundle
    • Note: the resulting bundle only needs a fully modeled device to work.
  4. Install ZenETL, and allow it to run for 24 to 48 hours
  • Ensure that all your tables (including raw_v2_*, hourly_*, daily_* tables) are in the reporing database on analytics server.
  1. Check that Analytics server has your tables created
  2. After editing, .dsv file could be added to dmd using chkaliases script, and
from there exported to objects.xml, so you don’t have to edit it from UI or by hand in XML.
  1. Check results