Debug Log Monitoring for Salesforce Cloud (Configure)

⚙️ Configure Salesforce Debug Log Monitoring

GermainUX collects and analyzes Salesforce Debug Logs to provide detailed visibility into Apex execution and related Salesforce activity.

🔍 What Debug Log Monitoring Can Collect

This information helps teams identify why a Salesforce transaction was slow, failed, or produced an unexpected result.

📈 What Debug Log Monitoring Helps Analyze

Use Salesforce Debug Log Monitoring to:

Debug Log Monitoring is performed by the GermainUX Engine.

✅ Prerequisites

Before configuring Debug Log Monitoring, confirm that:

For the initial integration, see Deploy GermainUX for Salesforce.

🔁 Enable Debug Log Monitoring

Debug Log Monitoring is enabled automatically when Salesforce monitoring is deployed through the Salesforce Application wizard.

To deploy it:

1. Open GermainUX Workspace.

2. Open the left navigation menu.

3. Select Wizards.

4. Select Salesforce Application.

5. Choose the GermainUX Engine that will monitor Salesforce.

6. Enter the Salesforce connection and authentication settings.

7. Expand Show Advanced if you want to customize the collection interval.

8. Set Debug Log Monitoring Interval.

9. Complete the wizard.

The wizard deploys three related components used by Salesforce Debug Log Monitoring.

⏰ Default Collection Frequency

By default, GermainUX retrieves Salesforce Debug Logs once per hour.

The appropriate interval depends on:

A shorter interval provides fresher data but increases API activity and processing. A longer interval reduces collection activity but may delay investigation and increase the risk that short-lived source data is no longer available.

🔧 Configure the Frequency During Deployment

During the initial Salesforce Application wizard:

1. Select Show Advanced.

2. Locate Debug Log Monitoring Interval.

   

3. Enter the required frequency.

4. Complete the wizard.

🔁 Change the Frequency After Deployment

To update the schedule of an existing debug-log monitor:

1. Open GermainUX Workspace.

2. Open the left navigation menu.

3. Select Germain.

4. Open the State tab.

5. Search for:

   Type Name = Salesforce Debug Log Monitor
   

6. Select the applicable component.

7. Update Execution Schedule.

8. Save the change.

9. Repeat the review for each related Debug Log Monitoring component when applicable.

Confirm that the related components use compatible schedules and remain enabled.

⛔ Disable Debug Log Monitoring

Salesforce Debug Log Monitoring uses three related components. Disable all three to stop collection completely.

1. Open GermainUX Workspace.

2. Open the left navigation menu.

3. Select Germain.

4. Open the State tab.

5. Search for:

   Salesforce Debug Log
   

6. Identify all three related components for the Salesforce organization.

7. Turn off the toggle in the Enabled column for each component.

8. Save the changes if prompted.

   

Disabling only one component may leave part of the debug-log collection or processing workflow active.

Previously collected data remains available according to the configured GermainUX retention policy.

▶️ Re-enable Debug Log Monitoring

To resume collection:

1. Return to Germain → State.

2. Search for Salesforce Debug Log.

3. Enable all three related components.

4. Confirm their execution schedules.

5. Save the configuration.

6. Allow the next scheduled executions to complete.

📦 Data Collected From Debug Logs

The exact information depends on the logging generated by Salesforce, but GermainUX can extract and normalize the following types of evidence.

Exceptions

Exception data can include:

Use this information to group recurring exceptions and identify their source.

⚡ Code-Unit Execution

Code-unit events can reveal:

🔎 SOQL Execution

SOQL metrics can help identify:

🗄️ Database and DML Activity

Database execution data can provide evidence about:

📄 Visualforce Activity

Visualforce information can help analyze:

💡 Custom Events

GermainUX can collect applicable custom diagnostic events present in Salesforce Debug Logs.

Use custom events to expose application-specific details not available through standard log records.

📊 View Debug Log Data

Open:

GermainUX Workspace → Dashboards → All → Salesforce Logs

The dashboard can include:

Select any metric to drill through to the underlying instances and related evidence.

🏆 Salesforce Debug Log KPIs

See Salesforce Debug Log KPIs.

These KPIs can be used to identify:

🔍 Analyze a Slow or Failed Salesforce Interaction

When browser monitoring and correlation are configured, use this investigation flow:

1. Detect a slow click, error, or failed workflow.

2. Open an affected user instance.

3. Review the user’s Session Replay.

4. Identify the action and transaction time.

5. Review related Debug Log KPIs.

6. Inspect Apex class and trigger execution.

7. Review SOQL and database activity.

8. Check for exceptions.

9. Determine which code, query, or integration contributed to the issue.

10. Track and validate the fix.

This connects the user-visible symptom to the Salesforce execution evidence.

🔎 Configure Exception Categorization

Exception messages often contain changing values such as record IDs, timestamps, or request identifiers.

Configure categorization so technically equivalent exceptions are grouped together.

Useful category dimensions include:

See Configure Apex Exception Monitoring.

🔔 Configure Alerts

Useful alert conditions include:

Avoid alerting on every debug record. Alert on categorized, actionable conditions.

📋 Validate Debug Log Monitoring

After the first scheduled collection:

1. Confirm that all three related components are enabled.

2. Confirm that their most recent executions succeeded.

3. Confirm that the next execution times match the intended schedule.

4. Generate or locate a known Salesforce Debug Log in a controlled environment.

5. Verify that GermainUX collects it.

6. Confirm that expected code-unit, SOQL, database, exception, or Visualforce data appears.

7. Verify the Salesforce organization and environment.

8. Confirm timestamps and transaction details.

9. Test any configured categorization or alert.

10. Confirm that user-session correlation works when configured.

No Debug Logs Appear

If no data is collected:

1. Confirm that Salesforce generated Debug Logs during the selected period.

2. Verify that the correct users or transactions are being logged.

3. Confirm that the Salesforce OAuth connection is active.

4. Confirm that the integration user can access Debug Logs.

5. Check that all three GermainUX Debug Log Monitoring components are enabled.

6. Review their last execution and next scheduled execution.

7. Confirm that the GermainUX Engine is running.

8. Check network connectivity from the Engine to Salesforce.

9. Review Engine logs for authorization, API, parsing, and download errors.

10. Check Salesforce API usage and applicable limits.

11. Verify dashboard organization, environment, and time filters.

12. Confirm that the collection interval is short enough for the source logs to remain available.

❓ Some Transactions Are Missing

Salesforce does not necessarily produce Debug Logs for every transaction automatically.

If some transactions are missing:

✂️ Debug Logs Are Truncated or Incomplete

Salesforce may limit the size, volume, retention, or detail of Debug Logs.

If a log lacks required evidence:

⚙️ Performance, Volume, and Retention

Debug logging can generate significant data and may affect Salesforce limits and GermainUX storage.

For production use:

🔒 Security and Privacy

Debug Logs can contain sensitive information, including:

Before production enablement:

🔗 Related Documentation

ℹ️ Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Salesforce CRM environment.

Contact GermainUX Support.