> Automatic triggering How do you know about inconsistent? For the metadata missing or partial missing, there is no way the backend could know. Could you info me more about inconsistent check mechanism? The only thing in my mind, which doesn't break performance, is when you can't get the name of service/endpoint-ip from cache, you know something is wrong. But this is really part of fact called inconsistent check.
The id before and after the reset may change, then the metrics aggregated according to the id are not allowed. > For me, this could be dangerous to tell people, SkyWalking has inconsistent > check, because this mechanism can't guarantee no exception = data is right. SkyWalking's consistency check adds instance code to uniquely determine instance to guarantee no-exception=data is right > If you can't do this manually, I doubt the meaning of this check. This is not > a pattern recognition, which AI may do better than human, otherwise, this is > a fault check, I am pretty sure, human check is the most reliable thing and > the final defence. I am wrong in this place, the server side can also send instructions to the agent reset through the grpc response. But considering this operation is not a common operation and security problem, do not use the server side reset >How is this could identify the needs to thing? Could you explain more? >Uniquely determine the instance location this is an ID of service instance, >yes. Then? By adding an instanceCode to the agent configuration file, which is determined by the operation and maintenance personnel, they can also find the problem agent according to the instanceCode. [ Full content available at: https://github.com/apache/incubator-skywalking/issues/1585 ] This message was relayed via gitbox.apache.org for [email protected]
