Zabbix::API::Screen -- Zabbix screen objects
use Zabbix::API::Screen; # TODO write the rest
Handles CRUD for Zabbix screen objects.
This is a subclass of
Mutator for the screenitems array. Setting the screenitems through this means you won't have to set the
vsize data attributes accordingly, as that will be done for you. It also checks that the
y attributes have been specified for all the screenitems and throws an exception otherwise.
This method handles extraneous
graph => Zabbix::API::Graph attributes in the screenitems array, transforming them into
resourcetype attributes, and pushing the graphs to the server if they don't exist already.
This means you can put
Zabbix::API::Graph objects in your data and the module will Do The Right Thing (assuming you agree with my definition of the Right Thing). Graphs that have been created this way will not be removed from the server if they are removed from the screen, however.
Since graphs do the same thing with their
Item graphitems, you can create a bunch of items, put them in a bunch of graphs, put those in a screen, push the screen, sit back and enjoy the fireworks.
A bunch of constants:
SCREEN_RESOURCE_GRAPH SCREEN_RESOURCE_SIMPLE_GRAPH SCREEN_RESOURCE_MAP SCREEN_RESOURCE_PLAIN_TEXT SCREEN_RESOURCE_HOSTS_INFO SCREEN_RESOURCE_TRIGGERS_INFO SCREEN_RESOURCE_SERVER_INFO SCREEN_RESOURCE_CLOCK SCREEN_RESOURCE_SCREEN SCREEN_RESOURCE_TRIGGERS_OVERVIEW SCREEN_RESOURCE_DATA_OVERVIEW SCREEN_RESOURCE_URL SCREEN_RESOURCE_ACTIONS SCREEN_RESOURCE_EVENTS SCREEN_RESOURCE_HOSTGROUP_TRIGGERS SCREEN_RESOURCE_SYSTEM_STATUS SCREEN_RESOURCE_HOST_TRIGGERS
These are used to specify the type of resource to use in a screenitem. They are not exported by default, only on request; or you could import the
Fabrice Gabolde <firstname.lastname@example.org>
Copyright (C) 2011 SFR
This library is free software; you can redistribute it and/or modify it under the terms of the GPLv3.