介绍
我们希望客户端能够主动与oap端通信拿到服务端的配置数据然后执行对应的客户端的业务逻辑。
那么本文挑选的Profile的case恰好是符合这样的要求的。下面不妨展开研究一下
实现介绍
撰写grpc契约
Profile.proto文件中,代码如下:(主要看一下getProfileTaskCommands接口)
/*
* 篇幅限制,license声明的注释略去
*/
syntax = "proto3";
option java_multiple_files = true;
option java_package = "org.apache.skywalking.apm.network.language.profile.v3";
option csharp_namespace = "SkyWalking.NetworkProtocol.V3";
option go_package = "skywalking/network/language/profile/v3";
import "common/Common.proto";
service ProfileTask {
// query all sniffer need to execute profile task commands
rpc getProfileTaskCommands (ProfileTaskCommandQuery) returns (Commands) {
}
// collect dumped thread snapshot
rpc collectSnapshot (stream ThreadSnapshot) returns (Commands) {
}
// report profiling task finished
rpc reportTaskFinish (ProfileTaskFinishReport) returns (Commands) {
}
}
message ProfileTaskCommandQuery {
// current sniffer information
string service = 1;
string serviceInstance = 2;
// last command timestamp
int64 lastCommandTime = 3;
}
// dumped thread snapshot
message ThreadSnapshot {
// profile task id
string taskId = 1;
// dumped segment id
string traceSegmentId = 2;
// dump timestamp
int64 time = 3;
// snapshot dump sequence, start with zero
int32 sequence = 4;
// snapshot stack
ThreadStack stack = 5;
}
message ThreadStack {
// stack code signature list
repeated string codeSignatures = 1;
}
// profile task finished report
message ProfileTaskFinishReport {
// current sniffer information
string service = 1;
string serviceInstance = 2;
// profile task
string taskId = 3;
}
实现业务逻辑
注册服务
在ProfileModuleProvider类中注册,前提是必须extends ModuleProvider
/**
* profile task receiver default provider
*/·
public class ProfileModuleProvider extends ModuleProvider {
@Override
public String name() {
return "default";
}
@Override
public Class<? extends ModuleDefine> module() {
return ProfileModule.class;
}
@Override
public ModuleConfig createConfigBeanIfAbsent() {
return null;
}