Get desktop application:
View/edit binary Protocol Buffers messages
A DevMode Payload is a message that will contain reqRes data or span data that is forwarded to ingest via the internal extension
The AWS Account ID where this payload originated from
The AWS Region where this payload originated from
The lambda request id where this payload originated from
Extracted Lambda Telemetry API data
The set of lambda traces that were generated via an internal extension
The req or response data from the instrumented lambda function
DevMode Transport Payload that will be used to aggregate reqRes, traces, and logs into a single payload that will be packaged and sent to our DevMode ingest.
The AWS Account ID where this payload originated from
The AWS Region where this payload originated from
The lambda request id where this payload originated from
The request/response data from the instrumented lambda function
The set of lambda traces that were generated via an internal extension
The logs generated via the telemetry API
Used in: ,
The Event ID, this will be a random 8-byte ID encoded as a length 16 lowercase hex string.
The Trace ID, this will be a random 16-byte ID encoded as a length 32 lowercase hex string. The Trace ID is what is used to group all spans for specific trace together.
An optional Span ID to be used to create to show the span context that the event was generated in. In practical terms, every span except the root span will have a parent span ID.
The timestamp of when the Event happened in nanoseconds from EPOCH.
The name that is used internal in the Serverless platform to identify the event.
The optional customTags that can be attached to an event when published. This is expected to be a JSON object in string format.
The optional custom fingerprint that will override our default fingerprinting approach
A message containing any number of Tagsets.
An EventPayload is a message that will contain any number of Events plus the global tags required by our Serverless Ingest Platform.
A list of Events to be ingested. Ingest does not impose a limit on the number of Events in a single payload. It is the responsibility of the Event producer to limit the size of payloads based on their own requirements.
Lambda Telemetry API data. This data is only available for lambda functions that have access to the telemetry API so it will not be included in all regions.
Used in:
Init duration in milliseconds as reported by the metrics on the platform.initReport event
Internal runtime duration in milliseconds as reported by the metrics on the platform.runtimeDone event
Internal runtime duration in milliseconds as reported by the responseLatency span on the platform.runtimeDone event
Used in:
The timestamp of when the LogEvent was created.
The Trace Id that the log's are linked to. When ingesting LogEvents, ingest will attempt to infer the request_id from the payload and attach it. If it is not able to, then it will attempt to reconcile later.
The LogEvent's body.
The calculated severity text value for a log
The calculated severity text value for a log
A message containing any number of Tagsets
Is historical is addedd via ingestion so that we can tell the differnce between historical payloads and live streamed payloads
Type is used to determine the kind of document that is being send via a livestream
A LogPayload is a message that will contain any number of LogEvents plus the global tags required by our Serverless Ingest Platform.
Used in:
A list of LogEvents to be ingested. Ingest does not impose a limit on the number of LogEvents in a single payload. It is the responsibility of the LogEvents' producers to limit the size of payloads based on their own requirements.
Used in:
A unique id for the metric measurement. If this is a Metric from, The metric stream then it will be a randomly generated UUID at ingest time.
The name of the metric. If this is a Metric from the Metric stream, it will be in the format amazonaws.com/<metric_namespace>/<metric_name>. The name is what will be mapped into influx.
The start time of the measure. If this is a Metric from the Metric stream, it will be the Cloudwatch startTime property.
The end time of the measure. If this is a Metric from the Metric stream, it will be the Cloudwatch endTime property.
Tags for the Metric. Any tags can be placed in this field, however, ingest will only write allowlisted, low cardinality tags to Influx.
The number of datapoints for the Metric. If this is a Metric from the Metric stream, it will be the SampleCount from Cloudwatch
The sum of the datapoints for the Metric.
List of quantile values. If this is a Metric from the Metric stream, it will by default have quantile 0.0 and 1.0 to represent the min and max values. If defined during Metric's Stream setup it will have additional quantiles as well.
A value at a given quantile of the distribution. If a Metric has multiple samples, the Min and Max will be represented by, 1. Quantile = 1.0, is the max value 2. Quantile = 0.0, is the min value
Used in:
A MetricPayload is a message that will contain any number of Metrics plus the global tags required by our Serverless Ingest Platform.
A list of Metrics to be ingested. Ingest does not impose a limit on the number of Metrics in a single payload. It is the responsibility of the metrics' producers to limit the size of payloads based on their own requirements.
RequestResponse is the AWS Lambda Event and Response Data. In the Serverless Platform there will be two of these payloads One for Event payload and then one for the payload returned at the end of the function invocation.
Used in: ,
The Global Serverless Platform Tags
The trace Id of the invocation
The span id of the root Lambda Span that request data is attached to on ingest.
The Lambda Request Id.
JSON string of the request or the response body In case of response may be omited if lambda resolved with no value
Type of body
A message containing any number of Tagsets
Is historical is addedd via ingestion so that we can tell the differnce between historical payloads and live streamed payloads
Type is used to determine the kind of document that is being send via a livestream
The timestamp of when the req/res data was generated.
Used in:
Not disclosed (not applicable as property is required)
Function request event
Function handler response
Used in:
The Span ID, this will be a random 8-byte ID encoded as a length 16 lowercase hex string.
The Trace ID, this will be a random 16-byte ID encoded as a length 32 lowercase hex string. The Trace ID is what is used to group all spans for specific trace together.
An optional Parent Span ID to be used to create a trace's Span Dependency graph. In practical terms, every span except the root span will have a parent span ID.
The name of the span describes the type of span that is being produced. currently have a limited set of span names - aws.lambda: Spans the full invocation duration of a lambda function - aws.lambda.invocation: Spans the cold-start duration of a lambda function
The start time of the span in nanoseconds from EPOCH.
The end time of the span in nanoseconds from EPOCH. An important invariant to keep in mind is that the root span will always have the latest end time.
A message containing any number of Tagsets
Eventual input body (e.g. HTTP request body)
Eventual output body (e.g. HTTP response body)
The timestamp that is created in ingestion as the search key
Is historical is addedd via ingestion so that we can tell the differnce between historical payloads and live streamed payloads
Type is used to determine the kind of document that is being send via a livestream
The optional custom tags to be set by the user This is expected to be a JSON object in string format.
TracePayload is a message that will contain any number of Spans plus the global tags required by our Serverless Ingest Platform. A TracePayload DOES NOT necessarily mean that it is a complete Trace. It may contain only a subset of Spans that will make up the complete Trace.
Used in: ,
A list of Spans to be ingest. Ingest does not impose a limit on the number of Spans in a single payload. It is the responsibility of the Span producers to limit the size of payloads based on their own requirements.
A list of Events to be ingested. Ingest does not impose a limit on the number of Events in a single payload. It is the responsibility of the Event producers to limit the size of paylaods based on their own requirements.
The optional custom trace tags to be set by the user This is expected to be a JSON object in string format.
Whether the trace payload represents sampled out invocation and in result contains just core spans and no events
Whether the trace payload represents truncated result (to fit max 256KB size limit)