Cisco Cisco Firepower Management Center 2000 Guia Do Programador
2-30
FireSIGHT eStreamer Integration Guide
Chapter 2 Understanding the eStreamer Application Protocol
Streaming Request Message Format
Streaming Request Message Format
The client uses the Streaming Request message to specify to eStreamer the service in the Streaming
Information message that it wants to use, followed by a set of requests for event types and versions to
be streamed. The graphic below shows the message structure and the following table defines the fields.
The requested service is represented by a Streaming Service Request structure described in
Information message that it wants to use, followed by a set of requests for event types and versions to
be streamed. The graphic below shows the message structure and the following table defines the fields.
The requested service is represented by a Streaming Service Request structure described in
.
The graphic below illustrates the format for the Streaming Information message. The shaded field is
specific to this message type. The preceding three fields are the standard message header.
specific to this message type. The preceding three fields are the standard message header.
The fields of the Streaming Request message are:
Streaming Service Request Structure
The eStreamer service sends one Streaming Service Request data structure in the Streaming Information
message for each service it advertises. The eStreamer service does not use the last field of the Streaming
Service Request, which provides for a list of event types to be included.
message for each service it advertises. The eStreamer service does not use the last field of the Streaming
Service Request, which provides for a list of event types to be included.
The client processes the Streaming Service Request structure from eStreamer and uses the same structure
in the response it returns to the server. In the Streaming Service Request that the client sends to the
server, it includes, first, a request for the service advertised by eStreamer, and, second, a list of Streaming
Event Type structures, which specify the requested event types the client wants to receive.
in the response it returns to the server. In the Streaming Service Request that the client sends to the
server, it includes, first, a request for the service advertised by eStreamer, and, second, a list of Streaming
Event Type structures, which specify the requested event types the client wants to receive.
Each Streaming Event Type structure contains two fields to specify the event type and version for each
requested event type. For information on the Streaming Event Type structure, see
requested event type. For information on the Streaming Event Type structure, see
Byte
0
1
2
3
Bit
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Header Version (1)
Message Type (2049)
Message Length
Service...
Table 2-17
Streaming Request Message Fields
Field
Data Type
Description
Header Version
uint16
Set to
1
.
Message Type
uint16
eStreamer message type. Set to
2049
for Streaming Request messages.
Message Length uint32
Length of the content of the message after the message header. Does
not include the bytes in the Header Version, Message Type, and
Message Length fields.
not include the bytes in the Header Version, Message Type, and
Message Length fields.
Service[]
array
List of requested service structures. See