These should be moved into github issues, but not yet
-
Priority
- Gateway commands to add items to ignore lists
- Email per-gateway reports to specific recipients
- Document how to write new reports
-
Ideas
- Web interface for reports
- Web interface for admin, edit some config, e.g. sources and intervals
- Historical data handling
- Track maximum usage for planning
- Consume licd "Summary" info for total available info
- Auto config reload and reconfiguration on changes. (This is not proving straight forward, back burner for now)
- Add contact column for each grouping "table" for emails to owners
- target next release
-
Support for new minimal netprobe distro
This needs reworking of PackageTypes and DownloadBase in the Component struct and the package code with it
-
Revisit the
geneos.json
config, break the config elements up into a hierarchy, so that things like port ranges, clean/purge patterns etc. can be set/unset based on component typesEnsure that support for original format/names is complete. Do not assume that users will update all versions of
geneos
at the same time. Consider a manual migration process for a few releases? -
Config Export/Import
- the rest
- Windows build, in stages:
- Initially for remote management (ssh etc)
- Add netprobe support, services?
- Add a 'selfupdate' like, but simpler than, rclone
- Instead of a single binary, look at installing
cordial
as a package in itself, with files then in bin, lib etc
- Instead of a single binary, look at installing
- When 'moving' a gateway, update licd connection details (if licd-host is undefined or localhost)
- Positive confirmations of all commands unless quiet mode - PARTIAL
- Should be an 'action taken' return from commands for output
- create a separate "verbose" logger and work through output to choose
- or more if verbose ... logic
- Warnings when a name cannot be processed (but continue)
- Help highlight typos rather than skip them
- Command line verbosity control - PARTIAL
- TLS support
- output chain.pem file / or to stdout for sharing
- TLS sync should copy root CA
- Docker Compose file build from selection of components
- Run REST commands against gateways
- initially just a framework that picks up port number etc.
- specific command output parsing
- centralised config
- web dashboard
- TLS
- Port selection
- SSO / Auth
- SSO Agent as a component (follow Web Dashboard Java model)
- Support gateway2.gci files
- web interface
- first version, review configs and instance state
- second to edit
- use a REST interface
- explore gRPC and other options over ssh for remotes (required daemon mode)
- add socket and open file details to ps (ala lsof) - perhaps a "details" command or an option to "show" ?
- /proc/N/fd/- [ ] links
- Reconnection support
- Look at contexts
- Heartbeat support by default
- Add higher level methods to update small sets of data, e.g. rows