[Docs]: Add Documentation for Monitoring with OpenTelemetry #335
+90
−1
Conversation
This file contains 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
|
Hey @unclecode Lemme know if I can help get this PR merge ready. Thanks and Happy New year! |
|
Hi @patcher9 sure this weekend I will check it and thx for contributing |
aravindkarnam
added
🔌 Integration
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.
Hi Team, I am one of the maintainers of OpenLIT and we support Observability for web crawler agents built with Crawl4AI, It is all OpenTelemetry-native so the traces and metrics can be sent to any platform like Grafana or any OSS OTel tools
I think the biggest benefit for developers is when they are using LLMs along with a web crawler as then OpenLIT helps to give the complete picture of what actions were taken.
Figured the mention here might be useful for developers using Crawl4AI hence adding the reference in documentation page.
(Btw great project I am planning to use this to update our LLM pricing Json like in one of your examples)