idmef-message-write Writing IDMEF class to a message buffer If you're not willing to use the prelude_client_send_idmef() function, because for example you want more control over how a message is sent, you can use the idmef-message-write API to send your message manually. The functions defined in this API all take an IDMEF object as an argument and dump this object in a format suitable for writing it to a socket or a file (covering, for example, convertion from host byte order to network byte order), to the provided #prelude_msgbuf_t buffer. The #prelude_msgbuf_t object is just a buffer holding a #prelude_msg_t object. When the buffer is full, the user defined function for #prelude_msgbuf_t will be called, and the user can write his message using the prelude_msg_write() function. idmef_message_write(message, msgbuf); #prelude_msgbuf_t #prelude_msg_t @additional_data: @msg: @Returns: @reference: @msg: @Returns: @classification: @msg: @Returns: @user_id: @msg: @Returns: @user: @msg: @Returns: @address: @msg: @Returns: @process: @msg: @Returns: @web_service: @msg: @Returns: @snmp_service: @msg: @Returns: @service: @msg: @Returns: @node: @msg: @Returns: @source: @msg: @Returns: @file_access: @msg: @Returns: @inode: @msg: @Returns: @checksum: @msg: @Returns: @file: @msg: @Returns: @linkage: @msg: @Returns: @target: @msg: @Returns: @analyzer: @msg: @Returns: @alertident: @msg: @Returns: @impact: @msg: @Returns: @action: @msg: @Returns: @confidence: @msg: @Returns: @assessment: @msg: @Returns: @tool_alert: @msg: @Returns: @correlation_alert: @msg: @Returns: @overflow_alert: @msg: @Returns: @alert: @msg: @Returns: @heartbeat: @msg: @Returns: @message: @msg: @Returns: