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

bug: api_version Error When Using HTTP Sink type in victorialogs-single-server Helm Chart #2043

Open
Angel0r opened this issue Mar 6, 2025 · 3 comments
Labels

Comments

@Angel0r
Copy link

Angel0r commented Mar 6, 2025

Chart name and version
chart: victoria-logs-single
version: v0.8.11

Describe the bug
Vector works fine with sink.vlogs.type:elasticsearch, however when I change the configuration to use type: http I get the following error:
ERROR vector::cli: Configuration error. error=unknown field api_version

Custom values
My configuration:

        sinks:
          vlogs:
            inputs:
              - parser
            type: http
            uri: http://victorialogs-victoria-logs-single-server.vlogs.svc.cluster.local:9428/insert/jsonline
            compression: gzip
            encoding:
              codec: json
            framing:
              method: newline_delimited
            healthcheck:
              enabled: false
@AndrewChubatiuk
Copy link
Collaborator

AndrewChubatiuk commented Mar 8, 2025

please check default chart parameters, api_version is set there to v8 for elasticsearch output type and this parameter is not relevant for http output. Same is for endpoints and mode parameters.

if you've decided to change vector output type you should disable vector subchart and install and configure it on your own. Elasticsearch output is the only Vector output, which allows to configure multiple endpoints using a single sink, which is used for VictoriaLogs HA mode setup.

@Angel0r
Copy link
Author

Angel0r commented Mar 11, 2025

Hey @AndrewChubatiuk,

I had checked them, but I thought that if I changed the type to HTTP, it would adapt since the documentation doesn't say that it works only with Elasticsearch(or maybe I missed that).

Thank you very much!

/Angelos

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants