Edge logging

When you encounter an issue in Edge, you can use diagnostic and log files in Datadog which provide data about the issue. If you want to report a problem to Collibra Support, you can include these files in the support ticket. As a result, Collibra Support will be able to determine what went wrong and find a solution to your issue.

You can create a diagnostics ZIP file with logs and information about the server or EKS environment on which you installed the Edge site. Edge also generates two types of log files that are not included in the diagnostics file:

Edge diagnostics file

The Edge diagnostics file is a ZIP file that is created by running the diagnostics script in the Edge site installer folder. The diagnostics script checks amongst others:

  • Your operating system setup
  • Your firewall settings
  • Connectivity information
  • Edge cluster logs

You can send the diagnostics file to Collibra Support when you have an issue with the Edge site installation.

Edge infrastructure log files

Edge infrastructure logs contain Edge infrastructure information, for example, Edge status updates and capability information. The logs from Datadog can be used by Collibra Support to help solve general Edge issues. The log files do not contain any database content or private information.

By default, the Edge infrastructure log files are always enabled on an information level. You can enable debug level logging per specific capability when you add or edit an Edge capability. As a result, Edge sends infrastructure logs with more information about that capability to Collibra Data Intelligence Platform. Edge infrastructure log files can contain the following information:

  • Job execution phases
  • The Edge status
  • Service updates
  • System upgrades

These log files can be accessed only by Collibra Support.

Note By default, Debug logging for an Edge capability is set to False. We highly recommend enabling only the Debug logging for an Edge capability if an issue arises.

Metadata connector log files

Metadata connector log files contain the logs of the JDBC connections between the Edge capability and your data source.

These log files are generated when you:

  • Register a database.
  • Synchronize a schema.
  • Trigger data sampling.
  • Run profiling and classification.
  • Synchronize technical lineage.
  • Synchronize data quality.

Note Metadata connector log files are not created when "Test Connection" is performed on an Edge.

These log files can be used by Collibra Support to help solve issues with processing or accessing data. The log files may contain information about your data source.

For security reasons, these log files are not automatically sent to your Collibra Data Intelligence Platform environment. You can, however, create the log files, save them, review them locally, and then attach them to a Collibra support ticket.

Edge system monitoring

The system monitoring, run via OpenTelemetry, sends the following information to your Collibra environment:

  • CPU usage
  • Memory usage
  • Network statistics

Collibra Support can then analyze this information to troubleshoot potential anomalies. This data is available only to Collibra personnel.

Verbosity log levels

The verbosity log levels indicate how much information you want to see in the Catalog Connector log files. You can change the verbosity log levels in the Edge capability for which you want to create logs. The following verbosity log levels are available.

Verbosity log level

Description

No logging

The Catalog Connector logs are not created.

This is the default level.

Low

The Catalog Connector logs contain the following:

  • All connection query logs
  • Any errors

Medium

The Catalog Connector logs include the Low logs and the following:

  • All cache queries
  • Additional information about the request

High

The Catalog Connector logs include the Medium logs and the following:

  • The body of the request
  • The response