NFS fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
NFS v4/3 specific event fields.
nfs.version-
NFS protocol version number.
type: long
nfs.minor_version-
NFS protocol minor version number.
type: long
nfs.tag- NFS v4 COMPOUND operation tag.
nfs.opcode- NFS operation name, or main operation name, in case of COMPOUND calls.
nfs.status- NFS operation reply status.
ONC RPC specific event fields.
rpc.xid- RPC message transaction identifier.
rpc.status- RPC message reply status.
rpc.auth_flavor- RPC authentication flavor.
rpc.cred.uid-
RPC caller's user id, in case of auth-unix.
type: long
rpc.cred.gid-
RPC caller's group id, in case of auth-unix.
type: long
rpc.cred.gids- RPC caller's secondary group ids, in case of auth-unix.
rpc.cred.stamp-
Arbitrary ID which the caller machine may generate.
type: long
rpc.cred.machinename- The name of the caller's machine.
rpc.call_size-
RPC call size with argument.
type: alias
alias to: source.bytes
rpc.reply_size-
RPC reply size with argument.
type: alias
alias to: destination.bytes