If we’re going to be tracking step invocations anyway, it’d be interesting to count the number of Declarative Pipelines with a script block, maybe?
A. On Fri, Mar 16, 2018 at 4:28 PM R. Tyler Croy <ty...@monkeypox.org> wrote: > The successful adoption and iterative improvement of Jenkins Essentials > [0] is > heavily contingent on a spectrum of automated feedback which I've been > referring to as "telemetry" in many of the design documents. I wanted to > start > discussing the prospect of collecting anonymized Pipeline usage telemetry > to > help Jenkins Essentials, Blue Ocean, and Pipeline teams understand how > users > are actually using Jenkins Pipeline. > > James Dumay has already prototyped some similar work[1] for collecting > behavioral telemetry in Blue Ocean, but what I'm proposing would be much > more > broad in scope[2]. The metrics I am interested in, to help us understand > how > Pipeline is being used, are: > > * Counts: > * configured Declarative Pipelines > * configured Script Pipelines > * Pipeline executions > * distinct built-in step invocations (i.e. not counting Global Variable > invocations) > * Global Shared Pipelines configured > * Folder-level Shared Pipelines configured > * Agents used per-Pipeline > * Post-directive breakdown (stable,unstable,changed,etc) > > * Timers > * Runtime duration per step invocation > * Runtime duration per Pipeline > > > I believe this is a sufficiently useful set of metrics to send along, but > the > two questions I could use help answering are: > > * What are other metrics which would positively impact the development of > Jenkins? > * Are there concerns about implementation feasibility for any of these? > > > I am planning on using statsd (sent to the project's Datadog account), so > sampling and controlling the volume of individual metrics is not something > I'm > terribly worried about. > > > > Happy to hear any feedback y'all are willing to share! > > > [0] https://github.com/jenkins-infra/evergreen#evergreen > [1] https://github.com/jenkinsci/blueocean-plugin/pull/1653 > [2] https://issues.jenkins-ci.org/browse/JENKINS-49852 > > > > Cheers > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > xmpp: rty...@jabber.org > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > ------------------------------------------------------ > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/20180316202818.hgl5irxnuqduq24v%40blackberry.coupleofllamas.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOYCryfDV8Edo1D6XTa7qhu9ik-wNEqLc4OYQVFh4hKvXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
