Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Enable SPM in Jaeger v2 #5680

Closed
wants to merge 0 commits into from

Conversation

FlamingSaint
Copy link
Member

Which problem is this PR solving?

Description of the changes

  • Added a new docker-compose file
  • Added the configuration file which will be used for enabling SPM in v2

How was this change tested?

  • docker compose -f docker-compose-v2.yml up

TODO

  • Need to use a local image in the compose file instead of pulling from docker hub
  • Fix the error with microsim

Checklist

@FlamingSaint FlamingSaint changed the title Enable SPM in Jaeger v2 [WIP] Enable SPM in Jaeger v2 Jun 26, 2024
networks:
- backend
# TODO: Need to use the local image here while making changes
image: jaegertracing/jaeger
Copy link
Member

Choose a reason for hiding this comment

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

follow the same pattern as in the other compose file - env var defaulted to latest but make dev uses local build

Copy link

codecov bot commented Jun 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.36%. Comparing base (afdd311) to head (ecd4a2a).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5680   +/-   ##
=======================================
  Coverage   96.36%   96.36%           
=======================================
  Files         329      329           
  Lines       16060    16060           
=======================================
  Hits        15477    15477           
  Misses        405      405           
  Partials      178      178           
Flag Coverage Δ
badger_v1 8.04% <ø> (ø)
badger_v2 1.92% <ø> (ø)
cassandra-3.x-v1 16.60% <ø> (ø)
cassandra-3.x-v2 1.84% <ø> (ø)
cassandra-4.x-v1 16.60% <ø> (ø)
cassandra-4.x-v2 1.84% <ø> (ø)
elasticsearch-7.x-v1 18.88% <ø> (ø)
elasticsearch-8.x-v1 19.08% <ø> (ø)
elasticsearch-8.x-v2 19.07% <ø> (-0.02%) ⬇️
grpc_v1 9.47% <ø> (+0.01%) ⬆️
grpc_v2 7.49% <ø> (ø)
kafka 9.76% <ø> (ø)
opensearch-1.x-v1 18.93% <ø> (+0.01%) ⬆️
opensearch-2.x-v1 18.92% <ø> (-0.02%) ⬇️
opensearch-2.x-v2 18.92% <ø> (ø)
unittests 94.22% <ø> (ø)

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.

# TODO: Need to use the local image here while making changes
image: jaegertracing/jaeger
volumes:
- "./jaeger-ui.json:/etc/jaeger/jaeger-ui.json" # Do we need this for v2 ? Seems to be running without this.
Copy link
Member

Choose a reason for hiding this comment

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

it has this:

  "monitor": {
    "menuEnabled": true
  },

I don't remember if it's the default. We already have a Capabilities exchange protocol between backend and UI, ideally it would just use that and not require explicit config.

- backend
image: yurishkuro/microsim:0.3.0
# TODO: Fix error - dial tcp [::1]:14278: connect: connection refused
command: "-j http://localhost:14278/api/traces -d 24h -s 500ms"
Copy link
Member

Choose a reason for hiding this comment

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

Does microsim support exporting via OTLP? If not, might be a good thing to implement.

@FlamingSaint FlamingSaint marked this pull request as ready for review June 26, 2024 23:00
@FlamingSaint FlamingSaint requested a review from a team as a code owner June 26, 2024 23:00
@FlamingSaint FlamingSaint requested a review from pavolloffay June 26, 2024 23:00
@FlamingSaint FlamingSaint marked this pull request as draft June 26, 2024 23:00
@FlamingSaint
Copy link
Member Author

Looks like I had some merge conflicts. I will open a new PR with the updated changes. Sorry for the trouble.

@FlamingSaint FlamingSaint deleted the spm branch June 26, 2024 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[jaeger v2] Service Performance Monitoring
2 participants