|
|
|
#ifndef LIGHTNING_LIGHTNINGD_LOG_H
|
|
|
|
#define LIGHTNING_LIGHTNINGD_LOG_H
|
|
|
|
#include "config.h"
|
plugin: Add new notification type: warning
This notification bases on `LOG_BROKEN` and `LOG_UNUSUAL` level log.
--Introduction
A notification for topic `warning` is sent every time a new `BROKEN`/
`UNUSUAL` level(in plugins, we use `error`/`warn`) log generated, which
means an unusual/borken thing happens, such as channel failed,
message resolving failed...
```json
{
"warning": {
"level": "warn",
"time": "1559743608.565342521",
"source": "lightningd(17652): 0821f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c chan #7854:",
"log": "Peer permanent failure in CHANNELD_NORMAL: lightning_channeld: sent ERROR bad reestablish dataloss msg"
}
}
```
1. `level` is `warn` or `error`:
`warn` means something seems bad happened and it's under control, but
we'd better check it;
`error` means something extremely bad is out of control, and it may lead
to crash;
2. `time` is the second since epoch;
3. `source`, in fact, is the `prefix` of the log_entry. It means where
the event happened, it may have the following forms:
`<node_id> chan #<db_id_of_channel>:`, `lightningd(<lightningd_pid>):`,
`plugin-<plugin_name>:`, `<daemon_name>(<daemon_pid>):`, `jsonrpc:`,
`jcon fd <error_fd_to_jsonrpc>:`, `plugin-manager`;
4. `log` is the context of the original log entry.
--Note:
1. The main code uses `UNUSUAL`/`BROKEN`, and plugin module uses `warn`
/`error`, considering the consistency with plugin, warning choose `warn`
/`error`. But users who use c-lightning with plugins may want to
`getlog` with specified level when receive warning. It's the duty for
plugin dev to turn `warn`/`error` into `UNUSUAL`/`BROKEN` and present it
to the users, or pass it directly to `getlog`;
2. About time, `json_log()` in `log` module uses the Relative Time, from
the time when `log_book` inited to the time when this event happend.
But I consider the `UNUSUAL`/`BROKEN` event is rare, and it is very
likely to happen after running for a long time, so for users, they will
pay more attention to Absolute Time.
-- Related Change
1. Remove the definitions of `log`, `log_book`, `log_entry` from `log.c`
to `log.h`, then they can be used in warning declaration and definition.
2. Remove `void json_add_time(struct json_stream *result, const char
*fieldname, struct timespec ts)` from `log.c` to `json.c`, and add
related declaration in `json.h`. Now the notification function in
`notification.c` can call it.
2. Add a pointer to `struct lightningd` in `struct log_book`. This may
affect the independence of the `log` module, but storing a pointer to
`ld` is more direct;
6 years ago
|
|
|
#include <ccan/list/list.h>
|
|
|
|
#include <ccan/tal/tal.h>
|
|
|
|
#include <ccan/time/time.h>
|
|
|
|
#include <ccan/typesafe_cb/typesafe_cb.h>
|
|
|
|
#include <common/status.h>
|
|
|
|
#include <common/type_to_string.h>
|
|
|
|
#include <jsmn.h>
|
|
|
|
#include <stdarg.h>
|
|
|
|
|
|
|
|
struct command;
|
|
|
|
struct json_stream;
|
|
|
|
struct lightningd;
|
|
|
|
struct timerel;
|
|
|
|
|
plugin: Add new notification type: warning
This notification bases on `LOG_BROKEN` and `LOG_UNUSUAL` level log.
--Introduction
A notification for topic `warning` is sent every time a new `BROKEN`/
`UNUSUAL` level(in plugins, we use `error`/`warn`) log generated, which
means an unusual/borken thing happens, such as channel failed,
message resolving failed...
```json
{
"warning": {
"level": "warn",
"time": "1559743608.565342521",
"source": "lightningd(17652): 0821f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c chan #7854:",
"log": "Peer permanent failure in CHANNELD_NORMAL: lightning_channeld: sent ERROR bad reestablish dataloss msg"
}
}
```
1. `level` is `warn` or `error`:
`warn` means something seems bad happened and it's under control, but
we'd better check it;
`error` means something extremely bad is out of control, and it may lead
to crash;
2. `time` is the second since epoch;
3. `source`, in fact, is the `prefix` of the log_entry. It means where
the event happened, it may have the following forms:
`<node_id> chan #<db_id_of_channel>:`, `lightningd(<lightningd_pid>):`,
`plugin-<plugin_name>:`, `<daemon_name>(<daemon_pid>):`, `jsonrpc:`,
`jcon fd <error_fd_to_jsonrpc>:`, `plugin-manager`;
4. `log` is the context of the original log entry.
--Note:
1. The main code uses `UNUSUAL`/`BROKEN`, and plugin module uses `warn`
/`error`, considering the consistency with plugin, warning choose `warn`
/`error`. But users who use c-lightning with plugins may want to
`getlog` with specified level when receive warning. It's the duty for
plugin dev to turn `warn`/`error` into `UNUSUAL`/`BROKEN` and present it
to the users, or pass it directly to `getlog`;
2. About time, `json_log()` in `log` module uses the Relative Time, from
the time when `log_book` inited to the time when this event happend.
But I consider the `UNUSUAL`/`BROKEN` event is rare, and it is very
likely to happen after running for a long time, so for users, they will
pay more attention to Absolute Time.
-- Related Change
1. Remove the definitions of `log`, `log_book`, `log_entry` from `log.c`
to `log.h`, then they can be used in warning declaration and definition.
2. Remove `void json_add_time(struct json_stream *result, const char
*fieldname, struct timespec ts)` from `log.c` to `json.c`, and add
related declaration in `json.h`. Now the notification function in
`notification.c` can call it.
2. Add a pointer to `struct lightningd` in `struct log_book`. This may
affect the independence of the `log` module, but storing a pointer to
`ld` is more direct;
6 years ago
|
|
|
struct log_entry {
|
|
|
|
struct list_node list;
|
|
|
|
struct timeabs time;
|
|
|
|
enum log_level level;
|
|
|
|
unsigned int skipped;
|
|
|
|
const char *prefix;
|
|
|
|
char *log;
|
|
|
|
/* Iff LOG_IO */
|
|
|
|
const u8 *io;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct log_book {
|
|
|
|
size_t mem_used;
|
|
|
|
size_t max_mem;
|
|
|
|
void (*print)(const char *prefix,
|
|
|
|
enum log_level level,
|
|
|
|
bool continued,
|
|
|
|
const struct timeabs *time,
|
|
|
|
const char *str,
|
|
|
|
const u8 *io, size_t io_len,
|
|
|
|
void *arg);
|
|
|
|
void *print_arg;
|
|
|
|
enum log_level print_level;
|
|
|
|
struct timeabs init_time;
|
|
|
|
|
|
|
|
struct list_head log;
|
|
|
|
/* Although log_book will copy log entries to parent log_book
|
|
|
|
* (the log_book belongs to lightningd), a pointer to lightningd
|
|
|
|
* is more directly because the notification needs ld->plugins.
|
|
|
|
*/
|
|
|
|
struct lightningd *ld;
|
plugin: Add new notification type: warning
This notification bases on `LOG_BROKEN` and `LOG_UNUSUAL` level log.
--Introduction
A notification for topic `warning` is sent every time a new `BROKEN`/
`UNUSUAL` level(in plugins, we use `error`/`warn`) log generated, which
means an unusual/borken thing happens, such as channel failed,
message resolving failed...
```json
{
"warning": {
"level": "warn",
"time": "1559743608.565342521",
"source": "lightningd(17652): 0821f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c chan #7854:",
"log": "Peer permanent failure in CHANNELD_NORMAL: lightning_channeld: sent ERROR bad reestablish dataloss msg"
}
}
```
1. `level` is `warn` or `error`:
`warn` means something seems bad happened and it's under control, but
we'd better check it;
`error` means something extremely bad is out of control, and it may lead
to crash;
2. `time` is the second since epoch;
3. `source`, in fact, is the `prefix` of the log_entry. It means where
the event happened, it may have the following forms:
`<node_id> chan #<db_id_of_channel>:`, `lightningd(<lightningd_pid>):`,
`plugin-<plugin_name>:`, `<daemon_name>(<daemon_pid>):`, `jsonrpc:`,
`jcon fd <error_fd_to_jsonrpc>:`, `plugin-manager`;
4. `log` is the context of the original log entry.
--Note:
1. The main code uses `UNUSUAL`/`BROKEN`, and plugin module uses `warn`
/`error`, considering the consistency with plugin, warning choose `warn`
/`error`. But users who use c-lightning with plugins may want to
`getlog` with specified level when receive warning. It's the duty for
plugin dev to turn `warn`/`error` into `UNUSUAL`/`BROKEN` and present it
to the users, or pass it directly to `getlog`;
2. About time, `json_log()` in `log` module uses the Relative Time, from
the time when `log_book` inited to the time when this event happend.
But I consider the `UNUSUAL`/`BROKEN` event is rare, and it is very
likely to happen after running for a long time, so for users, they will
pay more attention to Absolute Time.
-- Related Change
1. Remove the definitions of `log`, `log_book`, `log_entry` from `log.c`
to `log.h`, then they can be used in warning declaration and definition.
2. Remove `void json_add_time(struct json_stream *result, const char
*fieldname, struct timespec ts)` from `log.c` to `json.c`, and add
related declaration in `json.h`. Now the notification function in
`notification.c` can call it.
2. Add a pointer to `struct lightningd` in `struct log_book`. This may
affect the independence of the `log` module, but storing a pointer to
`ld` is more direct;
6 years ago
|
|
|
};
|
|
|
|
|
|
|
|
struct log {
|
|
|
|
struct log_book *lr;
|
|
|
|
const char *prefix;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* We can have a single log book, with multiple logs in it: it's freed
|
|
|
|
* by the last struct log itself. */
|
|
|
|
struct log_book *new_log_book(struct lightningd *ld, size_t max_mem,
|
|
|
|
enum log_level printlevel);
|
|
|
|
|
|
|
|
/* With different entry points */
|
|
|
|
struct log *new_log(const tal_t *ctx, struct log_book *record, const char *fmt, ...) PRINTF_FMT(3,4);
|
|
|
|
|
|
|
|
#define log_debug(log, ...) log_((log), LOG_DBG, false, __VA_ARGS__)
|
|
|
|
#define log_info(log, ...) log_((log), LOG_INFORM, false, __VA_ARGS__)
|
|
|
|
#define log_unusual(log, ...) log_((log), LOG_UNUSUAL, true, __VA_ARGS__)
|
|
|
|
#define log_broken(log, ...) log_((log), LOG_BROKEN, true, __VA_ARGS__)
|
|
|
|
|
|
|
|
void log_io(struct log *log, enum log_level dir, const char *comment,
|
|
|
|
const void *data, size_t len);
|
|
|
|
|
|
|
|
void log_(struct log *log, enum log_level level, bool call_notifier, const char *fmt, ...)
|
|
|
|
PRINTF_FMT(4,5);
|
|
|
|
void log_add(struct log *log, const char *fmt, ...) PRINTF_FMT(2,3);
|
|
|
|
void logv(struct log *log, enum log_level level, bool call_notifier, const char *fmt, va_list ap);
|
|
|
|
void logv_add(struct log *log, const char *fmt, va_list ap);
|
|
|
|
|
|
|
|
enum log_level get_log_level(struct log_book *lr);
|
|
|
|
void set_log_level(struct log_book *lr, enum log_level level);
|
|
|
|
void set_log_prefix(struct log *log, const char *prefix);
|
|
|
|
const char *log_prefix(const struct log *log);
|
|
|
|
struct log_book *get_log_book(const struct log *log);
|
|
|
|
|
|
|
|
#define set_log_outfn(lr, print, arg) \
|
|
|
|
set_log_outfn_((lr), \
|
|
|
|
typesafe_cb_preargs(void, void *, (print), (arg),\
|
|
|
|
const char *, \
|
|
|
|
enum log_level, \
|
|
|
|
bool, \
|
|
|
|
const struct timeabs *, \
|
|
|
|
const char *, \
|
|
|
|
const u8 *, size_t), (arg))
|
|
|
|
|
|
|
|
/* If level == LOG_IO_IN/LOG_IO_OUT, then io contains data */
|
|
|
|
void set_log_outfn_(struct log_book *lr,
|
|
|
|
void (*print)(const char *prefix,
|
|
|
|
enum log_level level,
|
|
|
|
bool continued,
|
|
|
|
const struct timeabs *time,
|
|
|
|
const char *str,
|
|
|
|
const u8 *io, size_t io_len,
|
|
|
|
void *arg),
|
|
|
|
void *arg);
|
|
|
|
|
|
|
|
size_t log_max_mem(const struct log_book *lr);
|
|
|
|
size_t log_used(const struct log_book *lr);
|
|
|
|
const struct timeabs *log_init_time(const struct log_book *lr);
|
|
|
|
|
|
|
|
#define log_each_line(lr, func, arg) \
|
|
|
|
log_each_line_((lr), \
|
|
|
|
typesafe_cb_preargs(void, void *, (func), (arg), \
|
|
|
|
unsigned int, \
|
|
|
|
struct timerel, \
|
|
|
|
enum log_level, \
|
|
|
|
const char *, \
|
|
|
|
const char *, \
|
|
|
|
const u8 *), (arg))
|
|
|
|
|
|
|
|
void log_each_line_(const struct log_book *lr,
|
|
|
|
void (*func)(unsigned int skipped,
|
|
|
|
struct timerel time,
|
|
|
|
enum log_level level,
|
|
|
|
const char *prefix,
|
|
|
|
const char *log,
|
|
|
|
const u8 *io,
|
|
|
|
void *arg),
|
|
|
|
void *arg);
|
|
|
|
|
|
|
|
|
|
|
|
void opt_register_logging(struct lightningd *ld);
|
|
|
|
|
|
|
|
char *arg_log_to_file(const char *arg, struct lightningd *ld);
|
|
|
|
|
|
|
|
/* Once this is set, we dump fatal with a backtrace to this log */
|
|
|
|
extern struct log *crashlog;
|
|
|
|
void NORETURN PRINTF_FMT(1,2) fatal(const char *fmt, ...);
|
|
|
|
|
|
|
|
void log_backtrace_print(const char *fmt, ...);
|
|
|
|
void log_backtrace_exit(void);
|
|
|
|
|
|
|
|
/* Adds an array showing log entries */
|
|
|
|
void json_add_log(struct json_stream *result,
|
|
|
|
const struct log_book *lr, enum log_level minlevel);
|
|
|
|
|
|
|
|
struct command_result *param_loglevel(struct command *cmd,
|
|
|
|
const char *name,
|
|
|
|
const char *buffer,
|
|
|
|
const jsmntok_t *tok,
|
|
|
|
enum log_level **level);
|
|
|
|
|
|
|
|
#endif /* LIGHTNING_LIGHTNINGD_LOG_H */
|