OPMANTEKNETWORK MANAGEMENT AND IT AUDIT SOFTWARE

Creating Actionable Reports with NMIS8 and opReports v1.0 – May 2018

We will send you the recording.

Submit your questions anytime. We’ll do Q&A throughout.

Please complete the Exit survey.

Topics for Today

• Performance monitoring systems gather data, it’s what they do by their very definition. How you use that data can transform your organization from a reactionary one to a data driven group that proactively prevents user impacting events and system degradation.

• How to leverage NMIS8’s built-in reports to create ToDo lists

• How to create custom reports from NMIS using simple scripts

• How Opmantek’s opReports solution enhances NMIS’ reporting to

provide truly actionable reports for Engineers and Managers

IT Service Management Maturity Model

CHAOTIC• Ad Hoc• Undocumented• Unpredictable• Multiple help desks• Minimal IT operations• User call notification

REACTIVE• Fight fires• Inventory• Desktop software

distribution• Initiate problem

management process• Alert and event

management• Measure component

availability (up/down)

PROACTIVE• Analyze trends• Set thresholds• Predict problems• Measure application

availability• Automate• Mature problem

configuration, change, asset andperformance mgmt. processes

SERVICES• IT as a service provider• Define services, classes,

pricing• Understand costs• Guarantee SLAs• Measure and report

service availability• Integrate processes• Capacity Mgmt.

VALUE• IT as a strategic business

partner• IT and business metric

linkage• IT/business collaboration

improves business process• Real-time infrastructure• Business planning

Tool Leverage

Operational Process Engineering

Service Delivery Process Engineering

Service & Account Management

Manage IT as a Business

Level 0

Level 1

Level 2

Level 3

Level 4

Increasing Performance & Value to Organization

Open-SourceNMIS: Fault and Performance Management

Commercial SolutionsopReports: Detailed reporting

Optional EnhancementsopEvents: Intelligent event response

Architecting a Solution

Opmantek Application Flow

Subnet

Poller

NMIS opEvents opConfig

Master

opHA

opHA NMIS

cli data

syslogSNMP / WMI

metadata

metadata

metadata

SNMPtrap

opEvents

meta-events

events

api

opCharts

opCharts

service monitor

opReports

opReports

reports

summary

metadata

detail-Link

metadata

Netflow Data

opFlow Collector

opFlow

References

Atlassian – 4 Must Haves for Successful IT Metrics and Reporting

https://www.atlassian.com/it-unplugged/itsm/successful-it-metrics-and-reporting

ITIL News - What is Service Reporting from an ITIL Perspective?

https://tinyurl.com/yd7oruux

ITSM Watch - Service Measurement & Reporting Across the ITIL Service Lifecycle

https://tinyurl.com/3lg3ljj

You should bookmark these…

LEVERAGING NMIS8’S REPORTING TO CREATE ACTION AND TO-DO LISTS

NMIS

• Separate Reports into 2 categories;

• Improving Information Collection

• Improving System Performance

Open Source Performance and Fault Management

NMIS

• Reports -> Current -> Collect/Update Time

• System -> Host Diagnostics -> NMIS Runtime Graph

• System -> Configuration Check -> Node Admin Summary (Only Exceptions)

• Check Model Selection, Active, Collect, Ping settings

Notes

• Use Current when selecting any NMIS Report, Column headers are sortable

• Don’t forget to Open in New Page, then use browser to Print/Save as PDF

Improving Information Collection

NMIS

• Reports -> Current -> Top 10

• Network Performance -> Top 10 (subtly different from the Reports version)

• Reports -> Current -> Availability

• Select Daily/Weekly/Monthly

• Service Desk -> Monitored Services -> Only Services with Problems

• Service Desk -> Alerts -> Events

Notes

• Use Current when selecting any NMIS Report, Column headers are sortable

• Don’t forget to Open in New Page, then use browser to Print/Save as PDF

Improving System Performance

CREATING CUSTOM REPORTS IN NMIS8 USING SCRIPTS

NMIS

• NMIS8 ships with several sample scripts demonstrating how to walk through nodes/devices• /usr/local/nmis8/admin/samples/

• config_format.pl – example of how to read/write a configuration file• nmis_scratch.pl – example of how to read the Nodes.nmis file, edit attributes and create a list• nmis_sys_scratch.pl – example of how to load a specific device and report on it• rrd_report_overmax.pl – compares reported vs set bandwidth and reports overages

• /usr/local/nmis8/admin/• billinggraph.pl – creates a custom graph based on interface usage• exportnodes.pl – creates a csv with specific device information• find_ipsla_nodes.pl – creates a list of devices running IPSLA

Creating Custom Reports from NMIS8 using Scripts

BUILDING ON NMIS8’S REPORTING WITH OPREPORTS

opReports

https://community.opmantek.com/display/opReports/Home

• Includes 18 Classes of reports

• Multiple ways to customize selection and grouping of devices, interface, and display

• Useful Reports

• Node Health Report

• Node Availability (i.e. SLA report)

• WAN Report

• Traffic Usage, Summary and Snapshot

Detailed Operational and Executive-Level Reports

Customizing Reports

• Each report has slightly different options

• In general -• Description• Report Name• Device and Interface Naming• Detail Level• Thresholds• Viewers• Device/Interface selection

Knobs and Switches to Flip

BONUS SECTION

opEvents

• Configure Daily Summary Reports in opCommon.nmis

• Views -> Summary Reports

• Use this report to drive improvements in network performance

• Remediate Top 3 Events and Devices every day (see: Top 10 nodes and events by event count)

• Compare to NMIS Top 10 list (or opCharts TopN if available)

Advanced Fault Management and Operational Automation

Automating Report Creation

• Avoid filling email boxes• Reports should have a targeted user and purpose• Reports should drive thought and action• Generate reports on a cadence that users can absorb and take action• Create emails lists, then manage membership centrally

Basic rules for scheduling reports

Scheduling Report Generation

• Daily• Event Summary Report to Engineers; drive remediation efforts• Device Health Report to Engineers; drive remediation efforts• Response Report to Engineers; drive remediation efforts

• Weekly• Node Availability Report to Network Managers, Lines of Business• Configuration Summary to Network Managers; drive discussion w/LOB

• Monthly• WAN Report to Telcom Managers; drive SLA discussion with providers• QOS/CoS Report to Network Managers; drive discussion w/network architect• Interface Capacity to Network Manager; drive discussion a/LOB

How Often Reports Should Be Created and Who Should Get Them

CONTACT FOR FOLLOW UP

Commercial enquiries:

Tom WiriAccount Executive+1 (512) 430-4450usa@opmantek.com

Technical enquiries:

Mark HenrySenior Engineer+1 (207) 951-2428markh@opmantek.com