twisted1919
Administrator
Staff memberHello guys,
As you know, in mailwizz there are a number of command line commands, most popular one is "send-campaigns" one, which can be called from command line to trigger email sending.
Every time there is an issue with delivery, we apply https://kb.mailwizz.com/articles/debug-send-campaigns-command/ which basically will show what mailwizz is doing, but in command line.
Now, this is fine for developers and people that can read a console output and make sense from it, but can we do better, can we make this info available to anyone in a nice dashboard, in realtime without affecting the application performance when sending emails?
We believe we can and in last weeks we fiddled with this idea and the technology we will use in order to make this happen and we'd like to build such dashboard that shows in realtime what is going one with the sending process.
When send-campaigns is running, we have access to all the campaigns sending at that point, to customers these campaigns belong to, to delivery servers used for these campaigns but also to the subscribers which will receive the campaign, so knowing this, what type of stats would you like to see in this dashboard?
We can do things like the number of emails sent per minute, hour, etc.
We can also do a breakdown on the domains the emails went out for, even the numbers of emails a domain got in the last minute/hour etc, then a breakdown for delivery servers and a graph that shows sending in realtime based on speed.
What else?
Note 1: because of the complexity involved and the fact it will need to be maintained in the long run, this will be a separate paid app. People contributing ideas here will get discounts.
Note 2: We want this app to perform extraordinary fast, which means we will store all the info in memory, which means there will be a limit to the quantity of data we will show and that data will be, most likely, removed between restarts.
This also means we can't have historic records(like keep what happened 6 months ago), we don't care. We care about what currently is going on, realtime (of course, almost realtime, but you get the point)
Note 3: We will send your data from mailwizz to this app over the wire, which means we'd like to send as less data as possible to make it travel as fast as possible.
Thank you in advance for any insight.
As you know, in mailwizz there are a number of command line commands, most popular one is "send-campaigns" one, which can be called from command line to trigger email sending.
Every time there is an issue with delivery, we apply https://kb.mailwizz.com/articles/debug-send-campaigns-command/ which basically will show what mailwizz is doing, but in command line.
Now, this is fine for developers and people that can read a console output and make sense from it, but can we do better, can we make this info available to anyone in a nice dashboard, in realtime without affecting the application performance when sending emails?
We believe we can and in last weeks we fiddled with this idea and the technology we will use in order to make this happen and we'd like to build such dashboard that shows in realtime what is going one with the sending process.
When send-campaigns is running, we have access to all the campaigns sending at that point, to customers these campaigns belong to, to delivery servers used for these campaigns but also to the subscribers which will receive the campaign, so knowing this, what type of stats would you like to see in this dashboard?
We can do things like the number of emails sent per minute, hour, etc.
We can also do a breakdown on the domains the emails went out for, even the numbers of emails a domain got in the last minute/hour etc, then a breakdown for delivery servers and a graph that shows sending in realtime based on speed.
What else?
Note 1: because of the complexity involved and the fact it will need to be maintained in the long run, this will be a separate paid app. People contributing ideas here will get discounts.
Note 2: We want this app to perform extraordinary fast, which means we will store all the info in memory, which means there will be a limit to the quantity of data we will show and that data will be, most likely, removed between restarts.
This also means we can't have historic records(like keep what happened 6 months ago), we don't care. We care about what currently is going on, realtime (of course, almost realtime, but you get the point)
Note 3: We will send your data from mailwizz to this app over the wire, which means we'd like to send as less data as possible to make it travel as fast as possible.
Thank you in advance for any insight.