- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.15
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- Navigate the APM UI
- Perform common tasks in the APM UI
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create and upload source maps (RUM)
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Explore mobile sessions with Discover
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- Use OpenTelemetry
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- APM Server API
- APM UI API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Log monitoring
- Infrastructure monitoring
- AWS monitoring
- Azure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
Configure settings
editConfigure settings
editTo configure settings for the Infrastructure app in Kibana, go to Observability → Infrastructure → Inventory or Hosts, and click the Settings link at the top of the page. The following settings are available:
| Setting | Description |
|---|---|
Name |
Name of the source configuration. |
Indices |
Index pattern or patterns used to match Elasticsearch indices that contain metrics. The default patterns are |
Machine learning |
The minimum severity score required to display anomalies in the Infrastructure app. The default is 50. |
Click Apply to save your changes.
The patterns used to match log sources are configured in the Logs app. The
default setting is logs-*,filebeat-*,kibana_sample_data_logs*. To change the
default, refer to Configure data sources.
If the fields are grayed out and cannot be edited, you may not have sufficient privileges to change the source configuration. For more information see Granting access to Kibana.
If Spaces are enabled in your Kibana instance, any configuration changes you make here are specific to the current space. You can make different subsets of data available by creating multiple spaces with different data source configurations.
Related settings
editYou can configure additional metrics settings in the Kibana configuration. For more information, refer to configuration settings in the Kibana documentation.
On this page