/
Event Monitoring Brick

Event Monitoring Brick

Univ. of Hawaii - ITS Technical Architecture - Brick   

Event Monitoring

Primary Architects:  Jan Kawachi and Michael Hodges

Description:   

ITS ITOC staff monitor infrastructure components, such as: networks, servers (hosts/vhosts), storage, and databases.  Infrastructure components should be setup to publish appropriate events and performance information to the central event monitoring tools.  Additionally, system capacity information should be collected and utilized for trending various performance and consumption metrics for capacity planning purposes.

There are two general categories to be monitored

    • Health Events – The tools for tracking these events help to indicate the current status of an online service or system so appropriate action can be taken.
    • Capacity Events – The tools for tracking these events are used by technical teams to set internal thresholds and/or track trends related to utilization.  They are a main collection point for capacity planning information.  They may also be used for team-specific alerts.

Any new system or service should only be considered production-ready when/if appropriate event monitoring has been implemented.

 

Experimental

  • End-user experience monitoring

    • Zabbix agents on remote campuses

    • Raspberry Pi sensor-net to measure network performance (for Manoa)

      • Focused on high volume research-type network traffic

Strategic (3-5 Years)

  • Health Events: Icinga

  • Capacity Events: Zabbix

Tactical (1-2 Years)

  • Health Events: Icinga Version 1.10.0

    • Vendor Specific tools may also be used by local technical teams (but will not be used by the central monitoring organization)

  • Capacity Events: Zabbix Version 3.0.4 LTS

    • Vendor Specific tools may also be used by local technical teams (but will not be used by the central monitoring organization)

Containment

 

Retirement

 

Notes

  • Vendor-specific monitoring tools are used by various ITS technical teams.  These tools are not listed in this document, but we expect teams to use vendors tools as they see fit to provide excellent production support.  Vendor specific tools add special value that vendor-agnostic tools often cannot.  These tools may be used by technical teams for their work but will not be used by any central monitoring groups.

Emerging Trends

  • Event reporting tools that integrate with cloud technology.


Change History

  • Approved October 2016

 


 Definitions

Experimental

Someone in ITS is currently investigating or experimenting with this technology.

Strategic

ITS will be investing in this technology for 3-5 years.

Tactical

ITS will be investing in this technology for 1-2 years.

Containment

ITS will continue to use this technology for existing systems, but will no longer invest in this technology and/or grow its use.

Retirement

ITS has a firm plan (and timeline) to retire this technology.


Related content