Skip to content

Conversation

chahatsagarmain
Copy link
Contributor

  • This setup provides a working Jaeger demo deployment with the HotROD application and Span Metrics Processor (SPM) enabled.
  • It currently uses in-memory storage for traces and Prometheus as the metrics backend.
  • In the future, we plan to use Elasticsearch as a unified storage solution for both traces and metrics.
  • Minor changes (e.g., switching from ClusterIP to LoadBalancer) with other production practices are still required for production readiness. These will be addressed in upcoming PRs.
  • Below are some screenshots from a successful local deployment on a kind cluster:
    Screenshot_20250626_083704
    Screenshot_20250626_083649

Checklist

@chahatsagarmain chahatsagarmain requested a review from a team as a code owner June 26, 2025 03:25
@chahatsagarmain chahatsagarmain marked this pull request as draft June 26, 2025 03:25
git clone https://github.com/jaegertracing/helm-charts.git
cd helm-charts
git checkout v2
````
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code block delimiter is inconsistent with the rest of the document. Please use triple backticks (```) instead of quadruple backticks (````) to maintain consistent formatting throughout the documentation.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

Copy link

codecov bot commented Jun 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.18%. Comparing base (461923b) to head (85c5c64).
Report is 10 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7262   +/-   ##
=======================================
  Coverage   96.18%   96.18%           
=======================================
  Files         369      369           
  Lines       22187    22187           
=======================================
  Hits        21341    21341           
  Misses        632      632           
  Partials      214      214           
Flag Coverage Δ
badger_v1 9.85% <ø> (ø)
badger_v2 1.89% <ø> (ø)
cassandra-4.x-v1-manual 14.81% <ø> (ø)
cassandra-4.x-v2-auto 1.88% <ø> (ø)
cassandra-4.x-v2-manual 1.88% <ø> (ø)
cassandra-5.x-v1-manual 14.81% <ø> (ø)
cassandra-5.x-v2-auto 1.88% <ø> (ø)
cassandra-5.x-v2-manual 1.88% <ø> (ø)
elasticsearch-6.x-v1 20.78% <ø> (ø)
elasticsearch-7.x-v1 20.83% <ø> (ø)
elasticsearch-8.x-v1 21.01% <ø> (ø)
elasticsearch-8.x-v2 1.89% <ø> (ø)
grpc_v1 11.39% <ø> (ø)
grpc_v2 1.89% <ø> (ø)
kafka-3.x-v1 10.21% <ø> (ø)
kafka-3.x-v2 1.89% <ø> (ø)
memory_v2 1.89% <ø> (ø)
opensearch-1.x-v1 20.88% <ø> (ø)
opensearch-2.x-v1 20.88% <ø> (ø)
opensearch-2.x-v2 1.89% <ø> (ø)
query 1.89% <ø> (ø)
tailsampling-processor 0.52% <ø> (ø)
unittests 95.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jkowall
Copy link
Contributor

jkowall commented Jun 26, 2025

Draft looks good aside from what the bot pointed out where you have a typo. I did not test it since I do not have a cluster on this machine.

…gertracing#7257)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/prometheus/common](https://redirect.github.com/prometheus/common)
| `v0.64.0` -> `v0.65.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fprometheus%2fcommon/v0.65.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fprometheus%2fcommon/v0.65.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fprometheus%2fcommon/v0.64.0/v0.65.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fprometheus%2fcommon/v0.64.0/v0.65.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

<details>
<summary>prometheus/common (github.com/prometheus/common)</summary>

[`v0.65.0`](https://redirect.github.com/prometheus/common/releases/tag/v0.65.0)

[Compare
Source](https://redirect.github.com/prometheus/common/compare/v0.64.0...v0.65.0)

- Synchronize common files from prometheus/prometheus by
[@&#8203;prombot](https://redirect.github.com/prombot) in
[https://github.com/prometheus/common/pull/789](https://redirect.github.com/prometheus/common/pull/789)
- Remove otlptranslator package by
[@&#8203;ArthurSens](https://redirect.github.com/ArthurSens) in
[https://github.com/prometheus/common/pull/791](https://redirect.github.com/prometheus/common/pull/791)
- feat(promslog): add Level() method to get slog.Level by
[@&#8203;tjhop](https://redirect.github.com/tjhop) in
[https://github.com/prometheus/common/pull/795](https://redirect.github.com/prometheus/common/pull/795)
- feat: Support negative duration in new function
ParseDurationAllowNegative by
[@&#8203;iamhalje](https://redirect.github.com/iamhalje) in
[https://github.com/prometheus/common/pull/793](https://redirect.github.com/prometheus/common/pull/793)

- [@&#8203;iamhalje](https://redirect.github.com/iamhalje) made their
first contribution in
[https://github.com/prometheus/common/pull/793](https://redirect.github.com/prometheus/common/pull/793)

**Full Changelog**:
prometheus/common@v0.64.0...v0.65.0

</details>

---

📅 **Schedule**: Branch creation - "on the first day of the month" (UTC),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/jaegertracing/jaeger).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC42Mi4xIiwidXBkYXRlZEluVmVyIjoiNDAuNjIuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiY2hhbmdlbG9nOmRlcGVuZGVuY2llcyJdfQ==-->

Signed-off-by: Mend Renovate <bot@renovateapp.com>
chahatsagarmain and others added 3 commits June 26, 2025 13:52
Signed-off-by: chahatsagarmain <chahatsagar2003@gmail.com>
Signed-off-by: chahatsagarmain <chahatsagar2003@gmail.com>
Create a ConfigMap to mount the Prometheus configuration:

```bash
kubectl create configmap prometheus-config --from-file=prometheus.yml=./prometheus.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so my question would be - are you expecting maintainers to do all these steps manually when deploying to OCI? Ideally I don't even want to think about the deployment, they should happen automatically when a new Jaeger version is released. How do we plan to achieve that? Let's work backwards from this ideal state.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to mention this in the PR description: my initial goal was to get the setup working locally first. We can then iteratively automate the entire process in subsequent PRs.

@yurishkuro yurishkuro added the changelog:exprimental Change to an experimental part of the code label Jun 30, 2025
@yurishkuro yurishkuro changed the title [WIP] Jaeger Demo on Oracle Cloud . Jaeger Demo on Kubernetes Jun 30, 2025
@yurishkuro yurishkuro marked this pull request as ready for review June 30, 2025 13:47
@yurishkuro yurishkuro merged commit f887e13 into jaegertracing:main Jun 30, 2025
61 of 62 checks passed
cd helm-charts
git checkout v2
```
After cloning, you must install chart dependencies to avoid the depedency missing error using this command :
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a small typo in this line: "depedency" should be spelled "dependency".

Suggested change
After cloning, you must install chart dependencies to avoid the depedency missing error using this command :
After cloning, you must install chart dependencies to avoid the dependency missing error using this command :

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage changelog:exprimental Change to an experimental part of the code storage/elasticsearch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants