Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • argonaut argonaut
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • argonautargonaut
  • Issues
  • #5706
Closed
Open
Issue created Nov 30, 2017 by Côme Chilliet@cchillietReporter

A ping fallback would be handy

Add a ping fallback

ping action is handled by OPSI module for OPSI clients and Argonaut module for argonaut clients. But when there is neither Argonaut nor OPSI client there should be a module using the usual ping to test if the system is answering or not.

Actual behavior

ping is only supported for OPSI and Argonaut

Expected behavior

There should be a fallback on standard ping on IP address.

Edited Jul 29, 2021 by bmortier
Assignee
Assign to
Time tracking