cloud.cloud_foundry

[ 1 Introduction ] [ 2 Tag structure ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with cloud.cloud_foundry identify events generated by Cloud Foundry.

Tag structure

The full tag must have three levels. The first two are fixed as cloud.cloud_foundry. The third level identifies the type of events sent, and the fourth level indicates the event subtype.

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
Cloud Foundry application	`cloud.cloud_foundry.application`	`cloud.cloud_foundry.application`
	`cloud.cloud_foundry.bosh`	`cloud.cloud_foundry.bosh`
	`cloud.cloud_foundry.cloud_controller_ng`	`cloud.cloud_foundry.cloud_controller_ng`
	`cloud.cloud_foundry.credhub`	`cloud.cloud_foundry.credhub`
	`cloud.cloud_foundry.rep`	`cloud.cloud_foundry.rep`
	`cloud.cloud_foundry.route_emitter`	`cloud.cloud_foundry.route_emitter`
	`cloud.cloud_foundry.route_registrar`	`cloud.cloud_foundry.route_registrar`
	`cloud.cloud_foundry.service_metrics`	`cloud.cloud_foundry.service_metrics`
	`cloud.cloud_foundry.uaa`	`cloud.cloud_foundry.uaa`

How is the data sent to Devo?

You can forward logs generated by Cloud Foundry using any Syslog drain (for example, Syslog-ng). Learn more about how to send Cloud Foundry logs and their structure here.

Table structure

These are the fields displayed in these tables: