Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P PulsoServer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Cristian Ojeda Flores
  • PulsoServer
  • Issues
  • #4

Closed
Open
Created Apr 17, 2021 by Cristian Ojeda Flores@maxMaintainer

Edit check name or notification targets

Only those two attributes; we aren’t including the hostname or frequency because that would require us to update the values on every remote server, and on the case of the hostname, it would mean that the previous check results were actually for something else that may have no relation to the new host under check.

There’s another issue regarding “edition” of hostname or frequency.

Assignee
Assign to
Time tracking