- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick starts
- Migrate from Beats to Elastic Agent
- Deployment models
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Install Elastic Agent on Kubernetes using Helm
- Example: Install standalone Elastic Agent on Kubernetes using Helm
- Example: Install Fleet-managed Elastic Agent on Kubernetes using Helm
- Advanced Elastic Agent configuration managed by Fleet
- Configuring Kubernetes metadata enrichment on Elastic Agent
- Run Elastic Agent on GKE managed by Fleet
- Run Elastic Agent on Amazon EKS managed by Fleet
- Run Elastic Agent on Azure AKS managed by Fleet
- Run Elastic Agent Standalone on Kubernetes
- Scaling Elastic Agent on Kubernetes
- Using a custom ingest pipeline with the Kubernetes Integration
- Environment variables
- Run Elastic Agent as an OTel Collector
- Run Elastic Agent without administrative privileges
- Install Elastic Agent from an MSI package
- Installation layout
- Air-gapped environments
- Using a proxy server with Elastic Agent and Fleet
- Uninstall Elastic Agents from edge hosts
- Start and stop Elastic Agents on edge hosts
- Elastic Agent configuration encryption
- Secure connections
- Manage Elastic Agents in Fleet
- Configure standalone Elastic Agents
- Create a standalone Elastic Agent policy
- Structure of a config file
- Inputs
- Providers
- Outputs
- SSL/TLS
- Logging
- Feature flags
- Agent download
- Config file examples
- Grant standalone Elastic Agents access to Elasticsearch
- Example: Use standalone Elastic Agent with Elastic Cloud Serverless to monitor nginx
- Example: Use standalone Elastic Agent with Elasticsearch Service to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Package signatures
- Add an integration to an Elastic Agent policy
- View integration policies
- Edit or delete an integration policy
- Install and uninstall integration assets
- View integration assets
- Set integration-level outputs
- Upgrade an integration
- Managed integrations content
- Best practices for integration assets
- Data streams
- Define processors
- Processor syntax
- 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_cef
- decode_csv_fields
- decode_duration
- 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
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Command reference
- Troubleshoot
- Release notes
Config file example: Nginx HTTP Server
editConfig file example: Nginx HTTP Server
editInclude these sample settings in your standalone Elastic Agent elastic-agent.yml
configuration file to ingest data from Nginx HTTP Server.
Nginx HTTP Server logs
editoutputs: default: type: elasticsearch hosts: - '{elasticsearch-host-url}' api_key: "my_api_key" agent: download: sourceURI: 'https://artifacts.elastic.co/downloads/' monitoring: enabled: true use_output: default namespace: default logs: true metrics: true inputs: - id: "insert a unique identifier here" name: nginx-1 type: logfile use_output: default data_stream: namespace: default streams: - id: "insert a unique identifier here" data_stream: dataset: nginx.access type: logs ignore_older: 72h paths: - /var/log/nginx/access.log* tags: - nginx-access exclude_files: - .gz$ processors: - add_locale: null - id: "insert a unique identifier here" data_stream: dataset: nginx.error type: logs ignore_older: 72h paths: - /var/log/nginx/error.log* tags: - nginx-error exclude_files: - .gz$ multiline: pattern: '^\d{4}\/\d{2}\/\d{2} ' negate: true match: after processors: - add_locale: null
For available output settings, refer to Configure outputs for standalone Elastic Agents. |
|
For settings specific to the Elasticsearch output, refer to Configure the Elasticsearch output. |
|
The URL of the Elasticsearch cluster where output should be sent, including the port number. For example |
|
An API key used to authenticate with the Elasticsearch cluster. |
|
For available download settings, refer to Configure download settings for standalone Elastic Agent upgrades. |
|
For available monitoring settings, refer to Configure monitoring for standalone Elastic Agents. |
|
For available input settings, refer to Configure inputs for standalone Elastic Agents. |
|
A user-defined ID to uniquely identify the input stream. |
|
For available input types, refer to Elastic Agent inputs. |
|
Learn about Data streams for time series data. |
|
Specify a unique ID for each individual input stream. Naming the ID by appending the associated |
|
Refer to Logs reference in the Nginx HTTP integration documentation for the logs available to ingest and exported fields. |
|
Path to the log files to be monitored. |
Nginx HTTP Server metrics
editoutputs: default: type: elasticsearch hosts: - '{elasticsearch-host-url}' api_key: "my_api_key" agent: download: sourceURI: 'https://artifacts.elastic.co/downloads/' monitoring: enabled: true use_output: default namespace: default logs: true metrics: true inputs: - id: "insert a unique identifier here" type: nginx/metrics use_output: default data_stream: namespace: default streams: - id: "insert a unique identifier here" data_stream: dataset: nginx.stubstatus type: metrics metricsets: - stubstatus hosts: - 'http://127.0.0.1:80' period: 10s server_status_path: /nginx_status
For available output settings, refer to Configure outputs for standalone Elastic Agents. |
|
For settings specific to the Elasticsearch output, refer to Configure the Elasticsearch output. |
|
The URL of the Elasticsearch cluster where output should be sent, including the port number. For example |
|
An API key used to authenticate with the Elasticsearch cluster. |
|
For available download settings, refer to Configure download settings for standalone Elastic Agent upgrades. |
|
For available monitoring settings, refer to Configure monitoring for standalone Elastic Agents. |
|
For available input settings, refer to Configure inputs for standalone Elastic Agents. |
|
A user-defined ID to uniquely identify the input stream. |
|
For available input types, refer to Elastic Agent inputs. |
|
Learn about Data streams for time series data. |
|
Specify a unique ID for each individual input stream. Naming the ID by appending the associated |
|
A user-defined dataset. You can specify anything that makes sense to signify the source of the data. |
|
Refer to Metrics reference in the Nginx integration documentation for the type of metrics collected and exported fields. |
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now