You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{% alert color="info" %}}Premium plans provide multi-AZ fallback, and Premium Plus plans provide multi-region fallback. For more details, see [Additional Resources](#additional-resources), below.{{% /alert %}}
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/monitoring-application-health/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -153,7 +153,7 @@ Database Freeable Memory | |
153
153
Description | Track the amount of freeable memory for the database belonging to the application.
154
154
Example message | Database has 35% freeable memory.
155
155
Warning Threshold | Not used.
156
-
Critical Threshold | Database has 5% freeable memory for XS21, XS20, S, and Strato [cloud resource packs](/developerportal/deploy/mendix-cloud-deploy/#resource-pack). Database has 10% freeable memory for all other cloud resource packs.
156
+
Critical Threshold | Database has 5% freeable memory for XS21 Standard, XS20, S, and Strato [cloud resource packs](/developerportal/deploy/mendix-cloud-deploy/#resource-pack). Database has 10% freeable memory for all other cloud resource packs.
157
157
First actions to take | Inspect the metrics graph **Database memory** for anomalies and correlate those with application behavior. Resolve by identifying and optimizing long-running database queries, or upgrading the cloud resource pack (for example, by ordering more memory).
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/splunk-metrics.md
+5-11Lines changed: 5 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,17 +47,11 @@ To send your runtime information to Splunk Cloud Platform, you need to set it up
47
47
|`SPLUNK_ENABLE_METRICS`| Sends application metrics to Splunk when it's set to `true`. Disabled by default. A metrics index is also required, refer to the [metrics index information](#splunk-metrics-info) below. |`false`|
48
48
|`APM_ENABLE_ACCESS_LOGS`| Sends access logs to Splunk when it's set to `true`. Disabled by default. |`false`|
49
49
50
-
<divid="splunk-metrics-info">
51
-
{{% alert color="info" %}}
52
-
**Splunk supports two types of indexes:**
53
-
54
-
***Event indexes**: These are the default index type and impose minimal structure, allowing them to store any kind of data, including metrics. To ingest logs, you must configure an event index as the default index in your HEC token.
55
-
56
-
***Metrics indexes**: These use a highly structured format designed for high-volume, low-latency metrics data. To ingest metrics, create an index named `mxmetrics` and add it to the list of allowed indexes in your HEC token. For more information, refer to the [Splunk documentation](https://help.splunk.com/en/splunk-cloud-platform/get-data-in/metrics/9.2.2406/introduction-to-metrics/overview-of-metrics).
57
-
58
-
{{% /alert %}}
59
-
</div>
60
-
50
+
<divid="splunk-metrics-info">
51
+
{{% alert color="info" %}}**Splunk supports two types of indexes:** <br/>
52
+
**Event indexes**: These are the default index type and impose minimal structure, allowing them to store any kind of data, including metrics. To ingest logs, you must configure an event index as the default index in your HEC token. <br/>
53
+
**Metrics indexes**: These use a highly structured format designed for high-volume, low-latency metrics data. To ingest metrics, create an index named `mxmetrics` and add it to the list of allowed indexes in your HEC token. For more information, refer to the [Splunk documentation](https://help.splunk.com/en/splunk-cloud-platform/get-data-in/metrics/9.2.2406/introduction-to-metrics/overview-of-metrics).{{% /alert %}}
54
+
</div>
61
55
62
56
5. Return to the **Environments** page for your app and **Deploy** or **Transport** your app into the selected environment.
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mx-azure/mx-azure-support.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,6 +158,10 @@ Node-level OS components receive weekly security patches through Microsoft's Nod
158
158
159
159
These automated upgrade cadences cannot be modified by customers.
160
160
161
+
{{% alert color="info" %}}
162
+
During automated upgrades, application containers may restart. However, built-in redundancy ensures that at least one replica remains available at all times, so no downtime occurs.
The features in the navigation pane can also be accessed via APIs, enabling third-party developers to integrate their own widgets and plugins. For more information, see [API Documentation](/apidocs-mxsdk/apidocs/).
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/overview/marketplace-home-page.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,10 @@ The **Personal** category contains the items described in the following sections
48
48
49
49
Clicking **Drafts** opens the **My Drafts** page, where you can see and manage the drafts for all the Marketplace content you have started.
50
50
51
+
{{% alert color="info" %}}
52
+
Only drafts that have been active over the last 30 days are displayed. Drafts are automatically removed if they have been inactive for more than 30 days.
53
+
{{% /alert %}}
54
+
51
55
You can also find details on how many total drafts you have, which drafts are ready to publish or are awaiting approval, and which drafts have been declined.
52
56
53
57
These are the possible **Status** entries for each item:
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/platform-supported-content/modules/global-inbox.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,12 +63,13 @@ The **Global Inbox** consists of the following components:
63
63
64
64
The Global Inbox operates with the following event flow:
65
65
66
-
1. Publisher App registration: Each publisher application registers with the Global Inbox by publishing a **PublisherAppRegisteredEvent**. This ensures the Global Inbox knows which apps are available to send task events.
66
+
1. Publisher App registration: Each publisher application registers with the Global Inbox by publishing a **PublisherAppRegisteredEvent**. This ensures the Global Inbox knows which apps are available to send task events. As part of this registration, the application's workflow groups are synchronized with the Global Inbox.
67
67
2. Task update and event publication: When a workflow or task is created, updated, or completed in a publisher application that includes the Global Inbox Connector, the connector publishes the following events:
68
68
***WorkflowUpdatedEvent** – triggered when the workflow is updated.
69
69
***UserTaskUpdatedEvent** – triggered when a user task is updated.
70
70
***UserTaskEndedEvent** – triggered when a user task is completed or aborted.
71
71
***UserTaskOutcomeSelectedEvent** – triggered when a user completes a task by selecting an outcome.
72
+
***WorkflowGroupUpdatedEvent** – triggered when a workflow group is updated.
72
73
3. Event consumption: The Global Inbox consumes these events and updates or creates the corresponding task entries in the central task list.
73
74
4. Task visibility and navigation: Tasks become visible in the Global Inbox. Users can click a button to navigate directly to the corresponding task page in the Publisher Application to take action.
74
75
@@ -138,6 +139,5 @@ Any user that can see a task in Publisher Application can see the same task in t
138
139
139
140
## Limitations
140
141
141
-
***Global Inbox** does not support [Workflow Groups](/refguide/workflow-groups/) at the moment. This will be introduced at a later stage.
142
142
***Global Inbox** has limited support for error handling. Any exceptions that occur in a microflow after updating a user task (or other Workflow-related entity) in the same microflow (for example, updating the targeted users or due date) might result in data becoming out of sync. This is a temporary limitation that will be resolved in an upcoming version.
143
-
* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications.
143
+
* Workflows and tasks that are modeled in the same app that includes the Global Inbox module are NOT available in the Global Inbox. The Global Inbox app only consumes and displays workflow instances from other Mendix applications.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments