- Metricbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting started with Metricbeat
- Setting up and running Metricbeat
- Upgrading Metricbeat
- How Metricbeat works
- Configuring Metricbeat
- Specify which modules to run
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse logs by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Set up logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- metricbeat.reference.yml
- Modules
- Aerospike module
- Apache module
- Ceph module
- Couchbase module
- Docker module
- Dropwizard module
- Elasticsearch module
- Golang module
- HAProxy module
- HTTP module
- Jolokia module
- Kafka module
- Kibana module
- Kubernetes module
- Kubernetes container metricset
- Kubernetes event metricset
- Kubernetes node metricset
- Kubernetes pod metricset
- Kubernetes state_container metricset
- Kubernetes state_deployment metricset
- Kubernetes state_node metricset
- Kubernetes state_pod metricset
- Kubernetes state_replicaset metricset
- Kubernetes system metricset
- Kubernetes volume metricset
- Memcached module
- MongoDB module
- MySQL module
- Nginx module
- PHP-FPM module
- PostgreSQL Module
- Prometheus module
- RabbitMQ module
- Redis module
- System module
- vSphere module
- Windows module
- ZooKeeper module
- Exported Fields
- Aerospike Fields
- Apache Fields
- Beat Fields
- Ceph Fields
- Cloud Provider Metadata Fields
- Common Fields
- Couchbase Fields
- docker Fields
- Docker Fields
- Dropwizard Fields
- Elasticsearch Fields
- Golang Fields
- HAProxy Fields
- HTTP Fields
- Jolokia Fields
- Kafka Fields
- Kibana Fields
- kubernetes Fields
- Kubernetes Fields
- Memcached Fields
- MongoDB Fields
- MySQL Fields
- Nginx Fields
- PHP-FPM Fields
- PostgreSQL Fields
- Prometheus Fields
- RabbitMQ Fields
- Redis Fields
- System Fields
- vSphere Fields
- Windows Fields
- ZooKeeper Fields
- Securing Metricbeat
- Troubleshooting
WARNING: Version 6.0 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Decode JSON fields
editDecode JSON fields
editThe decode_json_fields processor decodes fields containing JSON strings and
replaces the strings with valid JSON objects.
processors: - decode_json_fields: fields: ["field1", "field2", ...] process_array: false max_depth: 1 target: "" overwrite_keys: false
The decode_json_fields processor has the following configuration settings:
-
fields - The fields containing JSON strings to decode.
-
process_array - (Optional) A boolean that specifies whether to process arrays. The default is false.
-
max_depth - (Optional) The maximum parsing depth. The default is 1.
-
target -
(Optional) The field under which the decoded JSON will be written. By
default the decoded JSON object replaces the string field from which it was
read. To merge the decoded JSON fields into the root of the event, specify
targetwith an empty string (target: ""). Note that thenullvalue (target:) is treated as if the field was not set at all. -
overwrite_keys - (Optional) A boolean that specifies whether keys that already exist in the event are overwritten by keys from the decoded JSON object. The default value is false.
Was this helpful?
Thank you for your feedback.