-
Notifications
You must be signed in to change notification settings - Fork 3.5k
/
en.yml
224 lines (221 loc) · 9.46 KB
/
en.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
# YAML notes
# |- means 'scalar block' useful for formatted text
# > means 'scalar block' but it chomps all newlines. Useful
# for unformatted text.
en:
oops: |-
An unexpected error occurred!
logstash:
environment:
jruby-required: >-
JRuby is required
missing-jars: >-
Could not find jar files under %{pattern}
pipeline:
worker-error: |-
A plugin had an unrecoverable error. Will restart this plugin.
Plugin: %{plugin}
Error: %{error}
worker-error-debug: |-
A plugin had an unrecoverable error. Will restart this plugin.
Plugin: %{plugin}
Error: %{error}
Exception: %{exception}
Stack: %{stacktrace}
plugin-loading-error: >-
Couldn't find any %{type} plugin named '%{name}'. Are you
sure this is correct? Trying to load the %{name} %{type} plugin
resulted in this error: %{error}
plugin-type-loading-error: >-
Could not find any plugin type named '%{type}'. Check for typos.
Valid plugin types are 'input' 'filter' and 'output'
output-worker-unsupported: >-
%{plugin} output plugin: setting 'workers => %{worker_count}' is not
supported by this plugin. I will continue working as if you had not set
this setting.
output-worker-unsupported-with-message: >-
%{plugin} output plugin: setting 'workers => %{worker_count}' is not
supported by this plugin. I will continue working as if you had not set
this setting. Reason: %{message}
plugin:
deprecated_milestone: >-
%{plugin} plugin is using the 'milestone' method to declare the version
of the plugin this method is deprecated in favor of declaring the
version inside the gemspec.
no_version: >-
%{name} plugin doesn't have a version. This plugin isn't well
supported by the community and likely has no maintainer.
version:
0-9-x:
Using version 0.9.x %{type} plugin '%{name}'. This plugin should work but
would benefit from use by folks like you. Please let us know if you
find bugs or have suggestions on how to improve this plugin.
0-1-x: >-
Using version 0.1.x %{type} plugin '%{name}'. This plugin isn't well
supported by the community and likely has no maintainer.
agent:
sighup: >-
SIGHUP received.
missing-configuration: >-
No configuration file was specified. Perhaps you forgot to provide
the '-f yourlogstash.conf' flag?
invalid-configuration: >-
The given configuration is invalid. Reason: %{error}
reload-without-config-path: >-
Configuration reloading also requires passing a configuration path with '-f yourlogstash.conf'
error: >-
Error: %{error}
sigint: >-
SIGINT received. Shutting down the agent.
sigterm: >-
SIGTERM received. Shutting down the agent.
slow_shutdown: |-
Received shutdown signal, but pipeline is still waiting for in-flight events
to be processed. Sending another ^C will force quit Logstash, but this may cause
data loss.
forced_sigint: >-
SIGINT received. Terminating immediately..
non_reloadable_config_reload: >-
Unable to reload configuration because it does not support dynamic reloading
non_reloadable_config_register: |-
Logstash was not able to load configuration since it does not support
dynamic reloading and -r or --auto-reload flag was enabled
configtest-flag-information: |-
You may be interested in the '--configtest' flag which you can
use to validate logstash's configuration before you choose
to restart a running system.
configuration:
obsolete: >-
The setting `%{name}` in plugin `%{plugin}` is obsolete and is no
longer available. %{extra} If you have any questions about this, you
are invited to visit https://discuss.elastic.co/c/logstash and ask.
file-not-found: |-
No config files found: %{path}
Can you make sure this path is a logstash config file?
scheme-not-supported: |-
URI scheme not supported: %{path}
Either pass a local file path or "file|http://" URI
fetch-failed: |-
Unable to fetch config from: %{path}
Reason: %{message}
setting_missing: |-
Missing a required setting for the %{plugin} %{type} plugin:
%{type} {
%{plugin} {
%{setting} => # SETTING MISSING
...
}
}
setting_invalid: |-
Invalid setting for %{plugin} %{type} plugin:
%{type} {
%{plugin} {
# This setting must be a %{value_type}
# %{note}
%{setting} => %{value}
...
}
}
invalid_plugin_settings: >-
Something is wrong with your configuration.
invalid_plugin_settings_duplicate_keys: |-
Duplicate keys found in your configuration: [%{keys}]
At line: %{line}, column %{column} (byte %{byte})
after %{after}
invalid_plugin_register: >-
Cannot register %{plugin} %{type} plugin.
The error reported is:
%{error}
plugin_path_missing: >-
You specified a plugin path that does not exist: %{path}
no_plugins_found: |-
Could not find any plugins in "%{path}"
I tried to find files matching the following, but found none:
%{plugin_glob}
log_file_failed: |-
Failed to open %{path} for writing: %{error}
This is often a permissions issue, or the wrong
path was specified?
flag:
# Note: Wrap these at 55 chars so they display nicely when clamp emits
# them in an 80-character terminal
config: |+
Load the logstash config from a specific file
or directory. If a directory is given, all
files in that directory will be concatenated
in lexicographical order and then parsed as a
single config file. You can also specify
wildcards (globs) and any matched files will
be loaded in the order described above.
config-string: |+
Use the given string as the configuration
data. Same syntax as the config file. If no
input is specified, then the following is
used as the default input:
"%{default_input}"
and if no output is specified, then the
following is used as the default output:
"%{default_output}"
If you wish to use both defaults, please use
the empty string for the '-e' flag.
configtest: |+
Check configuration for valid syntax and then exit.
allow-env: |+
EXPERIMENTAL. Enables templating of environment variable
values. Instances of "${VAR}" in strings will be replaced
with the respective environment variable value named "VAR".
pipeline-workers: |+
Sets the number of pipeline workers to run.
filterworkers: |+
DEPRECATED. Now an alias for --pipeline-workers and -w
pipeline-batch-size: |+
Size of batches the pipeline is to work in.
pipeline-batch-delay: |+
When creating pipeline batches, how long to wait while polling
for the next event.
auto_reload: |+
Monitor configuration changes and reload
whenever it is changed.
NOTE: use SIGHUP to manually reload the config
reload_interval: |+
How frequently to poll the configuration location
for changes, in seconds.
log: |+
Write logstash internal logs to the given
file. Without this flag, logstash will emit
logs to standard output.
verbosity: |+
Increase verbosity of logstash internal logs.
Specifying once will show 'informational'
logs. Specifying twice will show 'debug'
logs. This flag is deprecated. You should use
--verbose or --debug instead.
version: |+
Emit the version of logstash and its friends,
then exit.
pluginpath: |+
A path of where to find plugins. This flag
can be given multiple times to include
multiple paths. Plugins are expected to be
in a specific directory hierarchy:
'PATH/logstash/TYPE/NAME.rb' where TYPE is
'inputs' 'filters', 'outputs' or 'codecs'
and NAME is the name of the plugin.
quiet: |+
Quieter logstash logging. This causes only
errors to be emitted.
verbose: |+
More verbose logging. This causes 'info'
level logs to be emitted.
debug: |+
Most verbose logging. This causes 'debug'
level logs to be emitted.
debug-config: |+
Print the compiled config ruby code out as a debug log (you must also have --debug enabled).
WARNING: This will include any 'password' options passed to plugin configs as plaintext, and may result
in plaintext passwords appearing in your logs!
unsafe_shutdown: |+
Force logstash to exit during shutdown even
if there are still inflight events in memory.
By default, logstash will refuse to quit until all
received events have been pushed to the outputs.