- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.17
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- 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
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Known issues
editKnown issues
editUniversal Profiling has the following known issues:
Helm chart profiling-collector faulty binary location
editAffected: 8.16.0, 8.16.1, 8.16.2, 8.17.0 Fixed in: 8.16.3+, 8.17.1+
The installation of Universal Profiling collector using the Helm chart profiling-collector produces a Deployment with
the wrong binary path set in spec.template.spec.containers['pf-elastic-collector'].command.
The correct path should be /home/nonroot/pf-elastic-collector while the command field references the deprecated path
/root/pf-elastic-collector. This issue prevents the collector from starting and as a result, the Deployment has Pods
in CrashLoopBackoff status.
To fix this issue, a manual edit of the Deployment manifest should be performed, removing entirely the command field
from the spec section.
This can be performed by either manipulating the Deployment template emitted by Helm or by using the kubectl edit command.