Snowflake Logs Source

Snowflake is a leading cloud data platform known for its scalable, innovative data warehousing, and analytics solutions. It provides organizations with reliable and flexible tools to support data-driven decision-making. Snowflake enables seamless access to essential tables, allowing you to efficiently retrieve data, monitor key metrics, optimize data management processes, and enhance visibility and control over your Snowflake environment.

Data collected

The data will be collected from Snowflake's database using the connection string from the following log types and their respective tables:

Polling Interval	Data
5 minutes	Query History Logs
5 minutes	Security Logs
5 minutes	Custom Event Logs

Setup

Vendor configuration

The Snowflake Logs source requires you to provide the following data to setup the integration:

Account Identifier. An account identifier uniquely identifies a Snowflake account within your organization, as well as throughout the global network of Snowflake-supported cloud platforms and cloud regions. For more information, see Account identifiers.
Username. Snowflake account's login username. For example, SUMOLOGIC.
Password. Snowflake account's login password. For example, yufncixxxxxxxxxp55hbdy7.

Once you have all the required values, set up the source configuration to collect your desired log types available in the configuration section.

Source configuration

When you create a Snowflake Logs source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector and Source.

To configure a Trend Micro source:

Classic UI. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
New UI. In the Sumo Logic top menu select Configuration, and then under Data Collection select Collection. You can also click the Go To... menu at the top of the screen and select Collection.
On the Collection page, click Add Source next to a Hosted Collector.
Search for and select Trend Micro.
Enter a Name for the Source. The description is optional.
(Optional) For Source Category, enter any string to tag the output collected from the source. Category metadata is stored in a searchable field called _sourceCategory.
(Optional) Fields. Click the +Add button to define the fields you want to associate. Each field needs a name (key) and value.
- A green circle with a check mark is shown when the field exists in the Fields table schema.
- An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored, known as dropped.
Snowflake Username. Enter your Snowflake login username.
Snowflake Password. Enter your Snowflake login password.
Snowflake Account Identifier. Enter your Snowflake account name.
Log Types. Select the types of logs you want to collect data from:
- Collect Query History Logs. For example, SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY.
- Collect Security Logs. For example, SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY, SNOWFLAKE.ACCOUNT_USAGE.SESSIONS, SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS, SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY, and SNOWFLAKE.ACCOUNT_USAGE.STAGES.
- Collect Custom Event Logs (Format: DATABASE.SCHEMA.TABLE). Your custom event tables. For example, DATABASE.SCHEMA.TABLE.
  note
  The Snowflake Custom Events feature does not support timestamps with time zones when storing generated data in custom tables. Consequently, data is stored according to the Snowflake account's current time zone. Changing the account's time zone after a source has been configured to collect custom events can lead to data duplication or loss. Therefore, it is recommended not to change the time zone setting once the source has been configured to collect custom events.
Polling Interval. The polling interval is set for 5 minutes by default and can be configured to a maximum of 60 minutes. You can adjust it based on your needs. This sets how often the source checks for new data.
Processing Rules for Logs. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
When you are finished configuring the source, click Save.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See Use JSON to Configure Sources for details.

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	`{"type":"Snowflake Logs"}`	Yes	Define the specific schema type.
sourceType	String	`"Universal"`	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	`null`	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field `_source`.	`"mySource"`
description	String	No	`null`	Type a description of the source.	`"Testing source"`
category	String	No	`null`	Type a category of the source. This value is assigned to the metadata field `_sourceCategory`. See best practices for details.	`"mySource/test"`
fields	JSON Object	No	`null`	JSON map of key-value fields (metadata) to apply to the Collector or source. Use the boolean field _siemForward to enable forwarding to SIEM.	`{"_siemForward": false, "fieldA": "valueA"}`
userName	String	Yes	`null`	Snowflake account login username.	`SUMOLOGIC`
password	String	Yes	`null`	Snowflake account login password.	`yufncixxxxxxxxxp55hbdy7`
accountIdentifier	String	Yes	`null`	Snowflake account name.	`qabbxxr-hj65789`
collectQueryHistory	Boolean	No	`false`	The boolean value to collect the query history tables.	`SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY`
collectSecurity	Boolean	No	`false`	The boolean value to collect the security tables.	- `SNOWFLAKE.ACCOUNT_USAGE.LOGIN_HISTORY` - `SNOWFLAKE.ACCOUNT_USAGE.SESSIONS` - `SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS` - `SNOWFLAKE.ACCOUNT_USAGE.DATA_TRANSFER_HISTORY` - `SNOWFLAKE.ACCOUNT_USAGE.STAGES`
collectEventTable	Boolean	No	`false`	The boolean value to collect the custom event tables.	`DATABASE.SCHEMA.TABLE`
customEventTables	String	No	`null`	List of custom table names from which the data should be collected.
pollingInterval	Integer	Yes	`5 minutes`	Time interval (in minutes) after which the source will check for new data.

JSON example

{
    "api.version": "v1",
    "source": {
        "config": {
            "name": "Snowflake Logs",
            "username": "SUMO",
            "password": "bhwgdy4u28c",
            "accountIdentifier": "gsy64-cnkc8",
            "collectQueryHistory": true,
            "collectSecurity": true,
            "collectEvents": true,
            "pollingIntervalMin": 5,
            "customEventTables": [
                    "SNOW_DB.SCHEMA.TABLE1",
                    "SNOW_INFO.SCHEMA_VAL.TABLE2"
                                 ]
                  },
        "sourceType": "Universal"
    }
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "snowflake_logs_source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Snowflake Logs"
  }
  config = jsonencode({
      "name": "Snowflake Logs",
      "username": "SUMO",
      "password": "bhwgdy4u28c",
      "accountIdentifier": "gsy64-cnkc8",
      "collectQueryHistory": true,
      "collectSecurity": true,
      "collectEvents": true,
      "pollingIntervalMin": 5,
      "customEventTables": [
              "SNOW_DB.SCHEMA.TABLE1",
              "SNOW_INFO.SCHEMA_VAL.TABLE2"
                           ]
  })
}
resource "sumologic_collector" "collector" {
  name        = "my-collector"
  description = "Just testing this"
}

Download example

FAQ

info

Click here for more information about Cloud-to-Cloud sources.

Data collected​

Setup​

Vendor configuration​

Source configuration​

JSON schema​

Configuration Object​

JSON example​

Terraform example​

FAQ​