Pablo Sebastián García

Is the VictoriaMetrics support included in the latest release, v1.110?

@AndrewChubatiuk Thanks for the quick response! I followed that documentation. I'm working with a VictoriaMetrics vmsingle, but I got the following error: ``` 2024-04-30T19:40:00.011925792Z ??? Log level set to info...

Yes, I have deployed the VictoriaMetrics stack in the same cluster in the `victoria-metrics` namespace. Here is the logs after making a kubectl get svc ``` $ kubectl get svc...

@asdfgugus By mounting a volume and setting en env var `CONFIG_PATH` the following error disappeared: ``` ERR Controller: pullWatchers: failed to save statuses failed to save config statuses to file:...

Yes, I made a curl request to the vmcluster service: ``` ~ $ curl http://vmselect-victoria-metrics-k8s-stack.victoria-metrics.svc:8481/select/0/prometheus/api/v1/query?query=up {"status":"success","isPartial":false,"data":{"resultType":"vector","result":[]},"stats":{"seriesFetched": "0","executionTimeMsec":1}} ``` Also made another curl request to the vmagent targets: ``` ~ $...

In my case, it is how Opencost works with VictoriaMetrics. I followed the documentation explaining how to configure both applications but couldn't get it to work. Documentations: - [Repost: Monitoring...

Yes, I know that the latest is the one from the VictoriaMetrics blog, but I tested both configurations to make sure I tried all I could find about it to...