Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
,used for POLICY_UPDATED and POLICY_DELETED
used for ENDPOINT_REGENERATE_SUCCESS and ENDPOINT_REGENERATE_FAILURE
used for ENDPOINT_CREATED and ENDPOINT_DELETED
used for IPCACHE_UPSERTED and IPCACHE_DELETED
AgentEventType is the type of agent event. These values are shared with type AgentNotification in pkg/monitor/api/types.go.
Used in:
Used in:
These types correspond to definitions in pkg/policy/l4.go.
Used in:
CiliumEventType from which the flow originated.
Used in:
type of event the flow originated from, i.e. github.com/cilium/cilium/pkg/monitor/api.MessageType*
sub_type may indicate more details depending on type, e.g. - github.com/cilium/cilium/pkg/monitor/api.Trace* - github.com/cilium/cilium/pkg/monitor/api.Drop* - github.com/cilium/cilium/pkg/monitor/api.DbgCapture*
DNS flow. This is basically directly mapped from Cilium's [LogRecordDNS](https://github.com/cilium/cilium/blob/04f3889d627774f79e56d14ddbc165b3169e2d01/pkg/proxy/accesslog/record.go#L264):
Used in:
DNS name that's being looked up: e.g. "isovalent.com."
List of IP addresses in the DNS response.
TTL in the DNS response.
List of CNames in the DNS response.
Corresponds to DNSDataSource defined in: https://github.com/cilium/cilium/blob/04f3889d627774f79e56d14ddbc165b3169e2d01/pkg/proxy/accesslog/record.go#L253
Return code of the DNS request defined in: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6
String representation of qtypes defined in: https://tools.ietf.org/html/rfc1035#section-3.2.3
String representation of rrtypes defined in: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4
These values are shared with pkg/monitor/api/datapath_debug.go and bpf/lib/dbg.h.
Used in:
Used in:
,These values are shared with pkg/monitor/api/datapath_debug.go and bpf/lib/dbg.h.
Used in:
These values are shared with pkg/monitor/api/drop.go and bpf/lib/common.h. Note that non-drop reasons (i.e. values less than api.DropMin) are not used here.
Used in:
,non-drop reasons
drop reasons
A BPF program wants to tail call into bpf_host, but the host datapath hasn't been loaded yet.
A BPF program wants to tail call some endpoint's policy program in cilium_call_policy, but the program is not available.
An Egress Gateway node matched a packet against an Egress Gateway policy that didn't select a valid Egress IP.
Used in:
,labels in `foo=bar` format.
Used in:
Used in:
Used in:
EventType are constants are based on the ones from <linux/perf_event.h>.
EventSample is equivalent to PERF_RECORD_SAMPLE.
RecordLost is equivalent to PERF_RECORD_LOST.
EventTypeFilter is a filter describing a particular event type.
Used in:
type is the primary flow type as defined by: github.com/cilium/cilium/pkg/monitor/api.MessageType*
match_sub_type is set to true when matching on the sub_type should be done. This flag is required as 0 is a valid sub_type.
sub_type is the secondary type, e.g. - github.com/cilium/cilium/pkg/monitor/api.Trace*
Used in:
Used in:
,uuid is a universally unique identifier for this flow.
only applicable to Verdict = DROPPED. deprecated in favor of drop_reason_desc.
auth_type is the authentication type specified for the flow in Cilium Network Policy. Only set on policy verdict events.
l2
l3
l4
NodeName is the name of the node from which this Flow was captured.
node labels in `foo=bar` format.
all names the source IP can have.
all names the destination IP can have.
L7 information. This field is set if and only if FlowType is L7.
Deprecated. This suffers from false negatives due to protobuf not being able to distinguish between the value being false or it being absent. Please use is_reply instead.
EventType of the originating Cilium event
source_service contains the service name of the source
destination_service contains the service name of the destination
traffic_direction of the connection, e.g. ingress or egress
policy_match_type is only applicable to the cilium event type PolicyVerdict https://github.com/cilium/cilium/blob/e831859b5cc336c6d964a6d35bbd34d1840e21b9/pkg/monitor/datapath_policy.go#L50
Only applicable to cilium trace notifications, blank for other types.
Cilium datapath trace reason info.
Cilium datapath filename and line number. Currently only applicable when Verdict = DROPPED.
only applicable to Verdict = DROPPED.
is_reply indicates that this was a packet (L4) or message (L7) in the reply direction. May be absent (in which case it is unknown whether it is a reply or not).
Only applicable to cilium debug capture events, blank for other types
interface is the network interface on which this flow was observed
proxy_port indicates the port of the proxy to which the flow was forwarded
trace_context contains information about a trace related to the flow, if any.
sock_xlate_point is the socket translation point. Only applicable to TraceSock notifications, blank for other types
socket_cookie is the Linux kernel socket cookie for this flow. Only applicable to TraceSock notifications, zero for other types
cgroup_id of the process which emitted this event. Only applicable to TraceSock notifications, zero for other types
This is a temporary workaround to support summary field for pb.Flow without duplicating logic from the old parser. This field will be removed once we fully migrate to the new parser.
extensions can be used to add arbitrary additional metadata to flows. This can be used to extend functionality for other Hubble compatible APIs, or experiment with new functionality without needing to change the public API.
The CiliumNetworkPolicies allowing the egress of the flow.
The CiliumNetworkPolicies allowing the ingress of the flow.
The CiliumNetworkPolicies denying the egress of the flow.
The CiliumNetworkPolicies denying the ingress of the flow.
FlowFilter represent an individual flow filter. All fields are optional. If multiple fields are set, then all fields must match for the filter to match.
Used in:
uuid filters by a list of flow uuids.
source_ip filters by a list of source ips. Each of the source ips can be specified as an exact match (e.g. "1.1.1.1") or as a CIDR range (e.g. "1.1.1.0/24").
source_ip_xlated filters by a list IPs. Each of the IPs can be specified as an exact match (e.g. "1.1.1.1") or as a CIDR range (e.g. "1.1.1.0/24").
source_pod filters by a list of source pod name prefixes, optionally within a given namespace (e.g. "xwing", "kube-system/coredns-"). The pod name can be omitted to only filter by namespace (e.g. "kube-system/") or the namespace can be omitted to filter for pods in any namespace (e.g. "/xwing")
source_fqdn filters by a list of source fully qualified domain names
source_labels filters on a list of source label selectors. Selectors support the full Kubernetes label selector syntax.
source_service filters on a list of source service names. This field supports the same syntax as the source_pod field.
source_workload filters by a list of source workload.
destination_ip filters by a list of destination ips. Each of the destination ips can be specified as an exact match (e.g. "1.1.1.1") or as a CIDR range (e.g. "1.1.1.0/24").
destination_pod filters by a list of destination pod names
destination_fqdn filters by a list of destination fully qualified domain names
destination_label filters on a list of destination label selectors
destination_service filters on a list of destination service names
destination_workload filters by a list of destination workload.
traffic_direction filters flow by direction of the connection, e.g. ingress or egress.
only return Flows that were classified with a particular verdict.
only applicable to Verdict = DROPPED (e.g. "POLICY_DENIED", "UNSUPPORTED_L3_PROTOCOL")
interface is the network interface on which this flow was observed.
event_type is the list of event types to filter on
http_status_code is a list of string prefixes (e.g. "4+", "404", "5+") to filter on the HTTP status code
protocol filters flows by L4 or L7 protocol, e.g. (e.g. "tcp", "http")
source_port filters flows by L4 source port
destination_port filters flows by L4 destination port
reply filters flows based on the direction of the flow.
dns_query filters L7 DNS flows by query patterns (RE2 regex), e.g. 'kube.*local'.
source_identity filters by the security identity of the source endpoint.
destination_identity filters by the security identity of the destination endpoint.
GET, POST, PUT, etc. methods. This type of field is well suited for an enum but every single existing place is using a string already.
http_path is a list of regular expressions to filter on the HTTP path.
http_url is a list of regular expressions to filter on the HTTP URL.
http_header is a list of key:value pairs to filter on the HTTP headers.
tcp_flags filters flows based on TCP header flags
node_name is a list of patterns to filter on the node name, e.g. "k8s*", "test-cluster/*.domain.com", "cluster-name/" etc.
node_labels filters on a list of node label selectors. Selectors support the full Kubernetes label selector syntax.
filter based on IP version (ipv4 or ipv6)
trace_id filters flows by trace ID
experimental contains filters that are not stable yet. Support for experimental features is always optional and subject to change.
Experimental contains filters that are not stable yet. Support for experimental features is always optional and subject to change.
Used in:
cel_expression takes a common expression language (CEL) expression returning a boolean to determine if the filter matched or not. You can use the `_flow` variable to access fields on the flow using the flow.Flow protobuf field names. See https://github.com/google/cel-spec/blob/v0.14.0/doc/intro.md#introduction for more details on CEL and accessing the protobuf fields in CEL. Using CEL has performance cost compared to other filters, so prefer using non-CEL filters when possible, and try to specify CEL filters last in the list of FlowFilters.
Used in:
not sure about the underscore here, but `L34` also reads strange
L7 information for HTTP flows. It corresponds to Cilium's [accesslog.LogRecordHTTP](https://github.com/cilium/cilium/blob/728c79e427438ab6f8d9375b62fccd6fed4ace3a/pkg/proxy/accesslog/record.go#L206) type.
Used in:
Used in:
,Used in:
Used in:
Used in:
source_xlated is the post translation source IP when the flow was SNATed (and in that case source is the the original source IP).
This field indicates whether the TraceReasonEncryptMask is set or not. https://github.com/cilium/cilium/blob/ba0ed147bd5bb342f67b1794c2ad13c6e99d5236/pkg/monitor/datapath_trace.go#L27
Used in:
Used in:
,L7 information for Kafka flows. It corresponds to Cilium's [accesslog.LogRecordKafka](https://github.com/cilium/cilium/blob/728c79e427438ab6f8d9375b62fccd6fed4ace3a/pkg/proxy/accesslog/record.go#L229) type.
Used in:
This enum corresponds to Cilium's L7 accesslog [FlowType](https://github.com/cilium/cilium/blob/728c79e427438ab6f8d9375b62fccd6fed4ace3a/pkg/proxy/accesslog/record.go#L26):
Used in:
Used in:
ICMP is technically not L4, but mutually exclusive with the above
Message for L7 flow, which roughly corresponds to Cilium's accesslog [LogRecord](https://github.com/cilium/cilium/blob/728c79e427438ab6f8d9375b62fccd6fed4ace3a/pkg/proxy/accesslog/record.go#L141):
Used in:
Latency of the response
L7 field. This field is set if and only if FlowType is L7.
LostEvent is a message which notifies consumers about a loss of events that happened before the events were captured by Hubble.
Used in:
,source is the location where events got lost.
num_events_lost is the number of events that haven been lost at source.
cpu on which the event was lost if the source of lost events is PERF_EVENT_RING_BUFFER.
Used in:
PERF_EVENT_RING_BUFFER indicates that events were dropped in the BPF perf event ring buffer, indicating that userspace agent did not keep up with the events produced by the datapath.
OBSERVER_EVENTS_QUEUE indicates that events were dropped because the Hubble events queue was full, indicating that the Hubble observer did not keep up.
HUBBLE_RING_BUFFER indicates that the event was dropped because it could not be read from Hubble's ring buffer in time before being overwritten.
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
This mirrors enum xlate_point in bpf/lib/trace_sock.h
Used in:
Pre service translation
Post service translation
Pre reverse service translation
Post reverse service translation
Used in:
Used in:
,Used in:
TraceContext contains trace context propagation data, i.e. information about a distributed trace. For more information about trace context, check the [W3C Trace Context specification](https://www.w3.org/TR/trace-context/).
Used in:
parent identifies the incoming request in a tracing system.
Used in:
Cilium treats 0 as TO_LXC, but its's something we should work to remove. This is intentionally set as unknown, so proto API can guarantee the observation point is always going to be present on trace events.
TO_PROXY indicates network packets are transmitted towards the l7 proxy.
TO_HOST indicates network packets are transmitted towards the host namespace.
TO_STACK indicates network packets are transmitted towards the Linux kernel network stack on host machine.
TO_OVERLAY indicates network packets are transmitted towards the tunnel device.
TO_ENDPOINT indicates network packets are transmitted towards endpoints (containers).
FROM_ENDPOINT indicates network packets were received from endpoints (containers).
FROM_PROXY indicates network packets were received from the l7 proxy.
FROM_HOST indicates network packets were received from the host namespace.
FROM_STACK indicates network packets were received from the Linux kernel network stack on host machine.
FROM_OVERLAY indicates network packets were received from the tunnel device.
FROM_NETWORK indicates network packets were received from native devices.
TO_NETWORK indicates network packets are transmitted towards native devices.
TraceParent identifies the incoming request in a tracing system.
Used in:
trace_id is a unique value that identifies a trace. It is a byte array represented as a hex string.
Used in:
Used in:
,Used in:
Used in:
,UNKNOWN is used if there is no verdict for this flow event
FORWARDED is used for flow events where the trace point has forwarded this packet or connection to the next processing entity.
DROPPED is used for flow events where the connection or packet has been dropped (e.g. due to a malformed packet, it being rejected by a network policy etc). The exact drop reason may be found in drop_reason_desc.
ERROR is used for flow events where an error occurred during processing
AUDIT is used on policy verdict events in policy audit mode, to denominate flows that would have been dropped by policy if audit mode was turned off
REDIRECTED is used for flow events which have been redirected to the proxy
TRACED is used for flow events which have been observed at a trace point, but no particular verdict has been reached yet
TRANSLATED is used for flow events where an address has been translated
Used in:
,