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

.github/workflows/action-test-smoke: Add a step to verify the jeager #794

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Mossaka
Copy link
Member

@Mossaka Mossaka commented Jan 9, 2025

Add a GitHub Action step to verify that Jeager actually receives the expected emitted traces, rather than just hoping they made it.

It uses Jeager API to fetch the traces, and note that the limit=0 so that we can get all the operations.

This is to prevent #787 from happening without getting notices.

@Mossaka Mossaka requested review from Copilot and jprendes January 9, 2025 03:04
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

.github/workflows/action-test-smoke.yml Outdated Show resolved Hide resolved
@Mossaka Mossaka requested a review from Copilot January 9, 2025 03:14
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 3 changed files in this pull request and generated 1 comment.

Files not reviewed (2)
  • scripts/setup-jeager-and-otel.sh: Language not supported
  • scripts/verify-jaeger-traces.sh: Language not supported
Comments suppressed due to low confidence (1)

.github/workflows/action-test-smoke.yml:63

  • The spelling of 'Jeager' should be corrected to 'Jaeger' in the error message.
echo "Operation '$op' not found in Jaeger!"

.github/workflows/action-test-smoke.yml Outdated Show resolved Hide resolved
Add a GitHub Action step to verify that Jeager actually receives the expected emitted traces, rather than just hoping they made it.

It uses Jeager API to fetch the traces, and note that the limit=0 so that we can get all the operations.

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>

scripts/verify-jaeger-traces: Add a script to verify jeager traces

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>

rename scripts/setup-otel.sh -> scripts/setup-jeager-and-otel.sh

Signed-off-by: Jiaxiao (mossaka) Zhou <[email protected]>
@Mossaka Mossaka force-pushed the jeager-integration-test branch from 3914cd1 to f0c0a6d Compare January 9, 2025 03:17
@Mossaka Mossaka linked an issue Jan 9, 2025 that may be closed by this pull request
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.

Add Jeager traces integration tests
1 participant