About the Monte Carlo collector

The Monte Carlo collector harvests resources from your Monte Carlo environment such as Monitors and Incidents, and the tables associated with the Monitors and Incidents.

The collector currently supports harvesting resources from Monte Carlo for the following monitored target databases: Databricks, Redshift, Snowflake, and Bigquery.

Important

The Monte Carlo collector can be run in the Cloud or on-premise using Docker or Jar files.

Note

The latest version of the Collector is 2.206. To view the release notes for this version and all previous versions, please go here.

What is cataloged

The collector catalogs the following information.

Table 1.

Object	Information cataloged
Monitor	Name (Monitor Description or UUID), Description, Created Time, Monitor Status Type, External link, Paused State, Snoozable state, Snoozed state, Is Template Managed, Monitor type, Description, Schedule type, User the monitor was created by
Incident	Title, Incident ID, Incident Time, External Link, Incident Feedback, Incident Reaction Type, Owner Email, Severity, Incident type and sub-types
Table	External Link, Incidents by Status Summary, Incidents Under Investigation Summary, Monitors Summary, Table ID, Schema and database that tables belong to

Relationships between objects

By default, the harvested metadata includes catalog pages for the following resource types. Each catalog page has a relationship to the other related resource types. If the metadata presentation for this data source has been customized with the help of the data.world Solutions team, you may see other resource pages and relationships.

Table 2.

Resource page	Relationship
Table	Incident that occurred on the table Monitor for the table
Incident	Table that Incident occurred on
Monitor	Table that is monitored

Authentication supported

The Monte Carlo collector authenticates to Monte Carlo using API key.

In this section: