package mdg.engine.proto

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message ClientNameStats

apollo.proto:293

Used in: QueryStats

message ContextualizedQueryLatencyStats

apollo.proto:341

Used in: QueryStats

message ContextualizedTypeStats

apollo.proto:346

Used in: QueryStats

message Field

apollo.proto:387

Used in: Type

message FieldStat

apollo.proto:351

Used in: TypeStat

message FullTracesReport

apollo.proto:466

This is the top-level message used by the new traces ingress. This is designed for the apollo-engine-reporting TypeScript agent and will eventually be documented as a public ingress API. This message consists solely of traces; the equivalent of the StatsReport is automatically generated server-side from this message. Agents should send traces for all requests in this report. Generally, buffering up until a large size has been reached (say, 4MB) or 5-10 seconds has passed is appropriate.

message MemStats

apollo.proto:397

Used in: StatsReport

message PathErrorStats

apollo.proto:287

Used in: ClientNameStats, QueryLatencyStats

message QueryLatencyStats

apollo.proto:320

Used in: ContextualizedQueryLatencyStats

message QueryStats

apollo.proto:367

Used in: StatsReport

message ReportHeader

apollo.proto:268

The `service` value embedded within the header key is not guaranteed to contain an actual service, and, in most cases, the service information is trusted to come from upstream processing. If the service _is_ specified in this header, then it is checked to match the context that is reporting it. Otherwise, the service information is deduced from the token context of the reporter and then sent along via other mechanisms (in Kafka, the `ReportKafkaKey). The other information (hostname, agent_version, etc.) is sent by the Apollo Engine Reporting agent, but we do not currently save that information to any of our persistent storage.

Used in: FullTracesReport, StatsReport, TraceV1, TracesReport

message StatsContext

apollo.proto:335

Used in: ContextualizedQueryLatencyStats, ContextualizedTypeStats

message StatsReport

apollo.proto:424

Top-level message type for the server-side stats endpoint

message TimeStats

apollo.proto:416

Used in: StatsReport

message Trace

apollo.proto:7

Used in: Trace.QueryPlanNode.FetchNode, TraceV1, Traces, TracesReport

message Trace.CachePolicy

apollo.proto:8

Used in: Trace, Node

enum Trace.CachePolicy.Scope

apollo.proto:9

Used in: CachePolicy

message Trace.Details

apollo.proto:19

Used in: Trace

message Trace.Error

apollo.proto:40

Used in: Node

message Trace.HTTP

apollo.proto:47

Used in: Trace

enum Trace.HTTP.Method

apollo.proto:52

Used in: HTTP

message Trace.HTTP.Values

apollo.proto:48

Used in: HTTP

message Trace.Location

apollo.proto:78

Used in: Error

message Trace.Node

apollo.proto:88

We store information on each resolver execution as a Node on a tree. The structure of the tree corresponds to the structure of the GraphQL response; it does not indicate the order in which resolvers were invoked. Note that nodes representing indexes (and the root node) don't contain all Node fields (eg types and times).

Used in: Trace

message Trace.QueryPlanNode

apollo.proto:126

represents a node in the query plan, under which there is a trace tree for that service fetch. In particular, each fetch node represents a call to an implementing service, and calls to implementing services may not be unique. See https://github.com/apollographql/apollo-server/blob/master/packages/apollo-gateway/src/QueryPlan.ts for more information and details.

Used in: Trace, QueryPlanNode.FlattenNode, QueryPlanNode.ParallelNode, QueryPlanNode.SequenceNode

message Trace.QueryPlanNode.FetchNode

apollo.proto:136

This represents a node to send an operation to an implementing service

Used in: QueryPlanNode

message Trace.QueryPlanNode.FlattenNode

apollo.proto:160

This node represents a way to reach into the response path and attach related entities. XXX Flatten is really not the right name and this node may be renamed in the query planner.

Used in: QueryPlanNode

message Trace.QueryPlanNode.ParallelNode

apollo.proto:132

This represents a set of nodes to be executed in parallel by the Gateway executor

Used in: QueryPlanNode

message Trace.QueryPlanNode.ResponsePathElement

apollo.proto:164

Used in: FlattenNode

message Trace.QueryPlanNode.SequenceNode

apollo.proto:128

This represents a set of nodes to be executed sequentially by the Gateway executor

Used in: QueryPlanNode

message TraceV1

apollo.proto:485

message Traces

apollo.proto:481

Just a sequence of traces with the same statsReportKey.

Used in: FullTracesReport

message TracesReport

apollo.proto:382

Top-level message type for the server-side traces endpoint

message Type

apollo.proto:392

Used in: StatsReport

message TypeStat

apollo.proto:360

Used in: ContextualizedTypeStats, QueryStats