Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

Not specifying API URI generates multiple errors #14

Closed
codepope opened this issue Dec 19, 2014 · 0 comments · Fixed by #15
Closed

Not specifying API URI generates multiple errors #14

codepope opened this issue Dec 19, 2014 · 0 comments · Fixed by #15

Comments

@codepope
Copy link
Contributor

If the config.yaml lacks the api uri value, rather than take it as an indication that no metrics are needed
the transporter generates an error everytime the interval expires. eg.

transporter: EventEmitter Error: Post : unsupported protocol scheme ""
transporter: EventEmitter Error: Post : unsupported protocol scheme ""
transporter: EventEmitter Error: Post : unsupported protocol scheme ""
nstott added a commit that referenced this issue Dec 19, 2014
@nstott
default to a 60s interval if no interval is passed in. if no config.A…
ec9e36c 
…PI.URI is passed in then use an events.NoopEmitter instead of an HttpPostEmitter. fixes #13 fixes #14
@nstott nstott mentioned this issue Dec 19, 2014
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

This makes the api in the config.yaml optional compose/transporter
1 participant
@codepope