Because the Analysis page covers the aggregated data of the current Inbound Messages and Outbound Messages tabs, purging these datasets will effect the Analysis tab. Additionally, the data retention period for both inbound and outbound messages will also impact the aggregated analysis data.
Each inbound message JEMHC polls, or outbound message JEMHC sends, will count towards your current plan (See Usage for further information). Due to this, the Analysis of both inbound and outbound are treated as a combined total. If you wish to analyze based on inbound or outbound, you can use https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3774218241/Analysis#Group-By and filter by Direction.
Example scenario
The following scenario covers a full cycle of the following:
- Message handler polls a message (inbound)
- Message is processed, causing Jira issue event to fire
- Webhook from Jira is processed, causing notification (outbound)
Step 1 - No data usage
To begin, when inbound and outbound contain no message audit records:
 |
 |
The Analysis tab will appear empty by default.
 |
Step 2 - Inbound Message polling
When JEMHC mail handler polls the mailbox, the read mails will be shown in Inbound Messages. Each mail is shown in it’s own audit entry row, and contains data about the processing of that mail, such as (but not limited to):
Related Jira Project/Issue
Mail metadata (Subject/Senders)
Mail size
 |
The outcome of this mail resulted in a `No Catch Email Match` outcome, which results in a forward mail (Set using https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3708944393/Profile+Configuration#Forward-User-Email-Addresses when inbound mail processing failures occur).
After this, the Analysis tab will include the new inbound audit data in the aggregated total.
 |
Step 3 - Outbound Messaging
When Webhook events are processed to notify recipients, or inbound issues cause forward email notifications, these mails are shown in the Outbound Messages tab.
If we use our existing inbound mail example that resulted in a Forward mail, we can see the Foward mail notification has been sent:
 |
Now, looking at the Analysis tab, we see the total data has increased:
 |
This matches the total data usage for both inbound and outbound messages combined.
If we use the Group By filter, we can confirm this by seeing the following values for both inbound and outbound directions:
 |
This briefly covers how the Analysis tab aggregates both inbound and outbound message data. If you wish to understand how to filter the Analysis data, please seeAnalysis and https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/3774218241/Analysis#Group-By.