Logs Panel

The Logs panel is a simple, but a very helpful tool that allows you to immediately get all the new logs from Salesforce within the IDE and to open them in-place without switching to any other application.

You can call the Logs panel from the Main Menu: View ⇒ Pads ⇒ Logs.


Open the Logs panel from the Main Menu


Downloading logs

At first, in the opened panel you will only see a list of all the projects in the current solution with checkboxes next to their names.

To get the logs for a project (or projects) you should tick the corresponding checkbox and press the Download Logs button at the top left corner of the panel. Once you do this, The Welkin Suite will start polling each project’s organization (that you’ve selected) for the new logs and will display them in the list, when they appear. Usually, it won’t take more than 5-10 seconds to get the new logs in the IDE, but in cases of heavy logs activity (e.g. hundreds of logs during some seconds), it may require a bit more time to update the list.

While the button is pressed, The Welkin Suite sends requests to Salesforce for the new logs every 10 seconds.

To stop the polling process for new logs you should press the Download Logs button once more and The Welkin Suite will stop downloading any new logs while the old logs will still be visible on the list.


Logs Panel


Logs description

In this panel, you can find all needed information about the logs:

  • Application — the name of the application that triggered the log:
    • for API clients, this value is the client ID,
    • for browser clients, this value is Browser,
  • Operation — the name of the operation that triggered the log,
  • Start Time — start time of the transaction with seconds,
  • Length — length of the log in bytes,
  • Duration — duration of the transaction in milliseconds,
  • Status — the status of the transaction. This value is either Success or the text of an unhandled Apex exception,
  • Request — the request type:
    • API — the request came from an API;
    • Application — the request came from the Salesforce user interface,
  • Location — the location of the origin of the log:
    • Monitoring — generated as part of the debug log monitoring and visible to all administrators. These types of logs are maintained until the user or the system overwrites them,
    • SystemLog — generated as part of the system log monitoring and visible only to you. These types of logs are only maintained for 60 minutes or until the user clears them,
    • Preserved — a system log that is maintained longer than 60 minutes. Used for internal support,
  • User — information about the author of the logged action.

Additional actions with logs

If you find a log that you want to view in a text format, double-click it in the Logs panel, and it will be opened in the editor via Debug Logs Viewer. Please note that the logs content is downloaded once you open them, so the bigger the log the more time it will require being opened. You can find all log files that you downloaded in the Logs folder, which is placed in your project's folder.

In addition, you can easily debug any existing log file in the Debug mode of The Welkin Suite.

Also, you can set Debug log levels directly in the IDE without switching to Salesforce settings. To change the log level select any file in the Logs panel, click on the button Configure Debug Log Levels and select a necessary level for the type of log that you need. You can set the required log levels for the Apex Retrospective Debugging process in one click. To do so, click the Set Retrospective Debug Log Levels option. To apply the setting click the OK button.


Configure Debug Log Levels window


This option helps you to save your time and concentrate on developing without switching between other applications or services.

The last option gives you the ability to switch to your local time in the Logs panel.


Local time for logs


The start time for your log files changes automatically according to the selected status of this option. You can easy back to the UTC time by clicking on it again at any time. The following changes you can see directly in the Debug Log viewer.

In this section:

This also may be useful:

Last modified: 2017/05/30 14:39

footer image