vcs.github

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

Introduction

The tags beginning with vcs.github identify events generated by GitHub.

Valid tags and data tables

The full tag must have 4 levels. The first two are fixed as vcs.github. 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 table

Product / Service	Tags	Data table
Github	`vcs.github.api.enterprise.audit`	`vcs.github.enterprise.audit`
	`vcs.github.api.organization.audit`	`vcs.github.organization.audit`
	`vcs.github.api.organization.dependabot`	`vcs.github.organization.dependabot`
	`vcs.github.api.organization.sso_authorizations`	`vcs.github.organization.sso_authorizations`
	`vcs.github.api.organization.webhooks`	`vcs.github.organization.webhooks`
	`vcs.github.api.repository.actions`	`vcs.github.repository.actions`
	`vcs.github.api.repository.codescan`	`vcs.github.repository.codescan`
	`vcs.github.api.repository.collaborators`	`vcs.github.repository.collaborators`
	`vcs.github.api.repository.commits`	`vcs.github.repository.commits`
	`vcs.github.api.repository.commits`	`vcs.github.repository.commits`
	`vcs.github.api.repository.dependabot_alerts`	`vcs.github.repository.dependabot_alerts`
	`vcs.github.api.repository.events`	`vcs.github.repository.events`
	`vcs.github.api.repository.forks`	`vcs.github.repository.forks`
	`vcs.github.api.repository.issue_comments`	`vcs.github.repository.issue_comments`
	`vcs.github.api.repository.pull_request_commits`	`vcs.github.repository.pull_request_commits`
	`vcs.github.api.repository.pull_requests`	`vcs.github.repository.pull_requests`
	`vcs.github.api.repository.releases`	`vcs.github.repository.releases`
	`vcs.github.api.repository.stargazers`	`vcs.github.repository.stargazers`
	`vcs.github.api.repository.subscribers`	`vcs.github.repository.subscribers`
	`vcs.github.api.repository.subscriptions`	`vcs.github.repository.subscriptions`

For more information, read more About Devo tags.

Table structure

This is the fields displayed by these tables:

How is the data sent to Devo?

To send logs to these tables, Devo provides a collector that you can download and use to send the required events to your Devo domain. You can learn how to use it in this article GitHub collector.