Struct SolidSyslogConfig¶
#include <SolidSyslogConfig.h>
struct SolidSyslogConfig
{
struct SolidSyslogBuffer* Buffer;
struct SolidSyslogSender* Sender;
SolidSyslogClockFunction Clock;
SolidSyslogHeaderFieldFunction GetHostname;
void* GetHostnameContext;
SolidSyslogHeaderFieldFunction GetAppName;
void* GetAppNameContext;
SolidSyslogHeaderFieldFunction GetProcessId;
void* GetProcessIdContext;
struct SolidSyslogStore* Store;
struct SolidSyslogStructuredData** Sd;
size_t SdCount;
};
Detailed Description¶
Wiring for SolidSyslog_Create.
NULL is safe for any field: Buffer, Sender, and Store fall back to their Null object and report an error (a no-op unless an error handler is installed; inject the Null* object instead to stay silent), while the callbacks fall back to nil defaults with no error. Whatever you do provide must outlive the created handle; the config struct itself is only read during Create and may be transient.
Public Attributes Documentation¶
Buffer¶
Also sets Log's blocking behaviour (inline vs enqueued).
Clock¶
NULL leaves timestamps at the RFC 5424 nil value.
GetAppName¶
RFC 5424 APP-NAME; NULL emits "-".
GetAppNameContext¶
Passed back to the callback unchanged.
GetHostname¶
RFC 5424 HOSTNAME; NULL emits "-".
GetHostnameContext¶
Passed back to the callback unchanged.
GetProcessId¶
RFC 5424 PROCID; NULL emits "-".
GetProcessIdContext¶
Passed back to the callback unchanged.
Sd¶
Optional: per-instance SD-ELEMENTs, before any per-message SD.
SdCount¶
Sender¶
Store¶
NULL (or SolidSyslogNullStore_Get() ) means no store-and-forward.
The documentation for this class was generated from the following file Core/Interface/SolidSyslogConfig.h