You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Here's a simple use case where I'm generating demo logs and then attempting to store them in an AWS S3 sink (technically an S3 compatible store Linode Object Storage).
This config is incorrect. The endpoint should include a https:// prefix in order for it to work. However, this config fails with a very non-obvious error:
It was only by fluke that I discovered I had an invalid endpoint. Ideally we can more clearly indicate to the user that their endpoint is incorrect.
A note for the community
Problem
Here's a simple use case where I'm generating demo logs and then attempting to store them in an AWS S3 sink (technically an S3 compatible store Linode Object Storage).
This config is incorrect. The endpoint should include a
https://
prefix in order for it to work. However, this config fails with a very non-obvious error:It was only by fluke that I discovered I had an invalid endpoint. Ideally we can more clearly indicate to the user that their endpoint is incorrect.
Configuration
Version
vector 0.41.1 (x86_64-apple-darwin 745babd 2024-09-11 14:55:36.802851761)
Debug Output
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: