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

Rewire the ErrorTemetry service to send logs to FluentD

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Minor Minor
    • evergreen
    • Evergreen - Milestone 2

      Currently, the code stores the error logs in the DB like the other endpoints. This is a temporary (and unwise) choice for error logging because of the big amount of data it is likely to generate, and the fact we will want to only keep a few weeks of it.

      So we should send those logs elsewhere. After a sync with olblak, we need to prototype sending it instead to a FluentD socket to integrate with the existing error logging setup in the K8S cluster used in jenkins.io

          [JENKINS-51175] Rewire the ErrorTemetry service to send logs to FluentD

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Assignee Original: R. Tyler Croy [ rtyler ] New: Baptiste Mathus [ batmat ]

          R. Tyler Croy added a comment -

          We're not sending logs to fluentd but rather Sentry for the time being.

          Will create followup tickets if we need to change this

          R. Tyler Croy added a comment - We're not sending logs to fluentd but rather Sentry for the time being. Will create followup tickets if we need to change this
          R. Tyler Croy made changes -
          Resolution New: Won't Do [ 10001 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Baptiste Mathus made changes -
          Labels Original: essentials New: essentials evergreen
          Baptiste Mathus made changes -
          Labels Original: essentials evergreen New: evergreen

            batmat Baptiste Mathus
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: