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

fix: Fix observability stack #153

Merged
merged 1 commit into from
Feb 20, 2025
Merged

fix: Fix observability stack #153

merged 1 commit into from
Feb 20, 2025

Conversation

sbernauer
Copy link
Member

@sbernauer sbernauer commented Feb 17, 2025

  • Downgrade Grafana Loki to a version that works with the existing settings.
  • Downgrade Grafana Tempo to a version that works with the existing settings.
  • Configure Jaeger to use in-memory storage.
    It defaults to cassandra which wasn't deployed by the chart, so Jaeger was crashing. This should probably be moved to disk (using badger) to prevent Jaeger from crashing when receiving too many traces.

Note

This somewhat reverts changes made in #119, which appears to have been done without testing (since we test the demos and this stack doesn't yet have one).

Grafana Loki had the following problem:

You have more than zero replicas configured for both the single binary and simple scalable targets. If this was intentional change the deploymentMode to the transitional 'SingleBinary<->SimpleScalable' mode)

@NickLarsenNZ NickLarsenNZ self-requested a review February 17, 2025 13:54
Copy link
Member

@NickLarsenNZ NickLarsenNZ left a comment

Choose a reason for hiding this comment

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

LGTM

@NickLarsenNZ NickLarsenNZ added this pull request to the merge queue Feb 20, 2025
Merged via the queue into main with commit a0cea53 Feb 20, 2025
2 checks passed
@NickLarsenNZ NickLarsenNZ deleted the fix/observability-stack branch February 20, 2025 15:48
NickLarsenNZ pushed a commit that referenced this pull request Feb 27, 2025
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.

2 participants