aboutsummaryrefslogtreecommitdiff
path: root/contrib/epee/src/mlog.cpp (follow)
AgeCommit message (Collapse)AuthorFilesLines
2017-12-18mlog: terminate a string at last char, just in casemoneromooo-monero1-0/+1
2017-12-16move includes around to lessen overall loadmoneromooo-monero1-0/+4
2017-10-07frob level 1 logs a bit for consistencymoneromooo-monero1-1/+1
Level 1 logs map to INFO, so setting log level to 1 should show these. Demote some stuff to DEBUG to avoid spam, though.
2017-10-02Merge pull request #2512Riccardo Spagni1-4/+40
792ba4f0 Log categories can now be added to and removed from (moneromooo-monero) 48f92eb6 easylogging++: add categories getter (moneromooo-monero) f35afe62 epee: factor log level/categories setting (moneromooo-monero)
2017-09-22Log categories can now be added to and removed frommoneromooo-monero1-2/+39
Also, set_log without parameters now prints the log categories
2017-09-22epee: factor log level/categories settingmoneromooo-monero1-2/+1
2017-09-17daemon, wallet: add --max-log-file-size optionselsta1-2/+2
2017-08-15Tweak net logs so we get more info on why networking can't startmoneromooo-monero1-1/+1
This should prevent "silent" failures to start
2017-08-07Merge pull request #2189Riccardo Spagni1-1/+1
335fc8ab mlog: fix crash accessing stale data when rotating logs (moneromooo-monero)
2017-07-24mlog: default to msgwriter logs only for log level 1moneromooo-monero1-1/+1
There might be privacy issues doing it by default
2017-07-22mlog: fix crash accessing stale data when rotating logsmoneromooo-monero1-1/+1
2017-07-19Merge pull request #2173Riccardo Spagni1-1/+1
a02d7458 mlog: make MONERO_LOGS env var understand N,logs type spec (moneromooo-monero)
2017-07-15mlog: make MONERO_LOGS env var understand N,logs type specmoneromooo-monero1-1/+1
2017-07-06mlog: add msgwriter:INFO to log 0 and 1 defaultsmoneromooo-monero1-2/+2
This ensures command output gets logged by default
2017-05-17shared libs build (i.e. make debug)stoffu1-2/+0
2017-04-01mlog: direct log category changes to file onlymoneromooo-monero1-4/+9
Because some people just won't even try to read what is written and freak out because the word FATAL is in here, despite the context making it clear it's not an error.
2017-03-19Revert "Increase the log level for the info about log levels"moneromooo-monero1-2/+2
We want to know which log categories are active. This reverts commit 4f7bce6d20c72a1384289f7c35b7fe0ee796ed41.
2017-03-03Merge pull request #1805Riccardo Spagni1-1/+1
b7f85a30 mlog: default net.cn to FATAL (moneromooo-monero)
2017-02-26mlog: default net.cn to FATALmoneromooo-monero1-1/+1
Errors in this layer depend on how peers behave, and thus errors are expected
2017-02-25Increase the log level for the info about log levelsNano Akron1-2/+2
2017-02-21mlog: restrict net.p2p to FATAL by defaultmoneromooo-monero1-1/+1
2017-02-20mlog: only silence errors for net by default, not net.*moneromooo-monero1-1/+1
2017-02-12mlog: move log level changes to global levelmoneromooo-monero1-2/+2
Makes it more likely to show up
2017-02-12mlog: s/Mew/New/ in logmoneromooo-monero1-2/+2
2017-02-04Merge pull request #1670Riccardo Spagni1-1/+6
c3d7a198 mlog: probable fix for gmtime_r not being available on windows (moneromooo-monero)
2017-02-04mlog: fix default logging being not verbose enoughmoneromooo-monero1-27/+27
2017-02-04mlog: probable fix for gmtime_r not being available on windowsmoneromooo-monero1-1/+6
2017-01-22mlog: allow using numerical level as default prefixmoneromooo-monero1-25/+37
eg, 2,foo:ERROR,bar:INFO
2017-01-22Merge pull request #1613Riccardo Spagni1-2/+2
13dd102e mlog: fix default level/category mapping (moneromooo-monero)
2017-01-22Merge pull request #1604Riccardo Spagni1-2/+2
a854cec3 Make stack trace show up in log file with default settings (moneromooo-monero)
2017-01-22mlog: fix default level/category mappingmoneromooo-monero1-2/+2
It was not matching the LOG_PRINT_Lx mapping for 2/3/4
2017-01-21Make stack trace show up in log file with default settingsmoneromooo-monero1-2/+2
2017-01-16mlog: allow overriding log formatmoneromooo-monero1-2/+4
using the MONERO_LOG_FORMAT environment variable. Default is: %datetime{%Y-%M-%d %H:%m:%s.%g}\t%thread\t%level\t%logger\t%loc\t%msg Field list in easylogging++ documentation. Don't forget to escape as needed.
2017-01-16Change logging to easylogging++moneromooo-monero1-0/+319
This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 12:37:46 +0000