-
### Is your feature request related to a problem? Please describe.
Components should be able to speficy an atSign for loggung.
### Describe the solution you'd like
That atSign should be able to gat…
-
The command-line needs to print out information and errors for all sub-commands and we would benefit to have a single component responsible for this task. Right now we have a mixture of `log` and `fm…
-
## Story statement
**As a** [the beneficiary of this feature],
**I want** [what does the beneficiary want to be able to do?],
**So that** [what is the benefit or value of the feature?]
**And so …
-
Rather than having all the services store their own logs, they should be aggregated in canopy
-
Compendium should store loggers and have a command to change the logging level of each?
-
Previously, we had:
- InfluxDB for pipeline files & extraction statuses
- ELK stack at one point for python logging centralization
- Pipeline from Arizona just puts logs in text format
2018:
- …
-
Maybe use python mongoDB?
-
https://www.freeipa.org/page/Centralized_Logging
Log Gathering and Transport
To meet the defined use cases, at least following logs have to be gathered from the FreeIPA server:
/var/log/httpd/error_…
-
It'd be extremely useful to gather all application logs into centralized logging infrastructure to support investigations and debugging. Graylog and ELK are worth considering here, and it'd be ideal …
-
srv9 rsyslogd: centralize syslogging from every node including itself
- ~~some facilities (kern, user...) and levels (debug, info...) messages are never logged.~~
- ~~local failover: messages sent wh…