You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But in real world there are many applications that doesn't honour this limit. Many syslog aggregators use structured data to pass the ingest/auth token. The ingest/auth tokens are generally more than 32 characters. For example, Loggly uses uuid as token which more than 32 characters. Sumo Logic uses random string which is also more than 32 characters.
Considering the real world usages of structured data, it would be useful if there is a way to override structured data id length.
The text was updated successfully, but these errors were encountered:
RFC5424 limits the structured data id(sd-id) to be max of 32 characters in length
But in real world there are many applications that doesn't honour this limit. Many syslog aggregators use structured data to pass the ingest/auth token. The ingest/auth tokens are generally more than 32 characters. For example, Loggly uses uuid as token which more than 32 characters. Sumo Logic uses random string which is also more than 32 characters.
Considering the real world usages of structured data, it would be useful if there is a way to override structured data id length.
The text was updated successfully, but these errors were encountered: