Nms todo: Difference between revisions

From I Will Fear No Evil
Jump to navigation Jump to search
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Just notes on what I need to work on for the NMS..
Just notes on what I need to work on for the NMS..
=== Networking ===
* L2 maps and adjacency
* possible equiv of an MTR
* L3 maps? device all the way to gateway
=== Eventing ===
* begin definitions of application events vs infra events (host included)
* Begin ECE
* Define start of event parent child relationships?
=== Graphite ===
=== Graphite ===
* Clean regex up.
* Clean regex up.
Line 15: Line 25:
* figure out aggregation of different rrd into single graph
* figure out aggregation of different rrd into single graph
* learn more about rrd rendering in a fast way
* learn more about rrd rendering in a fast way
* rendering the graph we have to think about authed users vs not authed
* kiosk options?  Unlikely needed unless minimal access


=== logging ===
=== logging ===
Line 28: Line 40:
* file
* file
* debugger
* debugger
<pre>
Notes on testing API
Ubuntu 20.X
xSlim4
</pre>


=== Cleanup ===
=== Cleanup ===

Latest revision as of 07:06, 6 June 2023

Just notes on what I need to work on for the NMS..

Networking

  • L2 maps and adjacency
  • possible equiv of an MTR
  • L3 maps? device all the way to gateway

Eventing

  • begin definitions of application events vs infra events (host included)
  • Begin ECE
  • Define start of event parent child relationships?

Graphite

  • Clean regex up.
  • API search needs to be smarter
  • define template to match rrd 'look' for rendering

rrdGraph

  • filesystem search with a regex on a per host basis
  • rrd graph creation an link
  • predictive on demand
  • start / end global top of page for all shown RRD
  • threshold shown? On demand?
  • should rrd reflect active eventing based on shown metric?
  • support export of data from rrd outside maybe
  • figure out aggregation of different rrd into single graph
  • learn more about rrd rendering in a fast way
  • rendering the graph we have to think about authed users vs not authed
  • kiosk options? Unlikely needed unless minimal access

logging

  • stable
  • need more logrotate opotions set

Graphing metric ingestion

graph data ingestion is working and APPEARS stable 06-04

  • rrd
  • graphite
  • databaseMetric
  • database
  • file
  • debugger

Cleanup

  • Need to clean out unused adds in vendor.
  • Need to write SNMP class that is better fault tolerant
  • Make pollers identifiable via GUID so we can have discrete monitors per poller/ host. Not just localhost support
  • Start code for Triggers
  • Finish code for Maintenance.. This will require DB changes for suppression
  • Activate production states in the event system
  • Begin reporting API
  • document all completed APIs (last)
  • remove old/ code eventually
  • begin buildout AWS monitoring and toolset

WinBlows

  • Confirm regex of SNMP in Win
  • Powershell support somehow?
  • Win sys message ingestion
  • tie to deviceProperties

Printer

Printer support or at minimum a template system defined with skels..

  • template_printer_manufacturer_model.tpl
  • template_snowflake_who_what.tpl
  • snmp skel documented
  • Curl skel
  • shell skel? Does it even need to exist?

Dev work and overall validation

  • Build out fresh env and scratch install on minimal hardware
  • investigate the event ingestion API and look at mapping to make sure it is wired up correctly
  • Begin work again on UI/UX for existing API's
  • make complete list of API's and add into wiki
  • PHP7.4 unit tests
  • Investigate PHP8.X
  • Begin UI/UX testing again

Apache / Nginx

  • Write a template config
  • SSL support internal and howto for external

Authentication

  • Build out redis for auth
  • cookie client side need code written
  • Hammer this to see how stable it is in middleware
  • Write local auth support
  • Write LDAP support
  • Write AD support
  • TFA?