infra.terraform

[ 1 Introduction ] [ 2 Valid tags and data tables ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with infra.terraform identify events generated by Terraform.

Valid tags and data tables

The full tag must have 4 levels. The first two are fixed as infra.terraform. 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
Terraform	`infra.terraform.app.archivist`	`infra.terraform.app.archivist`
	`infra.terraform.app.atlas`	`infra.terraform.app.atlas`
	`infra.terraform.app.build_manager`	`infra.terraform.app.build_manager`
	`infra.terraform.app.build_worker`	`infra.terraform.app.build_worker`
	`infra.terraform.app.other`	`infra.terraform.app.other`
	`infra.terraform.app.sidekiq`	`infra.terraform.app.sidekiq`
	`infra.terraform.app.slug_ingress`	`infra.terraform.app.slug_ingress`
	`infra.terraform.audit.atlas`	`infra.terraform.audit.atlas`
	`infra.terraform.audit.sidekiq`	`infra.terraform.audit.sidekiq`

How is the data sent to Devo?

You can send the logs generated by Terraform by using a relay, fluent, or Syslog ng. Refer to this guide if you need more information.

Table structure

These are the fields displayed in these tables: