Skip to content

W-20280888-DIAFdeployment-49-dm #3199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dmerlob wants to merge 1 commit into
base: v4.9
Choose a base branch
from
Open

W-20280888-DIAFdeployment-49-dm #3199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
98 changes: 98 additions & 0 deletions modules/ROOT/pages/mule-troubleshooting-plugin.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,7 @@ The Diagnostic Information Analysis File (DIAF) organizes all diagnostic data co
* <<diaf-event-dump>>
* <<diaf-schedulers>>
* <<diaf-cpu-usage>>
* <<diaf-deployments>>

[[diaf-title]]
=== Title
Expand Down Expand Up @@ -378,6 +379,103 @@ This section shows the CPU usage for each thread in the Mule runtime process. Us
| Total CPU time the thread has consumed since the Mule runtime process started, in milliseconds.
|===

[[diaf-deployments]]
=== Deployments

This section shows the status and metadata of all artifacts currently deployed in the Mule runtime instance: applications, domains, policy templates, and policies applied to applications. It also shows undeployed artifacts still present in memory, which can indicate possible leaks.

==== Applications

For each application, the report includes this information:

[cols="1,3", options="header"]
|===
| Field | Description

| Artifact Name
| Name of the application.

| Artifact Type
| `APPLICATION`.

| State
a| Current state of the application:

* `INITIAL`
* `DEPLOYED`
* `STARTED`
* `STOPPED`
* `UNDEPLOYED`
* `FAILED`

| Domain
| Name of the domain the application uses. Shown only if the application uses a non-default domain.

| Policies
| List of policy IDs applied to the application. Shown only if the application has policies.

| Plugins
| List of all plugins available in the application's deployment.

| Time since Last State Update
| Timestamp of the most recent state update, formatted as `yyyy-MM-dd HH:mm:ss`.

| Feature Flags
| List of all enabled feature flags for the application, sorted alphabetically. Shown only for `DEPLOYED`, `STARTED`, or `STOPPED` applications.
|===

==== Domains

For each domain (excluding the default domain), the report includes this information:

[cols="1,3", options="header"]
|===
| Field | Description

| Artifact Name
| Name of the domain.

| Artifact Type
| `DOMAIN`.

| State
a| Current state of the domain:

* `INITIAL`
* `DEPLOYED`
* `STARTED`
* `STOPPED`
* `UNDEPLOYED`
* `FAILED`

| Plugins
| List of all plugins available in the domain's deployment.

| Time since Last State Update
| Timestamp of the most recent state update, formatted as `yyyy-MM-dd HH:mm:ss`.
|===

==== Policy Templates

Policy templates appear as separate top-level entries. Each entry represents a unique policy template used by one or more applications.

[cols="1,3", options="header"]
|===
| Field | Description

| Template Name/ID
| Name or identifier of the policy template.

| Artifact Type
| `POLICY_TEMPLATE`.

| Version
| Version of the policy template.

| Plugins
| List of all plugins available in the policy template.
|===

== Considerations

* DIAF provides investigation hints. Check the logs for complete details.
Expand Down