Repository navigation
Add LogBrew to Monitoring - #254
Open
furkanerday wants to merge 1 commit into
Open
furkanerday wants to merge 1 commit into
furkanerday wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds LogBrew to
data/Monitoring.md, in alphabetical order before Muscula. I did not editREADME.md, per the contributing guide.LogBrew is a hosted service for error tracking, logs, traces and metrics. It accepts OpenTelemetry data and has an MCP server so coding agents can read issues and logs. The free plan has no time limit and needs no card. It includes 100,000 errors, 50 GB of logs and 50 GB of metrics a month, with 30-day retention. Pricing is at https://logbrew.co/en/pricing.
Full disclosure, I'm the one building LogBrew.