Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
82 changes: 67 additions & 15 deletions modules/ROOT/pages/start-open-output-panel.adoc
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
= Opening the Output Panel
= Viewing Logs and Errors
:page-deployment-options: cloud-ide, desktop-ide
:page-aliases: configure-mulesoft-environment.adoc

Expand All @@ -7,29 +7,81 @@ include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"]
//LOGO (web, desktop, or both)
// include::partial$acb-ide-logos.adoc[tags="both-ides"]

Configuring the output panel to display logs for the Anypoint Code Builder extensions enables you to view the status of activity in the IDE.
Anypoint Code Builder provides two ways to view logs and errors:

* *ACB Logs*: A centralized view that consolidates warnings and errors from all Anypoint Code Builder extensions into a single, filterable panel. Use this view to quickly identify and troubleshoot issues.
* *Output panel*: Displays detailed, raw logs from individual extension channels. Use this view for in-depth investigation when you need complete log output.

== Before You Begin
[[acb-logs]]
== View Errors and Warnings in ACB Logs

include::partial$acb-prereq-login.adoc[]
The *ACB Logs* panel provides a centralized view of all warnings and errors generated by Anypoint Code Builder. This panel consolidates logs from multiple extension channels into a single, searchable interface.

== Configure the Default Output Panel
To open the ACB Logs panel, click the *ACB Logs* tab in the Panel area, alongside other tabs such as Output, Problems, and Debug Console.
// TODO: Add screenshot of ACB Logs tab

You must configure your output panel to display information from the Anypoint Code Builder extensions:
The panel displays log entries in a table with the following columns:

. Open the output panel:
+
** Use the keyboard shortcuts:
[cols="1,2"]
|===
| Column | Description

| *Date*
| Timestamp of when the log entry was recorded.

| *Log Level*
| Severity of the log entry (Error, Warning, Info).

| *Extension*
| The Anypoint Code Builder extension that generated the log.

| *Message*
| The detailed text of the log entry.
|===

=== Filter and Search Logs

Use filters to narrow down the log entries displayed:

* *Level*: Filter by log severity (Error, Warning, Info).
* *Source*: Filter by the extension that generated the log.
* *Date*: Filter by date range.

To search for specific text within the logs, use the search bar.

=== Expand Log Details

Click a log entry to expand it and view additional details, such as the full stack trace.

=== Clear Logs

To remove all log entries from the panel, click *Clear logs*.

=== Export Logs for Troubleshooting

When you export troubleshooting information using the `MuleSoft: Export Troubleshooting Information` command, the ACB Logs are automatically included in the exported file. For more information, see xref:troubleshooting.adoc#export-troubleshooting-info[Export Troubleshooting Information].

[[output-panel]]
== View Detailed Logs in the Output Panel

For in-depth investigation, use the Output panel to view raw, detailed logs from individual Anypoint Code Builder extension channels.

To open and configure the Output panel:

. Open the Output panel using one of these methods:
+
*** Mac: Cmd+Shift+u
*** Windows: Ctrl+Shift+u
** In the desktop IDE, select *View* > *Output*.
** In the cloud IDE, click the image:icon-menu.png["",18,18] (menu) icon, and select *View* > *Output*:
* Use the keyboard shortcuts: Cmd+Shift+u (Mac) or Ctrl+Shift+u (Windows)
* In the desktop IDE, select *View* > *Output*.
* In the cloud IDE, click the image:icon-menu.png["",18,18] (menu) icon, and select *View* > *Output*:
+
image::select-specific-output-view.png["The View and Output options are displayed in a list of menu choices"]
. In the output panel, select *Mule DX Server* from the dropdown list:
. In the Output panel, select an output channel from the dropdown list:
+
image::select-mule-dx-server.png["A menu bar with the Mule DX Server tab open"]
+
Common channels include:
+
* *Mule DX Server*: General logs from the Anypoint Code Builder backend.
* *Mule DX Server: Scaffolding*: Logs specific to project scaffolding operations.

Anypoint Code Builder now displays information related to logs produced by the extensions. To see scaffolding errors only, select *Mule DX Server: Scaffolding* from the list.
The Output panel displays the complete log stream for the selected channel, which is useful for debugging complex issues that require full context.
7 changes: 3 additions & 4 deletions modules/ROOT/pages/troubleshooting.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,10 @@ For tasks that support the troubleshooting process, see:
[[check-logs]]
== Check for Problems and Issues

When you don't know how to resolve an issue, the first step is to check for and review problems, console output, and logs.
When you don't know how to resolve an issue, the first step is to check for and review problems, console output, and logs. Error messages and logs list underlying issues that can help you understand what went wrong and what requires attention.

The *Output* panel provides build details and access to logs. The *Problems* tab lists warnings and error messages. Error messages and logs list underlying issues that can help you understand what went wrong and what requires attention.

* To view project logs from the *Output* panel, see xref:start-discover-ui.adoc#compare-project-uis-in-the-ide[Compare Project UIs in the IDE].
* To view centralized errors and warnings, open the *ACB Logs* panel. See xref:start-open-output-panel.adoc#acb-logs[View Errors and Warnings in ACB Logs].
* To view detailed logs for in-depth investigation, use the *Output* panel. See xref:start-open-output-panel.adoc#output-panel[View Detailed Logs in the Output Panel].
* To view problems, open the *Problems* tab by pressing Cmd+Shift+m (Mac) or Ctrl+Shift+m (Windows).

[[export-troubleshooting-info]]
Expand Down