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

[PROPOSAL][CCI] Add sample for logs and metrics collection and processing #331

Closed
Refffy opened this issue Mar 18, 2023 · 10 comments
Closed
Assignees
Labels
CCI enhancement New feature or request

Comments

@Refffy
Copy link

Refffy commented Mar 18, 2023

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

@github-actions github-actions bot added the untriaged Need triage label Mar 18, 2023
@Refffy Refffy changed the title [PROPOSAL] Logs collection, processing and metrics collection [PROPOSAL][CCI] Logs collection, processing and metrics collection Mar 19, 2023
@wbeckler wbeckler removed the untriaged Need triage label Mar 22, 2023
@wbeckler
Copy link
Contributor

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.

@dtaivpp
Copy link

dtaivpp commented Mar 22, 2023

@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.

https://youtu.be/-8CNa4T2Jaw

Is something like this what you were thinking of?

@Refffy
Copy link
Author

Refffy commented Mar 22, 2023

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.

@dtaivpp
Copy link

dtaivpp commented Mar 22, 2023

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

@saimedhi saimedhi added the CCI label Sep 7, 2023
@saimedhi
Copy link
Collaborator

saimedhi commented Sep 7, 2023

@Refffy, @dtaivpp Please feel free to take up this issue and raise a PR with your proposed solution. Thanks :)

@Djcarrillo6
Copy link
Contributor

Hi @saimedhi! This sounds like a fun proposal to work on! Can I request assignment on this issue?

@dblock dblock changed the title [PROPOSAL][CCI] Logs collection, processing and metrics collection [PROPOSAL][CCI] Add sample for logs and metrics collection and processing Nov 10, 2023
@dblock
Copy link
Member

dblock commented Nov 10, 2023

Do I understand this issue correctly that we're talking about adding a sample for logs and metrics collection and processing?

@dblock dblock added the enhancement New feature or request label Nov 10, 2023
@Djcarrillo6
Copy link
Contributor

@dblock that was my interpretation as well. Something similar to was @dtaivpp mentioned.

@Djcarrillo6
Copy link
Contributor

Djcarrillo6 commented Nov 12, 2023

@dblock @saimedhi What do you think is best way to address this issue? I was thinking of integrating the log collection script that David mentioned.. Does that make sense to you?

@dblock
Copy link
Member

dblock commented Nov 22, 2023

Closed via #331.

@dblock dblock closed this as completed Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCI enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants