Open
Description
openedon Apr 2, 2024
What's wrong?
There is no option to enable TLS while using integrations-next.
We are using app_agent_receiver which is available only under integrations-next, and not under regular integrations. Grafan-agent doesn't recognize http_tls_config parameters when started with integrations-next option.
Note: Same parameters are getting picked and working fine when we try any other integration and don't enable integrations-next option.
Steps to reproduce
Provide TLS config flags in server config and integration config.
Start grafana-agent with integrations-next enabled.
./grafana-agent-linux-amd64 -config.file=./grafana-agent.yaml -enable-features=integrations-next -server.http.enable-tls
System information
RHEL8
Software version
Grafan Agent v0.40.0
Configuration
server:
log_level: debug
http_tls_config:
cert_file: /apps/certs/client.cer
key_file: /apps/certs/server.key
#client_ca_file: /apps/certs/ca.cer
#client_auth_type: RequireAndVerifyClientCert
#min_version: TLS13
integrations:
http_tls_config:
cert_file: /apps/certs/client.cer
key_file: /apps/certs/server.key
#client_ca_file: /apps/certs/ca.cer
#client_auth_type: RequireAndVerifyClientCert
#min_version: TLS13
app_agent_receiver:
autoscrape:
enable: false
instance: "app-client"
logs_instance: "app--client"
logs_labels:
app: "app-client"
kind: ""
logs_send_timeout: "5s"
Logs
2024/04/02 08:29:11 error loading config file ./grafana-agent.yaml: yaml: unmarshal errors:
line 1: field http_tls_config not found in type integrations.SubsystemOptions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment