- 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
Run Universal Profiling on self-hosted Elastic stack
editRun Universal Profiling on self-hosted Elastic stack
editTo run Universal Profiling on self-hosted Elastic stack, you need an appropriate license.
Here you’ll find information on running Universal Profiling when hosting the Elastic stack on your own infrastructure.
Universal Profiling consists of a client part (the Universal Profiling Agent) and a server part (the backend). This documentation focuses on the server part.
Prerequisites
edit- Elastic stack: minimum version 8.12.0, on any Linux distribution (x86_64 or ARM64 architectures), with a Kernel 4.x or higher.
- ECE: minimum version 3.7.0, using the 8.12.0 stackpack or higher.
- Kubernetes: version 1.22+, using Helm charts.
For Elastic Cloud on Kubernetes (ECK), the Universal Profiling backend can be installed using helm charts in standalone mode. Once installed, you can connect the profiling backend to an existing ECK-managed stack. Currently, we do not have Profiling Operators and the CRDs necessary for running the Profiling backend natively in ECK.
Supported platforms
editThe following platforms were tested and successfully ran the Universal Profiling backend.
| Platform | OS | Details |
|---|---|---|
Linux x86_64, ARM64 |
Ubuntu 20.04 LTS |
|
Linux x86_64, ARM64 |
Ubuntu 22.04 LTS |
|
Linux x86_64, ARM64 |
Debian Bullseye |
|
Linux x86_64, ARM64 |
Debian Bookworm |
|
Linux x86_64, ARM64 |
Fedora 37 |
|
Linux x86_64, ARM64 |
Fedora 38 |
|
Linux x86_64, ARM64 |
RHEL 9.3 |
|
Linux x86_64, ARM64 |
RHEL 8.9 |
|
Linux x86_64, ARM64 |
openSUSE Leap |
|
Linux x86_64, ARM64 |
SUSE Linux Enterprise 15 |
|
Kubernetes 1.25, 1.26, 1.27 |
Linux x86_64/ARM64 |
|
Architecture overview
editThe backend is made up of two services: the collector and the symbolizer.
- The collector receives profiling data from the Universal Profiling Agents and sends it to Elasticsearch. It listens on an HTTP server and serves a gRPC endpoint.
- The symbolizer processes debug symbols that are not available on the Universal Profiling Agent, and symbolizes native frames from OS packages. It also listens on an HTTP server and serves an endpoint to upload private debug symbols. Refer to Adding symbols for more information on the importance of adding symbols.
