||Multi-graph reports are unable to show more than 39 entries in edit mode.
||FileSystem transform fails because evt.eventKey no longer
contains the data point name.
||Date range filtering not working.
||Provide an option to exclude full device location in graph title. Use to read
device names when locations become long.
||FQDN in multi-graph reports makes graphs difficult to read.
||When utilizing an event bookmark, only columns currently visible get the filters
applied; not all columns specified in the bookmark.
Instances. The count at the bottom might display incorrect values when
(as an example) and set the pull-down to |
||findposkeyerror reports trace backs with the log
"AttributeError: 'NoneType' object has no attribute 'getDatabase".
||Devices can be added to Component Group as they are
included in search results.
||Test data source browser interface functionality should test on device's actual
||Event View dashboard portlet does not retain specified
columns and filters.
||A DERIVE type data point is performing like a COUNTER data point in graphs. In
particular, when the delta of the current and previous value are negative, the graph
displays a spike instead of a drop.
||IPv6ServiceMap plug-in models services that are localhost-only.
||When using a Custom Production State and zProdStateThreshold
to disable monitoring for a device, the configuration does not take effect
||When running an auto discovery on a very large network subnet, the discover job
||zenmodeler logging 'Scan time' of modeling immediately after
modeling starts, resulting in inaccurate logging of modeling times.
||zeneventd logging duplicate entries.
||When a user with role ZenManager adds a device and a component group to a new
user as an Administered Object, the new user is unable to add components to the
||As a user with permissions only to a component group, clicking on a component
from that group results in a redirect to the login prompt and resulting login will
||Unable to selectively adjust zFileSystemSizeOffset based on
filesystem type. For example: Ext4 filesystems have five percent reserves and the
product must take that into account.
||When selecting All on Same Graph in Component Graphs, the
legend will contain the device ID instead of the title, component ID instead of the
title, GraphPoint legend is repeated, and device is included on each legend entry even
though it is the same for all.
||audit.log does not log changes to the page.
||SNMP INFORM via SNMPv3 are not being processed.
||Bad transform events can cause an event loop. zeneventd will
produce events sent to the root event class, events fail to find default mappings and
mapped to /Unknown, and transform errors are logged.
||zenhub stats does not include the pid of the zenhubworker for
which a task is assigned. This new information is useful when debugging
zenhub and its workers, especially in cases where a worker might
be hanging or deadlocked.
||zenbatchload --nocommit still commits changes.
||Graph refresh button will request new graph data, even if previous request is
still being processed, which leads to slowing down the system.
||Graph continues to make refresh requests even when graphs are no longer visible,
which leads to slowing down the system.
||When an error is encountered when evaluating min/max threshold, the resulting
logged error on the hub does not specify the device/component from which the error
||Device configuration loading speed is slow.
||Existing graph reports will not allow a user to add additional device-level
||RabbitMQ should not have an IP assignment because this limits the ability to
provide application-level high-availability (HA) if a host fails.
||Viewing a device graph where the value fluctuates over time, the actual maximum
value might not display correctly. Zoom out from the graph and at certain intervals,
the max value will drop, even though the higher value will still be within the graph's
||Setting the device parameter (evt.device) on an event
transform prevents the production state from being set.
||Using a formatted email notification, extra spaces are added in the html. The
extra spaces can break rendering and formatting.
||When a new data source name includes invalid characters, a message is needed to
state the allowed characters.
||In the component graphs section, graphs can have a group of disparate values of
different sizes. When displayed individually, graphs will render correctly; however,
when they are grouped, they render too large to be viewed without scrolling.
||When deleting an organizational group, the devices that belong to that group are
not completely removed from the group. Subsequently, if the group is re-created, the
devices appear in the list of group members, even though the devices claim to not be a
member of the group, and the group still claims to have zero members.
||Most component graphs display IDs instead of title in legend and summary.