package mdg.engine.proto

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

message ContextualizedQueryLatencyStats

reports.proto:313

message ContextualizedStats

reports.proto:376

Used in: TracesAndStats

message ContextualizedTypeStats

reports.proto:318

message Field

reports.proto:338

Used in: Type

message FieldStat

reports.proto:323

Used in: TypeStat

message PathErrorStats

reports.proto:286

Used in: QueryLatencyStats

message QueryLatencyStats

reports.proto:292

Used in: ContextualizedQueryLatencyStats, ContextualizedStats

message Report

reports.proto:356

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. Agent should either send a trace or include it in the stats for every request in this report. Generally, buffering up until a large size has been reached (say, 4MB) or 5-10 seconds has passed is appropriate. This message used to be know as FullTracesReport, but got renamed since it isn't just for traces anymore

message ReportHeader

reports.proto:264

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: Report

message StatsContext

reports.proto:307

Used in: ContextualizedQueryLatencyStats, ContextualizedStats, ContextualizedTypeStats

message Trace

reports.proto:7

Used in: Trace.QueryPlanNode.FetchNode, TracesAndStats

message Trace.CachePolicy

reports.proto:8

Used in: Trace, Node

enum Trace.CachePolicy.Scope

reports.proto:9

Used in: CachePolicy

message Trace.Details

reports.proto:19

Used in: Trace

message Trace.Error

reports.proto:34

Used in: Node

message Trace.HTTP

reports.proto:41

Used in: Trace

enum Trace.HTTP.Method

reports.proto:46

Used in: HTTP

message Trace.HTTP.Values

reports.proto:42

Used in: HTTP

message Trace.Location

reports.proto:72

Used in: Error

message Trace.Node

reports.proto:82

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

reports.proto:120

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/main/packages/apollo-gateway/src/QueryPlan.ts for more information and details.

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

message Trace.QueryPlanNode.FetchNode

reports.proto:130

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

Used in: QueryPlanNode

message Trace.QueryPlanNode.FlattenNode

reports.proto:154

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

reports.proto:126

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

Used in: QueryPlanNode

message Trace.QueryPlanNode.ResponsePathElement

reports.proto:158

Used in: FlattenNode

message Trace.QueryPlanNode.SequenceNode

reports.proto:122

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

Used in: QueryPlanNode

message TracesAndStats

reports.proto:384

A sequence of traces and stats. An individual trace should either be counted as a stat or trace

Used in: Report

message Type

reports.proto:343

message TypeStat

reports.proto:332

Used in: ContextualizedStats, ContextualizedTypeStats