Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Collector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Collector
  • Issues
  • #22834
Closed
Open
Created Jul 06, 2017 by iwakeh@iwakeh

Decide what to do with UnparseableDescriptors while synchronizing from another instance

Let's find out, if a code change is needed or things are fine as they are.

Current situation when one CollecTor fetches data from another CollecTor: Metrics Lib cannot parse the fetched content, provides an object of UnparseableDescriptor, and CollecTor simply ignores this object as unknown (only logs on trace level).

During normal collecting an unparseable descriptor is stored anyway.

Assignee
Assign to
Time tracking