-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
otlphttp exporter not able to export logs to the service endpoint #5779
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
It's hard to tell what's going on. Please add the For reference, I was testing a local service I'm building and I didn't have problems with the OTLP HTTP Exporter for Logs. My configuration was something like: receivers:
journald:
directory: /var/log/journal/a04e3a44cdd740f88d6a7ae3bb8c70cf
exporters:
logging:
verbosity: detailed
otlphttp:
endpoint: http://localhost:8000/otlp
tls:
insecure: true
headers:
"X-Scope-OrgID": 1
processors:
service:
extensions: []
pipelines:
logs:
receivers: [journald]
processors: []
exporters: [logging, otlphttp] |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
Perhaps related to open-telemetry/opentelemetry-collector#7009 ? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
Closing, as we didn't hear back after a few months... |
hello @jpkrohling 2024-03-07T14:12:07.150+0530 info [email protected]/service.go:169 Everything is ready. Begin running and processing data. And these log messages repeatedly getting printed, I dont know how to proceed further |
Describe the bug
otlphttp exporter does not work .
Steps to reproduce
used the filelog receiver to retrieve files and then send the ouput to a sink using otlphttp exporter.
What did you expect to see?
exporter able to send logs .
What did you see instead?
i dont see any logs being sent after reading from files.
this is the log i see for the collector container
i dont see any exporter logs in action and i can clearly see that exporter is started and working . there is no error there.
the service is running as a clusterip service in the cluster and the url is correct
What version did you use?
What config did you use?
this service is pointing to a deployment which has the endpoint : /audit-log/logging/v1/eventLogs. i am able to hit the endpoint when i use port-forward with the service and hit in the browser , but i am not able to hit it using the exporter.
Please let me know what is wrong here and if possible can someone give a correct example of using filelog receiver and otlphttp exporter . thanks .
Environment
OS: MacOS.
The text was updated successfully, but these errors were encountered: