Руководство Разработчика для Cisco Cisco Firepower Management Center 2000
2-6
FireSIGHT eStreamer Integration Guide
Chapter 2 Understanding the eStreamer Application Protocol
Understanding eStreamer Message Types
•
Client authentication fails (no error message is sent).
•
eStreamer service is shutting down (no error message is sent).
Your client can close the connection to eStreamer server at any time and should attempt to use the error
message format to notify the eStreamer server of the reason.
message format to notify the eStreamer server of the reason.
Understanding eStreamer Message Types
The eStreamer application protocol uses a simple message format that includes a standard message
header and various sub-header fields followed by the record data which contains the message’s payload.
The message header is the same in all eStreamer message types; for more information, see
header and various sub-header fields followed by the record data which contains the message’s payload.
The message header is the same in all eStreamer message types; for more information, see
.
Table 2-2
eStreamer Message Types
Message Type
Name
Description
0
Null message
Both the eStreamer server and the client send null messages
to control data flow. For information, see
to control data flow. For information, see
.
1
Error message
Both the eStreamer server and the client use error messages
to indicate why a connection closed. For information, see
to indicate why a connection closed. For information, see
.
2
Event Stream Request A client sends this message type to the eStreamer service to
initiate a new streaming session and request data. For
information, see
information, see
4
Event Data
The eStreamer service uses this message type to send event
data and metadata to the client. For information, see
data and metadata to the client. For information, see
5
Host Data Request
A client sends this message type to the eStreamer service to
request host data. A session must be started already via an
Event Stream Request message. For information, see
request host data. A session must be started already via an
Event Stream Request message. For information, see
6
Single Host Data
The eStreamer service uses this message type to send single
host data requested by the client. For information, see
host data requested by the client. For information, see
.
7
Multiple Host Data
The eStreamer service uses this message type to send
multiple host data requested by the client. For information,
see
multiple host data requested by the client. For information,
see
2049
Streaming Request
A client uses this message type in extended requests to
specify which of the advertised events from the Stream
Information message it wants. For information, see
specify which of the advertised events from the Stream
Information message it wants. For information, see