Closed jiankunking closed 1 year ago
This means the backend is too old. This method is not supported by this version of the backend.
This means the backend is too old. This method is not supported by this version of the backend.
Skywalking 8.6 Which version of go2sky should we use?
Sorry, I can't remember that. We only maintain which versions are supported for the latest OAP server, there is no matrix from the agent perspective. And the whole OAP 8.x is going to end-of-life, https://skywalking.apache.org/events/deprecate-v8/
Sorry, I can't remember that. We only maintain which versions are supported for the latest OAP server, there is no matrix from the agent perspective. And the whole OAP 8.x is going to end-of-life, https://skywalking.apache.org/events/deprecate-v8/
Maybe a table corresponding to the client version and skywalking version should be maintained, or the client releases version and skywalking version should be consistent, similar to the version of elasticsearch client and elasticsearch
In the open-source community, the thing only exists if someone is taking responsibility. Right now, no one is doing that. So, there is nothing called should
or should not
.
Don't take an example of other communities to prove, and to be honest, ElasticSearch support is never consistent, many breaking changes are there in different versions.
use go2sky v1.0.0 for skywalking 8.6 is ok
Describe the bug fetch dynamic configuration error rpc error: code = Unimplemented desc = Method not found: skywalking.v3.ConfigurationDiscoveryService/fetchConfigurations
To Reproduce go2sky version:v1.5.0 skywalking version:8.6
Additional context
After accessing according to the document, the service will always print the following errors