You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...!
The text was updated successfully, but these errors were encountered:
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) orotel.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:
Benefits
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...!
The text was updated successfully, but these errors were encountered: