how to trace network logs +salesforce

Traceroute using Network Utility

1. Open Network Utility.app, located in the Utilities folder.
2. Click Traceroute.
3. Enter login. salesforce.com the first time and yourinstance.salesforce.com the second time.
4. Click Trace.
5. Copy and paste the results into a text editor or reply email.

Full Answer

Why are there network logs in my Salesforce logs?

If you have an ongoing case with your internal network team or Salesforce support, these logs will help to identify the source of a potential network issue. Salesforce transmits packets of various sizes when communicating with your machine.

Why is Salesforce asking me to run a traceroute?

Salesforce will ask you to run a traceroute and share the logs with us when troubleshooting performance issues where the network is suspected to be the cause.

How to deal with network issues in Salesforce?

In addition to Salesforce activity, we will also occasionally post general status messages if we are engaged with an ISP to work through any networking issues. 2. Ask your colleagues. Check if your entire team is also experiencing the same level of performance and whether they have found any ways to mitigate it.

What are the debug logs in Salesforce apex?

The debug logs in Salesforce will get generated when the user based trace logs are active, when the Apex tests are run, when a code is executed and when API calls are made. This should include the debugging parameters as well.

Collect a network trace with Fiddler

Fiddler is a powerful tool for collecting HTTP traces. Install it from telerik.com/fiddler, launch it, and then run your app and reproduce the issue. Fiddler is available for Windows, macOS, and Linux.

Collect a network trace in the browser (Browser-based apps only)

Most browser Developer Tools have a "Network" tab that allows you to capture network activity between the browser and the server.

Debug Logs in Salesforce

Debug logs in Salesforce are the best source of information to uncover what is actually taking place on the platform. These are the best option to track back events that might have happened in the Org. Specifically, if we are doing root cause analysis for a particular problem, we can trace out the root cause from the debug logs.

Use cases of debug logs

Debug logs can be used by the developers for tracing any errors that might have occurred on the application. For example, the application is not stable or it is impacting the performance of the other components, or it might stop responding after a certain user input because exceptions are not defined.

Limitations of the Debug Log

Debug logs are undoubtedly helpful for monitoring the platform, but it has certain limitations as well.

Setting Up the debug logging

Debug logging can be activated for Apex classes & triggers and normal users. For this, trace flags need to be configured along with the debug levels, in the Developer Console. Each trace flag will contain the following:

Debug Log Details

Analyzing the debug log is an art, and might need prior experience as a developer or administrator. However, if you are aware of the components of the debug logs, at least you will be aware, where to look for what. The components of the debug log are mentioned below:

Debug Log Categories

Each debug level includes a debug log level for each of the following log categories. The amount of information logged for each category depends on the log level.

Debug Log Levels

Each debug level includes one of the following log levels for each log category. The levels are listed from lowest to highest. Specific events are logged based on the combination of category and levels. Most events start being logged at the INFO level.

Debug Event Types

The following is an example of what is written to the debug log. The event is USER_DEBUG. The format is timestamp | event identifier:

How long does a trace flag last?

The date and time that the trace flag expires. ExpirationDate must be less than 24 hours after StartDate. Only one trace flag per traced entity can be active at a time. If StartDate is null, the current time is used, and the ExpirationDate must be less than 24 hours from the current time. This field is required.

Can you see system logs?

System logs are visible only to you. Use this scope for class-level filtering. If there are both user and entity-level flags, the user flags take precedence until a method from a class with an entity trace flag is entered. When the method returns, the user trace flags are restored.