- Journalbeat Reference for 6.5-7.15:
- Journalbeat overview
- Quick start: installation and configuration
- Set up and run
- Configure
- Inputs
- General settings
- Project paths
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_csv_fields
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- journalbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Journalbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
Starting in version 7.16, this experimental functionality has been removed. You
should use the journald input in Filebeat instead.
URL Decode
editURL Decode
editThe urldecode
processor specifies a list of fields to decode from URL encoded format. Under the fields
key, each entry contains a from: source-field
and a to: target-field
pair, where:
-
from
is the source field name -
to
is the target field name (defaults to thefrom
value)
processors: - urldecode: fields: - from: "field1" to: "field2" ignore_missing: false fail_on_error: true
In the example above:
- field1 is decoded in field2
The urldecode
processor has the following configuration settings:
-
ignore_missing
-
(Optional) If set to true, no error is logged in case a key
which should be URL-decoded is missing. Default is
false
. -
fail_on_error
-
(Optional) If set to true, in case of an error the URL-decoding
of fields is stopped and the original event is returned. If set to false, decoding
continues also if an error happened during decoding. Default is
true
.
See Conditions for a list of supported conditions.
Was this helpful?
Thank you for your feedback.