Get desktop application:
View/edit binary Protocol Buffers messages
/ A ContainerMetric records resource usage of an app in a container.
Used in:
/ ID of the contained application.
/ Instance index of the contained application. (This, with applicationId, should uniquely identify a container.)
/ CPU based on number of cores.
/ Bytes of memory used.
/ Bytes of disk used.
/ Maximum bytes of memory allocated to container.
/ Maximum bytes of disk allocated to container.
/ A CounterEvent represents the increment of a counter. It contains only the change in the value; it is the responsibility of downstream consumers to maintain the value of the counter.
Used in:
/ Name of the counter. Must be consistent for downstream consumers to associate events semantically.
/ Amount by which to increment the counter.
/ Total value of the counter. This will be overridden by Metron, which internally tracks the total of each named Counter it receives.
/ Envelope wraps an Event and adds metadata.
/ Unique description of the origin of this event.
/ Type of wrapped event. Only the optional field corresponding to the value of eventType should be set.
/ UNIX timestamp (in nanoseconds) event was wrapped in this Envelope.
/ Deployment name (used to uniquely identify source).
/ Job name (used to uniquely identify source).
/ Index of job (used to uniquely identify source).
/ IP address (used to uniquely identify source).
/ key/value tags to include additional identifying information.
Removed Heartbeat at position 3 Removed HttpStart at position 4 Removed HttpStop at position 5
/ Type of the wrapped event.
Used in:
Removed Heartbeat at position 1 Removed HttpStart at position 2 Removed HttpStop at position 3
/ An Error event represents an error in the originating process.
Used in:
/ Source of the error. This may or may not be the same as the Origin in the envelope.
/ Numeric error code. This is provided for programmatic responses to the error.
/ Error description (preferably human-readable).
/ An HttpStartStop event represents the whole lifecycle of an HTTP request.
Used in:
/ UNIX timestamp (in nanoseconds) when the request was sent (by a client) or received (by a server).
/ UNIX timestamp (in nanoseconds) when the request was received.
/ ID for tracking lifecycle of request.
/ Role of the emitting process in the request cycle.
/ Method of the request.
/ Destination of the request.
/ Remote address of the request. (For a server, this should be the origin of the request.)
/ Contents of the UserAgent header on the request.
/ Status code returned with the response to the request.
/ Length of response (bytes).
/ If this request was made in relation to an appliciation, this field should track that application's ID.
/ Index of the application instance.
/ ID of the application instance.
/ This contains http forwarded-for [x-forwarded-for] header from the request.
/ A LogMessage contains a "log line" and associated metadata.
Used in:
/ Bytes of the log message. (Note that it is not required to be a single line.)
/ Type of the message (OUT or ERR).
/ UNIX timestamp (in nanoseconds) when the log was written.
/ Application that emitted the message (or to which the application is related).
/ Source of the message. For Cloud Foundry, this can be "APP", "RTR", "DEA", "STG", etc.
/ Instance that emitted the message.
/ MessageType stores the destination of the message (corresponding to STDOUT or STDERR).
Used in:
/ HTTP method.
Used in:
/ Type of peer handling request.
Used in:
/ Request is made by this process.
/ Request is received by this process.
/ Type representing a 128-bit UUID. The bytes of the UUID should be packed in little-endian **byte** (not bit) order. For example, the UUID `f47ac10b-58cc-4372-a567-0e02b2c3d479` should be encoded as `UUID{ low: 0x7243cc580bc17af4, high: 0x79d4c3b2020e67a5 }`
Used in:
/ A ValueMetric indicates the value of a metric at an instant in time.
Used in:
/ Name of the metric. Must be consistent for downstream consumers to associate events semantically.
/ Value at the time of event emission.
/ Unit of the metric. Please see http://metrics20.org/spec/#units for ideas; SI units/prefixes are recommended where applicable. Should be consistent for the life of the metric (consumers are expected to report, but not interpret, prefixes).