Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collection fails on billing emitter error #2853

Closed
jml opened this issue Sep 18, 2017 · 0 comments
Closed

Collection fails on billing emitter error #2853

jml opened this issue Sep 18, 2017 · 0 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it

Comments

@jml
Copy link
Contributor

jml commented Sep 18, 2017

Elsewhere, @bboreham states:

I think the scope collector should continue to function even when billing is down.

A quick search through the scope code shows

if err != nil {
log.Errorf("Failed emitting billing data: %v", err)
return err
}
return e.Collector.Add(ctx, rep, buf)

There, BillingEmitter (a decorator around the Collector interface) will only call the "upstream" collector if it successfully emitted billing details.

We could change it to forward even on emitter failure, or we could shift the model from decorator to composite, using something to tee reports to both destinations in parallel. No doubt there are other options too.

@jml jml self-assigned this Sep 22, 2017
@rade rade added the bug Broken end user or developer functionality; not working as the developers intended it label Sep 22, 2017
@jml jml closed this as completed in #2860 Sep 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

2 participants