Nms todo: Difference between revisions

From I Will Fear No Evil
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 32: Line 32:
Notes on testing API
Notes on testing API
Ubuntu 20.X
Ubuntu 20.X
PHP 7.4 testing on 8.X todo
xSlim4
Slim4
</pre>
</pre>


Need to clean out unused adds in vendor.
=== 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


Need to write SNMP class that is better fault tolerant
=== WinBlows ===
 
* Confirm regex of SNMP in Win
begin investigation of user auth and security system for application
* Powershell support somehow?
 
* Win sys message ingestion
Make pollers identifiable via GUID so we can have discrete monitors per poller/ host. Not just localhost support
* tie to deviceProperties
 
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
 
Begin Windows monitoring ability and tie to deviceProperties


=== Printer ===
Printer support or at minimum a template system defined with skels..
Printer support or at minimum a template system defined with skels..
* template_printer_manufacturer_model.tpl
* template_printer_manufacturer_model.tpl
Line 67: Line 61:
* shell skel?  Does it even need to exist?
* shell skel?  Does it even need to exist?


Build out fresh env and scratch install on minimal hardware
=== 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
* 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
Begin work again on UI/UX for existing API's
* make complete list of API's and add into wiki
 
* PHP7.4 unit tests
make complete list of API's and add into wiki
* 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?




Revision as of 07:52, 5 June 2023

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

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

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
Notes on testing API
Ubuntu 20.X
xSlim4

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?
Retrieved from "https://wiki.iwillfearnoevil.com/mediawiki/index.php?title=Nms_todo&oldid=313"