- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.14
- 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
- OpenTelemetry integration
- 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
- 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
Tag data for querying
editTag data for querying
editThe instructions to deploy the Universal Profiling Agent displayed in Add Data show a default configuration that allows ingesting data into an Elastic Cloud deployment.
The only config setting you may want to change is project-id
(default value is 1
).
The -project-id
flag, or the project-id
key in the Universal Profiling Agent configuration file, splits profiling data into logical groups that you control.
You can assign any non-zero, unsigned integer ⇐ 4095 to a Universal Profiling Agent deployment you control. In Kibana, the KQL field profiling.project.id
is mapped to project-id
and you can use it to split or filter data.
You may want to set a per-environment project ID (for example, dev=3, staging=2, production=1), a per-datacenter project ID (for example, DC1=1, DC2=2), or even a per-k8s-cluster project ID (for example, us-west2-production=100, eu-west1-production=101).
You can also use the -tags
flag to associate an arbitrary string with a specific Universal Profiling Agent instance.
Each tag must match ^[a-zA-Z0-9-:._]+$
regex and use ;
as a separator.
Invalid tags are dropped and warnings issued on startup.
In Kibana, you can use the KQL field tags
for filtering. For example, when running the Universal Profiling Agent with the following:
sudo pf-host-agent/pf-host-agent -project-id=1 -tags='cloud_region:us-central1;env:staging'
You can then filter profiling data from the Universal Profiling Agent in Kibana with the following tag:
tags : "cloud_region:us-central1"