Documentation ¶
Index ¶
Constants ¶
View Source
const ( CONFIG_OPTION_NAME = "config" BUFFER_SIZE_NAME = "buffer-size" PARSE_PATTERN_NAME = "pattern" PARSE_PATTERN_NAME_NAME = "pattern-name" FOLLOW_NAME = "follow" DISABLE_REGEX_ESCAPE = "disable-regex-escape" )
Option names
View Source
const (
DEFAULT_BUFFER_SIZE = 10000
)
Default values
Variables ¶
View Source
var LONG_DESCRIPTION = fmt.Sprintf(`By default loggy reads from STDIN or you can specify file path to read the logs from specific file. You quit the application by pressing Ctrl+C. Configuration ------------- All options that can be passed using CLI flags can be configured using config file or environment variables. loggy looks for a config file ".loggy.toml" in current working directory and in $HOME folder. Moreover you can use environment variables with "LOGGY_" prefix, where for example flag "--pattern" would be "LOGGY_PATTERN" env. variable. The order of precedence is: $HOME config > CWD config > --config config > Env. variables > CLI flags. Parsing pattern --------------- %s Pattern names ------------- In your config file you can create a [patterns] section where you can predefine your patterns using <name>="<pattern>" syntax and then use --pattern-name/-n flag to use it. Filter ------ %s Keyboard shortcuts ------------------ %s %s %s `, ui.HelpParsingPatternText, ui.HelpFilterText, ui.HelpHomeText, ui.HelpNavigationText, ui.HelpInputsText)
Functions ¶
Types ¶
This section is empty.
Click to show internal directories.
Click to hide internal directories.