Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

(info) See the Licensing page for all licensing info

Why a Plan is Fully Consumed

JEMHC Plan usage is not unlimited please see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/163164185/Licensing#Why-isn%27t-unlimited-usage-part-of-the-subscription-fee%3F . Exceeding your Plans Capacity is due to the following:

  • Exceeded Message Count limits

  • Exceeded Data Volume limits

Your limits can be found via Licensing page above based on your plan. You current plan can be found please see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3743416325/Capacity+Plan+Fully+Consumed#Checking-your-usage.

Capacity Plans

How/When Capacity Plans are allocated

During Evaluation

New evaluations are put onto the limited capacity Starter evaluation plan to stop excessive erroneous email processing while you are configuring the app.  Once normal email processing has been shown, contact our sales team to get a higher capacity plan.  

You are notified of usage once 80% (data or messages) is consumed.  See JEMHC > Licensing > System Notifications to change this threshold and who is notified more information found on this page: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3743416325/Capacity+Plan+Fully+Consumed#Alert-notifications-based-on-Capacity-levels.

Once Active

Plan allocations are reset at the beginning of each month. This should be based on your active users at that time.

How we calculate usage

Message Count

This can calculated from the two sources

Message In: The number of Email messages that JEMHC processes including all messages polled from the Mail Server configured in JEMHC Configuration > Messaging > Message Sources.

Message Out: The number of Outbound Email Notifications JEMHC sends. This can be from a number of sources:

  • Issue Events

  • JEMHC Post Functions

  • JEMHC Adhoc Notifications

  • Maintenance Notifications

Data Volume

This is related to the size of the aforementioned Message In and Message Out Emails and can be affected by the:

  • The size of an Email excluding attachments

  • Attachments included on the email

Understanding your usage

Standard mail in/out

  • Successful Inbound Messages processed by JEMHC

  • Outbound Notifications sent by JEMHC created in the normal traffic flow i.e. not maintenance traffic.

Maintenance

  • Inbound messages polled from the Inbound Mail Connection that encounter problems during processing

  • Outbound messages JEMH Cloud creates for Maintenance Notifications

  • System Notifications

Identifying causes of maintenance traffic

Please see on this page: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3743416325/Capacity+Plan+Fully+Consumed#Identifying-maintenance-traffic-through-JEMHC-Auditing

Usage Monitoring

Checking your usage

Please navigate to the usage page as found via JEMHC Configuration > Licensing > Usage a further breakdown on this page can be found here: Usage

Alert notifications based on Capacity levels

Recipients you list in the System Notifications found via Licensing > System Notifications will be notified via email about your instances usage.

You can set a % alert level such that the users/addressed configured are notified when the alert level is reached. Example below:

Identifying maintenance traffic through JEMHC Auditing

Sources of Maintenance traffic can be found in Auditing via JEMHC Configuration > Auditing which can then be further refined in Inbound Messages and Outbound Messages then set the Usage Filter to Maintenance In as shown below:

Once Usage is selected if you have any Maintenance traffic (provided that the auditing hasn’t been cleared), a list of maintenance only table items Inbound Messages example below:

Increasing your Capacity

During Evaluation

Its free up to production levels.

Once Active, or if you consume production capacity

Data Packs

Temporarily boost your capacity and are used only when plan capacity exceeded please see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/163164185/Licensing#Data-Packs.

Plan Upgrades

Recommended over Data Packs in cases where monthly limits are being frequently reached please see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/163164185/Licensing#Plan-upgrades

Purchasing

Additional capacity is typically allocated on payment only.

DataPacks

Data Packs are available from https://thepluginpeople.e-junkie.com/product/JEMHCDP/JEMHCloud-Data-Pack with a PayPal account. We can provide card only checkout links on request. If your host url is specified on the form during checking (e.g. nnnn.atlassian.net) the DataPack will be automatically allocated, if not, we can manually apply, in UK office hours.

Quotes will require:

  • your company name and office address including VAT# for GB/EU customers

  • your Atlassian host url: nnnn.atlassian.net

  • your required DataPack size as per Licensing page.

Invoices are issued for all payments received, a requirement of UK HMRC.

Plan Upgrades

Plan Upgrades are a 12 month term in advance non-refundable purchase. We do not recommend them until you have sufficient usage history.

We can issue quotes/invoices for this through our support portal : https://thepluginpeople.atlassian.net/servicedesk/customer/portal/1 (learn more about Getting support) or by email through sales@thepluginpeople.com. In order to issue quotes we will need:

  • your company name and office address including VAT# for GB/EU customers

  • your Atlassian host url: nnnn.atlassian.net

  • your required target Capacity Plan

  • No labels