- Filebeat Reference: other versions:
- Overview
- Getting Started With Filebeat
- Step 1: Install Filebeat
- Step 2: Configure Filebeat
- Step 3: Configure Filebeat to use Logstash
- Step 4: Load the index template in Elasticsearch
- Step 5: Set up the Kibana dashboards
- Step 6: Start Filebeat
- Step 7: View the sample Kibana dashboards
- Quick start: modules for common log formats
- Repositories for APT and YUM
- Setting up and running Filebeat
- Upgrading Filebeat
- How Filebeat works
- Configuring Filebeat
- Specify which modules to run
- Configure inputs
- Manage multiline messages
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Set up index lifecycle management
- Load balance the output hosts
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Enrich events with geoIP information
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- filebeat.reference.yml
- Beats central management
- Modules
- Exported fields
- Alias fields
- Apache2 fields
- Auditd fields
- Beat fields
- Cloud provider metadata fields
- Docker fields
- elasticsearch fields
- haproxy fields
- Host fields
- Icinga fields
- IIS fields
- Kafka fields
- kibana fields
- Kubernetes fields
- Log file content fields
- logstash fields
- mongodb fields
- MySQL fields
- Nginx fields
- Osquery fields
- PostgreSQL fields
- Redis fields
- System fields
- Traefik fields
- Monitoring Filebeat
- Securing Filebeat
- Troubleshooting
- Migrating from Logstash Forwarder to Filebeat
- Contributing to Beats
Step 7: View the sample Kibana dashboards
editStep 7: View the sample Kibana dashboards
editTo make it easier for you to explore Filebeat data in Kibana, we’ve created
example Filebeat dashboards. You loaded the dashboards earlier when you
ran the setup command.
To open the dashboards, launch the Kibana web interface by pointing your browser
to port 5601. For example, http://localhost:5601.
Replace localhost with the name of the Kibana host. If you’re using an
Elastic Cloud instance, log in to your cloud account,
then navigate to the Kibana endpoint in your deployment.
On the Discover page, make sure that the predefined filebeat-* index
pattern is selected to see Filebeat data.
If you don’t see data in Kibana, try changing the date range to a larger range. By default, Kibana shows the last 15 minutes.
Go to the Dashboard page and select the dashboard that you want to open.
These dashboards are designed to work out-of-the box when you use Filebeat modules. However, you can also use them as examples and customize them to meet your needs even if you aren’t using Filebeat modules.
To populate the example dashboards with data, you need to either define ingest node pipelines or use Logstash to parse the data into the fields expected by the dashboards. If you are using Logstash, see the configuration examples in the Logstash documentation for help parsing the log formats supported by the dashboards.
Here is an example of the Filebeat system dashboard:
