-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
No validations in otlphttpexporter #4709
Comments
Good catch. The OTLP exporter was done before we had |
Sure, will raise a PR soon! |
@anupamdalmia10 I'm happy to take this one off your hands if you find you don't have the time? |
@josephwoodward, sure @jpkrohling , comments? |
We can still validate that there is at least one endpoint being specified. |
Raised PR for this: #4860 |
Describe the bug
A clear and concise description of what the bug is.
Validate method does not evaluate the given config for the exporter.
opentelemetry-collector/exporter/otlphttpexporter/config.go
Line 42 in 04baaae
Steps to reproduce
If possible, provide a recipe for reproducing the error.
When collector is started with no value for endpoint in config.yaml for otlphttpexporter, collector crashes saying either endpoint or traces_endpoint (for traces pipeline) must be defined. Similar behaviour is observed for metrics and logs pipeline.
What did you expect to see?
A clear and concise description of what you expected to see.
These checks should be performed in Validate method, instead they are being done in factory.go in composeSignalURL method.
opentelemetry-collector/exporter/otlphttpexporter/factory.go
Line 60 in 04baaae
What did you see instead?
A clear and concise description of what you saw instead.
What version did you use?
Version: (e.g.,
v0.4.0
,1eb551b
, etc)What config did you use?
Config: (e.g. the yaml config file)
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: