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

Design (JEP) what the Error Telemetry API will be

    Details

    • Sprint:
      Evergreen - Milestone 1
    • Similar Issues:

      Description

      The prototyping work has been done in JENKINS-49811, so now we need to draft a JEP and submit it for review to the larger community for validation.

        Attachments

          Issue Links

            Activity

            Hide
            batmat Baptiste Mathus added a comment -

            Draft JEP submitted for feedback to Jenkins dev ML: https://groups.google.com/d/msg/jenkinsci-dev/ql9iX06IdGw/AJxFcGK5BgAJ

            Show
            batmat Baptiste Mathus added a comment - Draft JEP submitted for feedback to Jenkins dev ML:  https://groups.google.com/d/msg/jenkinsci-dev/ql9iX06IdGw/AJxFcGK5BgAJ
            Hide
            batmat Baptiste Mathus added a comment -

            JEP submitted as PR and waiting for number assignment.

            Show
            batmat Baptiste Mathus added a comment - JEP submitted as PR and waiting for number assignment.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Baptiste Mathus
            Path:
            jep/308/README.adoc
            jep/README.adoc
            http://jenkins-ci.org/commit/jep/20e40107d45e891812159b646354480d4e4e0d7c
            Log:
            JENKINS-51140 Essentials Error Telemetry API (#107)

            • JENKINS-51140 Design (JEP) what the Error Telemetry API will be
            • Give more precisions about query/answer payloads

            Also fix the link: I meant JEP 303 for Registrations and authentication,
            not 307.

            • Add rationale why (for now) we don't handle batch sending logs
            • Switch to use a JSON node instead of stringified JSON from the client side
            • Bump to ~ 1 MB max and clarify associated sentence
            • /errorTelemetry => /telemetry/error to be more REST-ish
            • Use `POST` exclusively
            • Add reliability concern from client to server
            • Referencing feedback thread on the dev ML
            • Recommend storing the UUID alongside with log entries
            • Assign JEP-308
            • DRAFT and formatting

            *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

            Functionality will be removed from GitHub.com on January 31st, 2019.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Baptiste Mathus Path: jep/308/README.adoc jep/README.adoc http://jenkins-ci.org/commit/jep/20e40107d45e891812159b646354480d4e4e0d7c Log: JENKINS-51140 Essentials Error Telemetry API (#107) JENKINS-51140 Design (JEP) what the Error Telemetry API will be Give more precisions about query/answer payloads Also fix the link: I meant JEP 303 for Registrations and authentication, not 307. Add rationale why (for now) we don't handle batch sending logs Switch to use a JSON node instead of stringified JSON from the client side Bump to ~ 1 MB max and clarify associated sentence /errorTelemetry => /telemetry/error to be more REST-ish Use `POST` exclusively Add reliability concern from client to server Referencing feedback thread on the dev ML Recommend storing the UUID alongside with log entries Assign JEP-308 DRAFT and formatting * NOTE: * This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019.
            Hide
            batmat Baptiste Mathus added a comment -

            Merged as JEP 308 by Liam yesterday.

            Show
            batmat Baptiste Mathus added a comment - Merged as JEP 308 by Liam yesterday.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: