-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
c474466
commit 5901fd8
Showing
1 changed file
with
2 additions
and
26 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,5 @@ | ||
# jaeger_storage | ||
|
||
This module implements an extension that allows to configure different storage backends that implement Jaeger's V1 storage APIs. The usual OpenTelemetry Collector's pipeline of receiver-processor-exporter does not require this because each exporter can be supporting just one storage backend, and many of then can be wired up via the pipeline. But in order to run `jaeger-query` service, which is not a part of the pipeline, we need the ability to access a shared storage backend implementations, and this extension serves as such shared container. | ||
This module implements an extension that allows to configure different storage backends that implement Jaeger Storage API. The usual OpenTelemetry Collector's pipeline of receiver-processor-exporter does not require this because each exporter can be supporting just one storage backend, and many of then can be wired up via the pipeline. But in order to run `jaeger-query` service, which is not a part of the pipeline, we need the ability to access shared storage backend implementations, and this extension serves as such shared container. | ||
|
||
## Configuration | ||
|
||
The extension can declare multiple storage backend implementations, separating them by storage type first, and then by user-assigned names. Here's an example that may lets [query-service](../jaegerquery/) extension use Cassandra as the main backend, but memory storage as Dependencies store: | ||
|
||
```yaml | ||
jaeger_storage: | ||
memory: | ||
memstore: | ||
max_traces: 100000 | ||
cassandra: | ||
cassandra_primary: | ||
servers: [...] | ||
namespace: jaeger | ||
cassandra_archive: | ||
servers: [...] | ||
namespace: jaeger_archive | ||
|
||
jaeger_query: | ||
trace_storage: cassandra_primary | ||
trace_archive: cassandra_archive | ||
dependencies: memstore | ||
metrics_store: prometheus_store | ||
``` | ||
NB: this is work in progress, only `memory` section is currently supported. | ||
See also https://www.jaegertracing.io/docs/latest/storage/. |