Costa Tsaousis
Costa Tsaousis
There are several issues mentioned here: 1. Kickstart fails with a `custom` install. 2. Kickstart fails without a documentation link to help the user go through the manual steps required....
> OK, so IOW we _do_ want to support random unknown installation types such as users building _by hand_ on their own system or installing through their system package manager?...
I am just suggesting that adding some documentation for corner-case of users is respectful for them, and easy for us...
btw, `netdata-claim.sh` is needed also to claim static installs. And if the node is old we have this: ```sh # /opt/netdata/usr/bin/netdata-claim.sh -token=qmwHshM-34i6RZrblN1YXaaZJVfuIjkKN5iKohBAhR7wBgs4D5Epd3LTKi_4FoS1_tjEVyqJlEWGYFjySntO7nolTAqgpDvUZpAtE6b4GCkoggo073ILTPptVXihuJvLfM2hIu0 -rooms=02179f1f-9030-486a-a873-9b57f6420a53 -url=https://app.netdata.cloud Token: **************** Base URL: https://app.netdata.cloud Id:...
@stelfrag @cpipilas please check this.
> Also, since we are on the topic of breaking changes for 2.0, it would be nice if we could add improvements in the streaming version negotiation on the list....
@ralphm check this.
> There were some internal discussions regarding netdata 2.0 already. Is this issue meant to encompass all of them or only the new "metric organisation model" described above? Everything that...
We have to find a generic way to do this. Since this is required for many metrics, we need to find a rule at our metric types document for them.