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

Ability to send limited traces without detailed stage/step spans #1017

Open
sparrowt opened this issue Jan 10, 2025 · 0 comments
Open

Ability to send limited traces without detailed stage/step spans #1017

sparrowt opened this issue Jan 10, 2025 · 0 comments

Comments

@sparrowt
Copy link

sparrowt commented Jan 10, 2025

What feature do you want to see added?

Firstly let me say again how awesome this plugin is - thank you. I realise I've opened several issues on this repo today, but I fully appreciate this is an open source project. These are just the things that jumped out at me having tried this out for the first time - in case they may be useful to others too.

Summary

It seems that traces are kind of "all or nothing" e.g. otel.traces.exporter=otlp (the default) or otel.traces.exporter=none (zero per-run info).

Some kind of middle option would be useful: to send only one trace per Jenkins job build/run with key info such as:

  • job name, URL etc.
  • result
  • duration

Benefits

  • core result & timing information can be kept efficiently for as long as desired, even when the run has been deleted (e.g. by Jenkins build discarder)
  • would reduce overhead (resource consumption & cost) of sending & storing the detailed spans for each stage / paralel branch / step, if not required

Perhaps there is a lighter-weight plugin which does this already, but in my (failed) search to find one I ended up here!

Implementation

I'm quite new to this plugin, but I can see on the receiving end that in Elasticsearch, the key info I'm interested in is already present in a single per-build record with processor.event=transaction & transaction.type=job. If the Jenkins plugin could be configured to only send this & omit all other spans that would be amazing.

Upstream changes

No response

Are you interested in contributing this feature?

With some pointers in the right direction I might be...!

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