Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36473

New Metric: Load assessment for required nodes

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Include in the metrics parameters list: load assessment for required nodes.
      Similar behaviour of "jenkins.job.scheduled" but for nodes and not for the master. Node label would be introduced as parameter as it does on `jenkins.node._XXX.builds` _(timer)

        Attachments

          Activity

          Hide
          stephenconnolly Stephen Connolly added a comment -

          The issue is how do you know that any specific job is waiting for that node specifically?

          The job could be configured with a label expression such as A && (!B || (C <=> D) || (E => F)) while the node could be configured with label A ... how are we to know that the job is scheduled for execution on that node and not some other node? For sure we can evaluate the conditions of the label expression... but then...

          Resource usage may prevent the job executing on the specific node (due to a parallel job execution on the node) and hence the job may actually end up targetting a different node.

          We could track scheduled against a label expression, but there will be bucket loads of them

          We could track scheduled against a labelatom... but in that case what are the label atoms of A && (!B || (C <=> D) || (E => F))?

          Show
          stephenconnolly Stephen Connolly added a comment - The issue is how do you know that any specific job is waiting for that node specifically? The job could be configured with a label expression such as A && (!B || (C <=> D) || (E => F)) while the node could be configured with label A ... how are we to know that the job is scheduled for execution on that node and not some other node? For sure we can evaluate the conditions of the label expression... but then... Resource usage may prevent the job executing on the specific node (due to a parallel job execution on the node) and hence the job may actually end up targetting a different node. We could track scheduled against a label expression, but there will be bucket loads of them We could track scheduled against a labelatom... but in that case what are the label atoms of A && (!B || (C <=> D) || (E => F)) ?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            carlosrodlop Carlos Rodríguez López
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: