Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-4069

[Link Checker] Redesign of the Slack "Broken Links" message

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Draft Sprint

      Figure out (a) the criteria used to calculate the final number of broken links and (b) figure out what we want to sent to the slack notification message.

      In general, I think we need to figure out what 'error codes' we want to count/total to send to slack, or perhaps send multiple error code counts to slack.  See Jira OCMUI-4068 for more information on how the GH workflow action and slack are implemented.

      Currently, the Slack notification looks like:

      • where "404_length" is the # of url/links which return 404 error code.

      The run/check_links.mjs script outputs:

      Category                           Count
      ---------------------------------- ------
      Total URLs skipped                     0
      Success                              265
      Redirects                            143
      Redirects errors                       1
      Client errors (4xx)                    4
      Server errors (5xx)                    0
      Request errors                         1
      ---------------------------------- ------
      Total URLs checked                   413
      

       

      Where the error codes are:  

      Client Errors (4xx):
          400 - Bad Request (Client error in request)
          401 - Unauthorized (Authentication required)
          403 - Forbidden (Server refuses authorization)
          404 - Not Found (Resource not found)
          405 - Method Not Allowed (Request method not supported)
          408 - Request Timeout (Server timeout)
          429 - Too Many Requests (Rate limit exceeded)
       
        Server Errors (5xx):
          500 - Internal Server Error (Server error)
          501 - Not Implemented (Function not supported)
          502 - Bad Gateway (Invalid response from upstream)
          503 - Service Unavailable (Server temporarily unavailable)
          504 - Gateway Timeout (Upstream server timeout) 
      

              Unassigned Unassigned
              dtaylor@redhat.com David Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: