Netuitive User Interface

Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
Netuitive User Interface
9/13/2010
Overview
Updating the Netuitive UI will provide users with an improved experience focused on
reducing workflow and presenting contextual information in an effective format for
discovery and identification.
A number of different usage patterns have been identified and will be addressed by
providing users with default themes that target information needed to effectively
perform their jobs. Login based interfaces can be customized by the user and follow
them whenever they log into Netuitive.
The proposed web application/port-let gives user the ability to customize their view
to meet their needs while providing defaults that will improve their workflow.
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 1 of 7
Pending
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
Overview
1.1
1.2
3.1
DRAFT
Pages: 2 of 7
Pending
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 3 of 7
Pending
Dashboards
All dashboards are not equal. We have identified a number of different usage types that will benefit from improvements to Netuitive’s user interface.
Portalizing the current product will give users the ability to pick from some default themes fine tuned to improve their workflow and customize those
themes to suit there personal preferences. Users can change colors, move widgets around on the page, and add or remove widgets.
Each one of the widgets can synchronize with other widgets on the same page to provide contextual data and provide the information necessary for
users to make discoveries and solve problems. To add an element for comparison a user can drag and drop or use search.
Sharing views with other engineers is an important feature for our users. Users will be able to save a dashboard in a new tab. They can also share a
dashboard view with others to simplify allocating a problem to the responsible groups for analysis and remediation.
2.1
1.2
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 4 of 7
Pending
Dashboards for Level 1 and Level 2 Engineers
For Olivia and Stuart the dashboard is often their only view into the health and workload of the system. The
proposed dashboard gives our fearless warriors the ability to quickly identify problems through an incident
based perspective allowing them to visualize important data, dependencies, contributing factors and impact
to services. Each incident combines all the elements that are contributing to an incident so engineers can trace
the “trail of dominos” that make up an incident.
2.1
Incidents are stored in a history
list presented in a familiar address
bar. The bar also allows users to
directly access any incident.
Dashboards can also be saved in a
new tab to allow users to keep an
eye on problem areas.
Sharing dashboards allows Olivia
to send Stuart her view so they
can look at a problem together in
real-time.
When an engineer chooses an
incident to review the timeline
graph updates to show dependencies and alarms. Each element
can be expanded to help engineers identify top deviations.
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 5 of 7
Pending
Dashboard Interactivity
Interaction in the dashboard include hover states that progressively disclose details about incidents, events, health and workload. As users hover over
points in time details of the snapshot are presented in pop-ups designed to provide context to the timeline and the selected element.
1.3
Views can be filtered and sorted
to reduce noise and add another
level of comparison.
Knowledge-base recommendations give engineers results based
on past incidents to help them
quickly identify solutions.
Deviation comparisons present
some common metrics to monitor. Additional elements can be
added to compare against to aid
in understanding what is normal
behavior for an element.
Additional details about elements
can be found below in tabs for
each one of the elements involved in an incident.
System notifications are seen only
by netuitive administrators and
message important information
about Netuitive SA.
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 6 of 7
Pending
Dashboards for IT Managers
Chi Lin manages a busy IT department with 200 engineers, analyst, and capacity planners. She needs to keep an eye on things in
real-time without added noise of things that don’t matter to her group. If there is a problem Chi Lin will need to be able to answer
some important questions like what was the problem, who is working on it, when will it be done and will it happen again.
2.1
Understanding problem scope,
dependencies, and capacity
risk will provide Chi Lin with the
information she need to engage
her teams, inform senior management and track progress.
Groups are an effective way for
Chi Lin to visualize the conceptual
structures of her network. Each
group can contain thousands of
elements and other groups.
As each group is selected the top
problems are found in the lower
half of the screen. When elements
are selected details of the status
and dependencies are presented.
Player controls enable the display
to be automated in an unattended mode that will allow users
to cycle through all the groups to
monitor the overall health.
Date: 9-13-2010
DRAFT CONCEPTS
Netuitive Service Analyzer Concepts
DRAFT CONCEPTS
netuitive_storyboard.v1.01.pdf
DRAFT
Pages: 7 of 7
Pending
Performance Assistant
James is an analyst so he is less interested in pretty presentations that show him real-time data. He just wants to know if the element is behaving differently and then find out why. Comparing the health timelines of the last month will help James discover the
root cause and then provide recommendations to prevent it from happening again.
3.1
The Performance Assistant presents the analyst with historic data
of the deviations that make up an
incident.
Adding additional elements for
comparison done by typing a
particular ME or dragging a node
from the dependencies chart.
Selecting a different element
changes the alarm timeline to
reflect that element.
Top deviations display graphs of
baseline and actual performance
over the same time range.
The most common metrics of the
selected element is found on the
right rail and provides the ability
to add other elements for comparison.