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

Add a new persona: My Persona #3368

Closed
soosanna opened this issue Oct 12, 2023 · 9 comments
Closed

Add a new persona: My Persona #3368

soosanna opened this issue Oct 12, 2023 · 9 comments

Comments

@soosanna
Copy link

Provide a description of your role and responsibilities and what your observability goals are

i am working data science platform, product based company , that product used python,java,react based . i don't know how and where to implement open telemetry concept , could you guide me.

@svrnm
Copy link
Member

svrnm commented Oct 12, 2023

Hey @soosanna,

thank you for raising this issue. The purpose of the issue type to add a new persona is here to extend the list from Devs, Ops at https://opentelemetry.io/docs/getting-started/ to whatever you think is missing. From your description it is not entirely clear to me what you're looking for, can you elaborate a little bit more what you try to accomplish?

Thanks

@soosanna
Copy link
Author

Thank you for replay . i will study clearly and ask.

@soosanna
Copy link
Author

OpenTelemetry.pdf

the above pdf is my intern job , how to do for poc

@svrnm
Copy link
Member

svrnm commented Oct 25, 2023

OpenTelemetry.pdf

the above pdf is my intern job , how to do for poc

Can you please provide the content of that PDF as plain text in a comment to this issue?

@soosanna
Copy link
Author

Objective
The objective of this exercise is to build a prototype to collect system metrics, traces and application logs, machine learning models training live statuses from batch jobs (machines) and aggregate to manage those collected data for analytics usage
Setting up a solid observability framework using OpenTelemetry SDKs to create & manage telemetry data and aggregate into a Opensource observability dashboard platform

Scope
• Use OpenTelemetry instrument for Python (If possible, for Java as well) to collect metrics and logs.
◦ Reference: https://opentelemetry.io/docs/instrumentation/
• Setup a collector to collect logs, metrics, and transport real-time data from python (and Java)
◦ Reference: https://opentelemetry.io/docs/collector/.
• Implement OTLP grpc protocol to collect data.
◦ Reference: https://opentelemetry.io/docs/collector/configuration/
• Setup Jaeger Dashboard to show real-time data flow and historic d

@svrnm
Copy link
Member

svrnm commented Oct 27, 2023

Hey @soosanna, parts of your objective are developer&ops tasks you will find through out the documentation, i.e. instrumenting, setting up the collector, etc. The part I am not sure about is "learning models training live statuses", this is something OpenTelemetry is not doing for you, this is something a receiving platform of your data is reponsible for.

@soosanna
Copy link
Author

OpenTelemetry

Objective
The objective of this exercise is to build a prototype to collect system metrics, traces and application logs, machine learning models training live statuses from batch jobs (machines) and aggregate to manage those collected data for analytics usage - https://opentelemetry.io/.
Setting up a solid observability framework using OpenTelemetry SDKs to create & manage telemetry data and aggregate into a Opensource observability dashboard platform - https://www.jaegertracing.io/.

Scope
• Use OpenTelemetry instrument for Python (If possible, for Java as well) to collect metrics and logs.
◦ Reference: https://opentelemetry.io/docs/instrumentation/
• Setup a collector to collect logs, metrics, and transport real-time data from python (and Java)
◦ Reference: https://opentelemetry.io/docs/collector/.
• Implement OTLP grpc protocol to collect data.
◦ Reference: https://opentelemetry.io/docs/collector/configuration/
• Setup Jaeger Dashboard to show real-time data flow and historic data.

@cartermp
Copy link
Contributor

I'll close this as a wontfix -- there's no distinct persona here, just a well thought-out set of requirements to build a system using OTel.

@cartermp cartermp closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@soosanna
Copy link
Author

Thanks for your response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants