Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 277
    • Issues 277
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • 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
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #194
Closed
Open
Issue created Mar 09, 2020 by Michal Nowikowski@godfrydContributor

'stats were not collected yet' situation should be better exposed in UI

From @tomek:

As for the two subnets, I think stats hook was not loaded on those two machines. It's a demo configuration error, not stork bug. But I agree that the situation can be handled a little bit better. @godfryd, @vicky, how about displaying a yellow warning that stats could not be retrieved and explain what the admin can do about it? Does it require any extra hook? Or is this a problem with the same subnet being handled by two servers?

ref: #47 (closed) and #47 (comment 115095)

Edited Apr 15, 2020 by Tomek Mrugalski
Assignee
Assign to
Time tracking