Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • N Notification
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Notification
  • Merge requests
  • !124

Custom error for bad push url

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Alok Joshi requested to merge handle_client_5xx into master Oct 04, 2021
  • Overview 0
  • Commits 6
  • Pipelines 15
  • Changes 4

As of today, Notification service does not log which client (subscription) is corrupted/unable to process requests that are sent to the pushUrl as part of the notifySubscriber method. To narrow down on bad clients, we can log more details about the subscription. Also, we can return a custom Http status (424 FAILED_DEPENDENCY) to separate out all such errors in monitoring.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: handle_client_5xx