Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,847
    • Issues 43,847
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,397
    • Merge requests 1,397
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #342730
Closed
Open
Created Oct 08, 2021 by Alana Bellucci@abellucci👶🏼Developer

Return alert id (iid) in POST responses for generic HTTP Endpoints

Release notes

When you POST an alert using a generic HTTP Endpoint the response is a simple 200 upon a successful POST. Internal teams hoping to dogfood alerts want to reconcile their current processes and would like to see additional information returned in the response, i.e. alert_id.

Problem to solve

When you POST an alert using a generic HTTP Endpoint the response is a simple 200 upon a successful POST. Internal teams hoping to dogfood alerts want to reconcile their current processes and would like to see additional information returned in the response, i.e. alert_id.

MVC Solution

Include alert_id in the response for generic HTTP Endpoint POST.

Long term solution

Not included in this MVC, but things that need to be considered:

  • Create a REST API for alerts. This will allow for more access privileges (e.g. read/write complete API) than HTTP integration tokens do.
  • Reconcile what is already available in the GraphQL API
Edited Nov 19, 2021 by Alana Bellucci
Assignee
Assign to
Time tracking