@flowfuse/flowfuse/forge/postoffice/templates/InstanceResourceMemoryExceeded.js

An open source low-code development platform

module.exports = {
    subject: 'FlowFuse Instance Memory usage exceeded 75%',
    text:
`Hello

Your FlowFuse Instance "{{{ name }}}" in Team "{{{ teamName.text }}}" is using more than 75% of its available memory.

This can occur for a number of reasons including:
- incorrect instance size for your workload
- an issue in your flows or functions holding onto memory
- an issue in a third-party library or node

Possible solutions:
- upgrading to a larger instance type
- try disabling some nodes to see if the problem settles down after a restart
- when polling external services, ensure you are not polling too frequently as this may cause backpressure leading to memory exhaustion
- check your flows for large data structures being held in memory, particularly in context
- check the issue tracker of your contrib nodes

{{#if log.text}}
------------------------------------------------------
Logs:

{{#log.text}}
Timestamp: {{{timestamp}}}
Severity: {{{level}}}
Message: {{{message}}}

{{/log.text}}

Note: Timestamps in this log are in UTC (Coordinated Universal Time).
------------------------------------------------------
{{/if}}

You can access the instance and its logs here:

{{{ url }}}

`,
    html:
`<p>Hello</p>
<p>Your FlowFuse Instance "{{{ name }}}" in Team "{{{ teamName.html }}}" is using more than 75% of its available memory.</p>

<p>
This can occur for a number of reasons including:
<ul>
<li>incorrect instance size for your workload</li>
<li>an issue in your flows holding onto memory</li>
<li>an issue in a third-party library or node</li>
</ul>

Possible solutions:
<ul>
<li>try selecting a larger instance type</li>
<li>try disabling some nodes to see if the problem settles down after a restart</li>
<li>when polling external services, ensure you are not polling too frequently as this may cause backpressure leading to memory exhaustion</li>
<li>check your flows for large data structures being held in memory, particularly in context</li>
<li>check the issue tracker of your contrib nodes</li>
</p>


{{#if log.html}}
<p>
Logs:
<table style="width: 100%; font-size: small; font-family: monospace; white-space: pre;">
    <tr>
        <th style="text-align: left; min-width: 135px;">Timestamp</th>
        <th style="text-align: left; white-space: nowrap;">Severity</th>
        <th style="text-align: left;">Message</th>
    </tr>
    {{#log.html}}
    <tr>
        <td style="vertical-align: text-top;">{{{timestamp}}}</td>
        <td style="vertical-align: text-top;">{{{level}}}</td>
        <td>{{{message}}}</td>
    </tr>
    {{/log.html}}
</table>
<i>Note: Timestamps in this log are in UTC (Coordinated Universal Time).</i>
</p>
{{/if}}

<p>You can access the instance and its logs here</p>
<a href="{{{ url }}}">Instance Logs</a>
`
}