#include <grpc/support/port_platform.h>
#include "src/core/lib/channel/channelz_registry.h"
#include <algorithm>
#include <cstdint>
#include <cstring>
#include <utility>
#include <vector>
#include <grpc/grpc.h>
#include <grpc/support/log.h>
#include <grpc/support/string_util.h>
#include "src/core/lib/channel/channelz.h"
#include "src/core/lib/gprpp/sync.h"
#include "src/core/lib/iomgr/exec_ctx.h"
#include "src/core/lib/json/json.h"
Go to the source code of this file.
Namespaces | |
grpc_core | |
grpc_core::channelz | |
Functions | |
char * | grpc_channelz_get_channel (intptr_t channel_id) |
char * | grpc_channelz_get_server (intptr_t server_id) |
char * | grpc_channelz_get_server_sockets (intptr_t server_id, intptr_t start_socket_id, intptr_t max_results) |
char * | grpc_channelz_get_servers (intptr_t start_server_id) |
char * | grpc_channelz_get_socket (intptr_t socket_id) |
char * | grpc_channelz_get_subchannel (intptr_t subchannel_id) |
char * | grpc_channelz_get_top_channels (intptr_t start_channel_id) |
char* grpc_channelz_get_channel | ( | intptr_t | channel_id | ) |
Definition at line 229 of file channelz_registry.cc.
char* grpc_channelz_get_server | ( | intptr_t | server_id | ) |
Definition at line 192 of file channelz_registry.cc.
char* grpc_channelz_get_server_sockets | ( | intptr_t | server_id, |
intptr_t | start_socket_id, | ||
intptr_t | max_results | ||
) |
Definition at line 208 of file channelz_registry.cc.
char* grpc_channelz_get_servers | ( | intptr_t | start_server_id | ) |
Definition at line 184 of file channelz_registry.cc.
char* grpc_channelz_get_socket | ( | intptr_t | socket_id | ) |
Definition at line 263 of file channelz_registry.cc.
char* grpc_channelz_get_subchannel | ( | intptr_t | subchannel_id | ) |
Definition at line 247 of file channelz_registry.cc.
char* grpc_channelz_get_top_channels | ( | intptr_t | start_channel_id | ) |
Channelz is under active development. The following APIs will see some churn as the feature is implemented. This comment will be removed once channelz is officially supported, and these APIs become stable. For now you may track the progress by following this github issue: https://github.com/grpc/grpc/issues/15340
the following APIs return allocated JSON strings that match the response objects from the channelz proto, found here: https://github.com/grpc/grpc/blob/master/src/proto/grpc/channelz/channelz.proto.
For easy conversion to protobuf, The JSON is formatted according to: https://developers.google.com/protocol-buffers/docs/proto3#json.
Definition at line 176 of file channelz_registry.cc.