-
Notifications
You must be signed in to change notification settings - Fork 163
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
[PROPOSAL][CCI] Add sample for logs and metrics collection and processing #331
Comments
Do you have any ideas for a good python framework for this? It probably makes sense to limit the options to open source, so that the library can remain open source. |
@Refffy I did a presentation for collecting logs from Python into OpenSearch. I wonder if it would make sense to integrate something like that here. https://gist.github.com/dtaivpp/a9b00957aa7d9cfe33e92aff8d50c835 Above is a gist and below is the video of this. Is something like this what you were thinking of? |
Hello, @dtaivpp! Yes, I think that your code snippet on gist is makes sense to this issue. But I also think, that it'll great not only to collect logs, but also to show common project issues in realtime like sentry, loki or graphana or even use elastic search for collecting and representing logs metrics (for example, crashes or something like that), but I suppose that it'll be hard to implement. |
I see so more of like an APM type workflow so that you get more context. Might be worth exploring adding traces to this. Here is another good place to read: https://opentelemetry-python.readthedocs.io/en/latest/api/trace.html |
Hi @saimedhi! This sounds like a fun proposal to work on! Can I request assignment on this issue? |
Do I understand this issue correctly that we're talking about adding a sample for logs and metrics collection and processing? |
Closed via #331. |
What are you proposing?
Add a service or may be a script for collecting and analyzing logs, crashes, etc. like sentry, loki or graphana
What problems are you trying to solve?
It'll help to calculate and store statistics of errors appearance ratio. Also, it'll be very helpfull for opensearch newbies (like me) to create new issues
The text was updated successfully, but these errors were encountered: