Opened 2 years ago

Last modified 2 years ago

#22834 needs_information enhancement

Decide what to do with UnparseableDescriptors while synchronizing from another instance

Reported by: iwakeh Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Normal Keywords: metrics-2018
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by iwakeh

Status: newneeds_information

comment:2 Changed 2 years ago by karsten

That matches my understanding, too. Do you think we should do something differently?

comment:3 Changed 2 years ago by iwakeh

The unpars.desc. could be counted or collected in a different place. Just want to make sure we thought about not changing anything with the 'new' descriptor type (unpars.desc).

Last edited 2 years ago by iwakeh (previous) (diff)

comment:4 Changed 2 years ago by karsten

Summary: CollecTor sync: what should happen to UnparseableDescriptors?Decide what to do with UnparseableDescriptors while synchronizing from another instance

Turn summary into a full sentence.

comment:5 Changed 2 years ago by karsten

Keywords: metrics-2018 added

comment:6 Changed 2 years ago by karsten

Keywords: metrics-2017 added; metrics-2018 removed

comment:7 Changed 2 years ago by iwakeh

Keywords: metrics-2018 added; metrics-2017 removed

Will be completed in 2018.

Note: See TracTickets for help on using tickets.