auth.jumpcloud

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

Introduction

Tags beginning with auth.jumpcloud identify events generated by JumpCloud.

Valid tags and data tables

The full tag must have 4 levels. The first two are fixed as auth.jumpcloud. 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
JumpCloud	`auth.jumpcloud.all.events`	`auth.jumpcloud.all.events` Union table This is a union table that collects events from a set of tables for easy access and analysis. Learn more about this union table in this article.
	`auth.jumpcloud.directory.events`	`auth.jumpcloud.directory.events`
	`auth.jumpcloud.ldap.events`	`auth.jumpcloud.ldap.events`
	`auth.jumpcloud.mdm.events`	`auth.jumpcloud.mdm.events`
	`auth.jumpcloud.radius.events`	`auth.jumpcloud.radius.events`
	`auth.jumpcloud.software.events`	`auth.jumpcloud.software.events`
	`auth.jumpcloud.sso.events`	`auth.jumpcloud.sso.events`
	`auth.jumpcloud.systems.events`	`auth.jumpcloud.systems.events`

For more information, read more About Devo tags.

How is the data sent to Devo?

Use the JumpCloud collector.

Table structure

These are the fields displayed in these tables:

Devo latest

auth.jumpcloud

Analytics

Introduction

Valid tags and data tables

How is the data sent to Devo?

Table structure

Related content