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

[Feat]: Guide for monitoring firecrawl usage with OpenTelemetry #1049

Open
patcher9 opened this issue Jan 9, 2025 · 0 comments
Open

[Feat]: Guide for monitoring firecrawl usage with OpenTelemetry #1049

patcher9 opened this issue Jan 9, 2025 · 0 comments

Comments

@patcher9
Copy link

patcher9 commented Jan 9, 2025

Problem Description

Currently there is no proper way to trace and get insights into the firecrawl usage (Observability)

Proposed Feature

A guide (in Documentation and a tutorial blogpost) that guides on how to add monitoring for firecrawl based Applications

Alternatives Considered

Manually instrument applications for monitoring which is not the easiest for all developers

Implementation Suggestions

Either a native integration for OpenTelemetry tracing or a guide explaining how the users can achieve this

Use Case

Observability makes the application better production ready

Additional Context

Hi Team, I am one of the maintainers of OpenLIT and we support Observability for LLM apps, It is all OpenTelemetry-native so the traces and metrics can be sent to any platform like Grafana or any OSS OTel tools

OpenLIT helps when the users are using LLM + VectorDBs + Other framework actions as the consolidated monitoring gives them a complete picture plus developers dont need to build this on their own.

Figured the mention here might be useful for developers using FireCrawl hence reaching out. Can someone help me understand how I can begin with contributing a blog guide and a documentation page that can serve as a follow up for in depth.

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

No branches or pull requests

1 participant