stream.confluent

[ 1 Introduction ] [ 2 Valid tags and data tables ] [ 3 Table structure ]

Introduction

The tags beginning with stream.confluent identify events generated by Confluent Platform belonging to Confluent.

Valid tags and data tables

The full tag must have at least 3 levels. The first two are fixed as stream.confluent. The third level identifies the type of events sent. The fourth level indicates the event subtypes.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service	Tags	Data tables

Product / Service	Tags	Data tables
Confluent Platform	`stream.confluent.kafka.controller`	`stream.confluent.kafka.controller`
	`stream.confluent.kafka.server`	`stream.confluent.kafka.server`
	`stream.confluent.zookeeper`	`stream.confluent.zookeeper`

For more information, read more About Devo tags.

Table structure

These are the fields displayed in these tables:

stream.confluent.kafka.controller

Field	Type	Extra fields

Field	Type	Extra fields
eventdate	`timestamp`
hostname	`str`
eventdate_instance	`str`
level	`str`
trace	`str`
message	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`

stream.confluent.kafka.server

Field	Type	Extra fields

Field	Type	Extra fields
eventdate	`timestamp`
hostname	`str`
eventdate_instance	`str`
level	`str`
trace	`str`
message	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`

stream.confluent.zookeeper

Field	Type	Extra fields

Field	Type	Extra fields
eventdate	`timestamp`
hostname	`str`
eventdate_instance	`str`
level	`str`
trace	`str`
message	`str`
hostchain	`str`	✓
tag	`str`	✓
rawMessage	`str`

Devo latest