The Digma Engine is defined in a simple Docker Compose [file](https://github.com/digma-ai/digma/blob/main/docker/docker-compose.yml) that is available online and consists of four containers:
* `Digma Compound`- This container holds the Digma analytics engine for processing traces
* `Digma Persistence` - DBs and storage for processing the time series data and aggregating it
* `Jaeger` - An embedded Jaeger instance that also has additional features for linking spans with code
* `Digma DS` - All of the data science and ML logic for detecting anomalies, calculating correlations, etc
### Default Ports
The following are the default ports used by Digma:
* `5050` is used to collect observability data. This will use the OTEL standard so can accept traces from any OTLP exporter.
* `5051` is used as a backend API for the plugin. The plugin uses it to retrieve and render the insights and processed data
* `17686` is the default embedded Jaeger port. This is used to render the visualization for traces including code location data.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.digma.ai/digma-developer-guide/installation/readme-1/local-install-architecture.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.