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

slurm processor #32312

Closed
luccabb opened this issue Apr 11, 2024 · 5 comments
Closed

slurm processor #32312

luccabb opened this issue Apr 11, 2024 · 5 comments
Labels

Comments

@luccabb
Copy link

luccabb commented Apr 11, 2024

Component(s)

No response

Is your feature request related to a problem? Please describe.

n/a

Describe the solution you'd like

open telemetry processor that enriches log, metrics, and traces with slurm metadata. Some of the metadata that would be helpful to include: jobid, jobname, nodelist, user

Describe alternatives you've considered

No response

Additional context

No response

@luccabb luccabb added enhancement New feature or request needs triage New item requiring triage labels Apr 11, 2024
@JaredTan95
Copy link
Member

JaredTan95 commented Apr 11, 2024

jobid, jobname, nodelist, user

Sorry, I don't know about slurm, but I have a question,Does those metadata injected by slurm

The otel col collect logs with the pod's annnotation and labels, So I don't quite understand your description

@JaredTan95 JaredTan95 removed the needs triage New item requiring triage label Apr 11, 2024
@luccabb
Copy link
Author

luccabb commented Apr 11, 2024

Does those metadata injected by slurm?

would need to shell out and query slurm info (assuming the environment has their binaries available, like sinfo).

my understanding is that it's possible to write a processor that shells out, grabs some metadata from slurm, and enriches metrics, traces, and logs

@crobert-1 crobert-1 added Sponsor Needed New component seeking sponsor and removed enhancement New feature or request labels Apr 11, 2024
@atoulme
Copy link
Contributor

atoulme commented Apr 13, 2024

Could this be part of the resourcedetectionprocessor? Seems like a natural fit for it.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants