The Manager Discovery Service provides an RPC for a management
service to upstream its configuration to a relay service.
This RPC works essentially the same as xDS, except instead of the
client connecting to the server to receive configuration, the
client is connecting to the server send its configuration.
This service enables the relay to merge the configuration of all
currently live management servers as a single aggregated
xDS server without the relay needing to maintain a list
of xDS servers to connect to in the relay itself.
Index into string table |
| num | int64 | | |
| num_unit | int64 | | Should only be present when num is present. Specifies the units of num. Use arbitrary string (for example, "requests") as a custom count unit. If no unit is specified, consumer may apply heuristic to deduce the unit. Consumers may also interpret units like "bytes" and "kilobytes" as memory units and units like "seconds" and "nanoseconds" as time units, and apply appropriate unit conversions to these.
The instruction address for this location, if available. It should be within [Mapping.memory_start...Mapping.memory_limit] for the corresponding mapping. A non-leaf address may be in the middle of a call instruction. It is up to display tools to find the beginning of the instruction if necessary.
Multiple line indicates this location has inlined functions, where the last entry represents the caller into which the preceding entries were inlined.
E.g., if memcpy() is inlined into printf: line[0].function_name == "memcpy" line[1].function_name == "printf" |
| is_folded | bool | | Provides an indication that multiple symbols map to this location's address, for example due to identical code folding by the linker. In that case the line information above represents one of the multiple symbols. This field must be recomputed when the symbolization state of the profile changes. |
The object this entry is loaded from. This can be a filename on disk for the main binary and shared libraries, or virtual abstractions like "[vdso]".
Index into string table |
| build_id | int64 | | A string that uniquely identifies a particular program version with high probability. E.g., for binaries generated by GNU tools, it could be the contents of the .note.gnu.build-id field.
Index into string table |
| has_functions | bool | | The following fields indicate the resolution of symbolic info. |
| has_filenames | bool | | |
| has_line_numbers | bool | | |
| has_inline_frames | bool | | |
A description of the samples associated with each Sample.value. For a cpu profile this might be: [["cpu","nanoseconds"]] or [["wall","seconds"]] or [["syscall","count"]] For a heap profile, this might be: [["allocations","count"], ["space","bytes"]], If one of the values represents the number of events represented by the sample, by convention it should be at index 0 and use sample_type.unit == "count".
frames with Function.function_name fully matching the following regexp will be dropped from the samples, along with their successors.
Index into string table. |
| keep_frames | int64 | | frames with Function.function_name fully matching the following regexp will be kept, even if it matches drop_functions.
Index into string table. |
| time_nanos | int64 | | Time of collection (UTC) represented as nanoseconds past the epoch. |
| duration_nanos | int64 | | Duration of the profile, if a duration makes sense. |
| period_type | ValueType | | The kind of events between sampled ocurrences. e.g [ "cpu","cycles" ] or [ "heap","bytes" ] |
| period | int64 | | The number of events between sampled occurrences. |
| comment | int64 | repeated | Freeform text associated to the profile.
Indices into string table. |
| default_sample_type | int64 | | Index into the string table of the type of the preferred sample value. If unset, clients should default to the last sample value. |
Each Sample records values encountered in some program
context. The program context is typically a stack trace, perhaps
augmented with auxiliary information like the thread-id, some
indicator of a higher level request being handled etc.
The type and unit of each value is defined by the corresponding entry in Profile.sample_type. All samples must have the same number of values, the same as the length of Profile.sample_type. When aggregating multiple samples into a single sample, the result has a list of values that is the elemntwise sum of the lists of the originals.