You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation in Eclipse Hono helm charts mention a Kubernetes sidecar based usage of Jaeger in Hono components but the helm charts don't specify what needs to be done if Jaeger is deployed externally (i.e. without using Hono helm charts) and you want to use this external Jaeger deployment for Hono traces. Check e.g. jaeger architecture and deployment documentation for more info.
TODO 1. Deploy Jaeger with Hono Helm charts (See #41)
Check what Jaeger UI looks like when Hono sends traces to it.
Documentation for configuring Hono with Jaeger tracing available in Hono documentation: https://www.eclipse.org/hono/docs/dev/admin-guide/monitoring-tracing-config/#configuring-usage-of-jaeger-tracing-included-in-docker-images
2. Configure Jaeger (deployed with Hono helm charts) for persistent storage using Badger.
(One probably needs to modify/override the Hono helm charts)
3. Find out how Jaeger can be deployed externally and Hono helm charts can be configured to use the external Jaeger deployment. See #44
4. Deploy Elasticsearch backend
5. Configure Jaeger to use Elasticsearch
all-in-one Jaeger deployment (here) is suitable for testing & development using Kubernetes Operator, but otherwise Kubernetes Operator based deployment needs to be investigated; will really bring any pros with it compare to e.g. Helm and kubectl? https://www.jaegertracing.io/docs/1.21/operator/
The text was updated successfully, but these errors were encountered:
hjhsalo
changed the title
Jaeger: Investigate deployment possibilities
Jaeger: Deploy Jaeger with persistent storage
Mar 9, 2021
Eclipse Hono helm charts can deploy an example Jaeger deployment using jaeger-all-in-one image:
https://github.com/eclipse/packages/blob/2760401288f22048346287d12abf53bd3b12320c/charts/hono/values.yaml#L232-L275
Jaeger documentation says that all-in-one-image uses Badger as storage backend and it can be configured for persistent storage: (NOTE:
--badger.ephemeral=false
and-v <storage_dir_on_host>:/badger
)https://www.jaegertracing.io/docs/1.22/deployment/#badger---local-storage
Documentation in Eclipse Hono helm charts mention a Kubernetes sidecar based usage of Jaeger in Hono components but the helm charts don't specify what needs to be done if Jaeger is deployed externally (i.e. without using Hono helm charts) and you want to use this external Jaeger deployment for Hono traces. Check e.g. jaeger architecture and deployment documentation for more info.
TODO
1. Deploy Jaeger with Hono Helm charts (See #41)Check what Jaeger UI looks like when Hono sends traces to it.
Documentation for configuring Hono with Jaeger tracing available in Hono documentation:
https://www.eclipse.org/hono/docs/dev/admin-guide/monitoring-tracing-config/#configuring-usage-of-jaeger-tracing-included-in-docker-images
2. Configure Jaeger (deployed with Hono helm charts) for persistent storage using Badger.
(One probably needs to modify/override the Hono helm charts)
3. Find out how Jaeger can be deployed externally and Hono helm charts can be configured to use the external Jaeger deployment. See #44
4. Deploy Elasticsearch backend
5. Configure Jaeger to use Elasticsearch
Summary of Jaeger architecture is available here.
https://www.jaegertracing.io/docs/1.21/architecture/
https://www.jaegertracing.io/docs/1.21/deployment/
all-in-one Jaeger deployment (here) is suitable for testing & development using Kubernetes Operator, but otherwise Kubernetes Operator based deployment needs to be investigated; will really bring any pros with it compare to e.g. Helm and kubectl?https://www.jaegertracing.io/docs/1.21/operator/
The text was updated successfully, but these errors were encountered: