VictoriaMetrics / grafana-datasource

Grafana Plugin for VictoriaMetrics

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[FEATURE]: missed version & help flags output for `victoriametrics_backend_plugin_linux_amd64`

denisgolius opened this issue · comments

./victoriametrics_backend_plugin_linux_amd64 -h
{"@level":"info","@message":"Starting VictoriaMetrics datasource backend ...","@timestamp":"2023-04-04T11:54:11.508891+03:00"}
{"@level":"info","@message":"Profiler","@timestamp":"2023-04-04T11:54:11.509006+03:00","enabled":false}
Usage of ./victoriametrics_backend_plugin_linux_amd64:
  -standalone
    	should this run standalone
    	
./victoriametrics_backend_plugin_linux_amd64 -v
{"@level":"info","@message":"Starting VictoriaMetrics datasource backend ...","@timestamp":"2023-04-04T11:56:56.782846+03:00"}
{"@level":"info","@message":"Profiler","@timestamp":"2023-04-04T11:56:56.782923+03:00","enabled":false}
flag provided but not defined: -v
Usage of ./victoriametrics_backend_plugin_linux_amd64:
  -standalone
    	should this run standalone

 ./victoriametrics_backend_plugin_linux_amd64 -version
{"@level":"info","@message":"Starting VictoriaMetrics datasource backend ...","@timestamp":"2023-04-04T11:57:04.635319+03:00"}
{"@level":"info","@message":"Profiler","@timestamp":"2023-04-04T11:57:04.635397+03:00","enabled":false}
flag provided but not defined: -version
Usage of ./victoriametrics_backend_plugin_linux_amd64:
  -standalone
    	should this run standalone

./victoriametrics_backend_plugin_linux_amd64 --version
{"@level":"info","@message":"Starting VictoriaMetrics datasource backend ...","@timestamp":"2023-04-04T11:57:06.658022+03:00"}
{"@level":"info","@message":"Profiler","@timestamp":"2023-04-04T11:57:06.658156+03:00","enabled":false}
flag provided but not defined: -version
Usage of ./victoriametrics_backend_plugin_linux_amd64:
  -standalone
    	should this run standalone

Would be great to have this flags output which help to recognized the version of executable file and how to use them as well.

@denisgolius this was addressed in #104 and available starting from the next release.

The issue was implemented and included in the v0.5.0 release