Unable to Install Betterstack

[riteshsonawane1372]

I used Helm for installation of betterstack on my cluster but I encountered an error Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "system:metrics-server-aggregated-reader" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "betterstack-logs": current value is "metrics-server"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "default": current value is "kube-system"

[gyfis]

Hi @riteshsonawane1372, thanks for the report. Seems something is off, since the helm chart works fine for us. Can you share your full helm charts & configs, please?

[riteshsonawane1372]

Hi @riteshsonawane1372, thanks for the report. Seems something is off, since the helm chart works fine for us. Can you share your full helm charts & configs, please?

helm repo add betterstack-logs https://betterstackhq.github.io/logs-helm-chart helm repo update This was the chart I used. When I tested betterstack on my local cluster minikube. It was running fine, I was able to see the logs, but when I tested it on a production EKS cluster I got the above error . This was the values.yaml file

metrics-server:
  enabled: true
vector:
  customConfig:
    sinks:
      better_stack_http_sink:
        auth: $TOKEN
          token: 
      better_stack_http_metrics_sink:
        auth:
          token: $TOKEN

I also test it by removing metrics-server: enabled: true

[curusarn]

Hi @riteshsonawane1372,

Thanks for raising the issue.

You should be able to avoid the errors by disabling metrics-server by using --set metrics-server.enabled=false option. Could you try it out and let me know if it solved your issue? 🙏

Thanks again for reaching out!

[riteshsonawane1372]

@curusarn Thanks Betterstack was installed but the pods are crashing Below are the logs

2023-10-27T02:37:58.579050Z  INFO vector::app: Log level is enabled. level="info"
2023-10-27T02:37:58.579771Z  INFO vector::app: Loading configs. paths=["/etc/vector"]
2023-10-27T02:37:59.956044Z  INFO source{component_kind="source" component_id=better_stack_kubernetes_logs component_type=kubernetes_logs component_name=better_stack_kubernetes_logs}: vector::sources::kubernetes_logs: Obtained Kubernetes Node name to collect logs for (self). self_node_name="ip-*.eu-west-1.compute.internal"
2023-10-27T02:37:59.965380Z  INFO source{component_kind="source" component_id=better_stack_kubernetes_logs component_type=kubernetes_logs component_name=better_stack_kubernetes_logs}: vector::sources::kubernetes_logs: Excluding matching files. exclude_paths=["**/*.gz", "**/*.tmp"]
2023-10-27T02:38:01.378705Z ERROR vector::topology: Configuration error. error=Transform "better_stack_kubernetes_parser":
error[E105]: call to undefined function
    ┌─ :268:29
    │
268 │     .dt = format_timestamp!(to_timestamp(del(.redis.unix_timestamp)) ?? now(), "%+")
    │                             ^^^^^^^^^^^^
    │                             │
    │                             undefined function
    │                             did you mean "is_timestamp"?
    │
    = learn more about error code 105 at https://errors.vrl.dev/105
    = see language documentation at https://vrl.dev
    = try your code in the VRL REPL, learn more at https://vrl.dev/examples

[PetrHeinz]

Hello @riteshsonawane1372, thanks for the detailed info 🙌

This crashing is because of changed Vector to v0.33, which wasn't compatible with previous VRL configuration. Should be fixed by #3.

Could you run helm repo update to fetch the new chart version, and retry? 🙏

[riteshsonawane1372]

@PetrHeinz Thanks Petr. Now everything is working good.

[riteshsonawane1372]

Thanks to @curusarn @gyfis

[Wei102193]

so the metrics-server does not work atm?