pub struct SdIdOrigin(/* private fields */);
Expand description
RFC:
The SD-ID “origin” MAY be used to indicate the origin of a syslog message. The following parameters can be used. All parameters are OPTIONAL.
Specifying any of these parameters is primarily an aid to log analyzers and similar applications.
RFC:
The “ip” parameter denotes an IP address that the originator knows it had at the time of originating the message. It MUST contain the textual representation of an IP address as outlined in Section 6.2.4.
This parameter can be used to provide identifying information in addition to what is present in the HOSTNAME field. It might be especially useful if the host’s IP address is included in the message while the HOSTNAME field still contains the FQDN. It is also useful for describing all IP addresses of a multihomed host.
If an originator has multiple IP addresses, it MAY either list one of its IP addresses in the “ip” parameter or it MAY include multiple “ip” parameters in a single “origin” structured data element. ip
Some sh$t which grandpas from IANA invented and grabbed. enterprise_id
RFC:
The “software” parameter uniquely identifies the software that generated the message. If it is used, “enterpriseId” SHOULD also be specified, so that a specific vendor’s software can be identified. The “software” parameter is not the same as the APP-NAME header field. The “software” parameter is a string. It MUST NOT be longer than 48 characters. software
RFC:
The “swVersion” parameter uniquely identifies the version of the software that generated the message. If it is used, the “software” and “enterpriseId” parameters SHOULD be provided, too.
The “swVersion” parameter is a string. It MUST NOT be longer than 32 characters. sw_version
Implementations§
Trait Implementations§
Source§impl Clone for SdIdOrigin
impl Clone for SdIdOrigin
Source§fn clone(&self) -> SdIdOrigin
fn clone(&self) -> SdIdOrigin
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more