Re: [WebDNA] WebDNA Health Monitor

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111502
interpreted = N
texte = This is a multi-part message in MIME format. --------------040600080803070103020900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit very nice. jym On 8/6/2014 5:25 PM, Stuart Tremain wrote: > That looks really great Dan !! > > After your question about error logs recently I got to thinking that > there must be a better way rather than having to look at each > directory and you have solved it !! > > Adding things to the error template such as USERNAME & BROWSERNAME > becomes possible allowing even better trouble shooting possibilities. > > The idea of a webdna restart would be good too. I did have a look at > doing that on a Windows server some time ago but ran into problems and > dropped the idea, I have not investigated it on Linux since. > > And being able to click through to the error would just about finish > it off. > > Nice job :) > > > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 7 Aug 2014, at 5:51 am, Dan Strong > wrote: > >> I guess I should specify intended upgrades as I see it right now: >> >> 1) Upgrade all tabular data to datatables for sorting, exporting as >> csv, etc. >> 2) Add alternate visualizations such as pie charts, etc. >> 3) Add email notifications upon user-defined threshholds >> 4) Create a main dashboard page which shows snapshot of WebDNA >> "health" at a glance (i.e "this page has suddenly started throwing >> errors, this error is becoming prevalent, this IP is generating the >> most errors, etc.), as well as any other useful things like a >> "restart webdna" button, etc. >> >> >> >> -Dan Strong >> http://DanStrong.com >> >> >> On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong > > wrote: >> >> https://danstrong.com/webdna-health-monitor/ >> >> First draft, proof-of-concept, "plugin" for WebDNA for use in >> monitoring/visualizing ErrorLog.txt files site-wide and/or >> server-wide. >> >> Probably not useful for small sites, but for larger sites and/or >> shared servers (where I intend to use it), this will be great to >> suss out issues hopefully a bit faster (for me anyhow) than >> manually debugging like I do now. >> >> If there is interest, I'd like to either crowdsource some funding >> for it and/or license it in some way. >> >> If not, then I'll keep it for myself, but thought I'd share and >> gauge interest. >> >> -Dan Strong >> http://DanStrong.com >> >> >> --------------------------------------------------------- This >> message is sent to you because you are subscribed to the mailing list >> . To unsubscribe, E-mail to: archives: >> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >> support@webdna.us > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Jym Duane - CTO - Purpose Media Creating Your Success Story Marketing : Television - Internet -Print Phone: (877) 443-1323 Email: jym@purposemedia.com Web: www.purposemedia.com Oregon - www.GuideToOregon.com PO Box 1725, Jacksonville, OR 97530 California - www.OrangeCounty.net PO Box 2025, Capistrano Beach, CA 92624 --------------040600080803070103020900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit very nice.
jym

On 8/6/2014 5:25 PM, Stuart Tremain wrote:
That looks really great Dan !!

After your question about error logs recently I got to thinking that there must be a better way rather than having to look at each directory and you have solved it !!

Adding things to the error template such as USERNAME & BROWSERNAME becomes possible allowing even better trouble shooting possibilities.

The idea of a webdna restart would be good too. I did have a look at doing that on a Windows server some time ago but ran into problems and dropped the idea, I have not investigated it on Linux since.

And being able to click through to the error would just about finish it off.

Nice job :)



Regards

Stuart Tremain
IDFK Web Developments
AUSTRALIA




On 7 Aug 2014, at 5:51 am, Dan Strong <dan@danstrong.com> wrote:

I guess I should specify intended upgrades as I see it right now:

1) Upgrade all tabular data to datatables for sorting, exporting as csv, etc.
2) Add alternate visualizations such as pie charts, etc.
3) Add email notifications upon user-defined threshholds
4) Create a main dashboard page which shows snapshot of WebDNA "health" at a glance (i.e "this page has suddenly started throwing errors, this error is becoming prevalent, this IP is generating the most errors, etc.), as well as any other useful things like a "restart webdna" button, etc.





On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong <dan@danstrong.com> wrote:

First draft, proof-of-concept, "plugin" for WebDNA for use in monitoring/visualizing ErrorLog.txt files site-wide and/or server-wide.

Probably not useful for small sites, but for larger sites and/or shared servers (where I intend to use it), this will be great to suss out issues hopefully a bit faster (for me anyhow) than manually debugging like I do now.

If there is interest, I'd like to either crowdsource some funding for it and/or license it in some way.

If not, then I'll keep it for myself, but thought I'd share and gauge interest.


--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 
-- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323   Email: jym@purposemedia.com   Web: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624
--------------040600080803070103020900-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
  2. Re: [WebDNA] WebDNA Health Monitor (Donovan Brooke 2014)
  3. Re: [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
  4. Re: [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
  5. Re: [WebDNA] WebDNA Health Monitor (Tom Duke 2014)
  6. Re: [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
  7. Re: [WebDNA] WebDNA Health Monitor (Stephen Reiss 2014)
  8. Re: [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
  9. Re: [WebDNA] WebDNA Health Monitor (Tom Duke 2014)
  10. Re: [WebDNA] WebDNA Health Monitor (Jym Duane 2014)
  11. Re: [WebDNA] WebDNA Health Monitor (Stuart Tremain 2014)
  12. [WebDNA] WebDNA Health Monitor (Dan Strong 2014)
This is a multi-part message in MIME format. --------------040600080803070103020900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit very nice. jym On 8/6/2014 5:25 PM, Stuart Tremain wrote: > That looks really great Dan !! > > After your question about error logs recently I got to thinking that > there must be a better way rather than having to look at each > directory and you have solved it !! > > Adding things to the error template such as USERNAME & BROWSERNAME > becomes possible allowing even better trouble shooting possibilities. > > The idea of a webdna restart would be good too. I did have a look at > doing that on a Windows server some time ago but ran into problems and > dropped the idea, I have not investigated it on Linux since. > > And being able to click through to the error would just about finish > it off. > > Nice job :) > > > > Regards > > Stuart Tremain > IDFK Web Developments > AUSTRALIA > webdna@idfk.com.au > > > > > On 7 Aug 2014, at 5:51 am, Dan Strong > wrote: > >> I guess I should specify intended upgrades as I see it right now: >> >> 1) Upgrade all tabular data to datatables for sorting, exporting as >> csv, etc. >> 2) Add alternate visualizations such as pie charts, etc. >> 3) Add email notifications upon user-defined threshholds >> 4) Create a main dashboard page which shows snapshot of WebDNA >> "health" at a glance (i.e "this page has suddenly started throwing >> errors, this error is becoming prevalent, this IP is generating the >> most errors, etc.), as well as any other useful things like a >> "restart webdna" button, etc. >> >> >> >> -Dan Strong >> http://DanStrong.com >> >> >> On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong > > wrote: >> >> https://danstrong.com/webdna-health-monitor/ >> >> First draft, proof-of-concept, "plugin" for WebDNA for use in >> monitoring/visualizing ErrorLog.txt files site-wide and/or >> server-wide. >> >> Probably not useful for small sites, but for larger sites and/or >> shared servers (where I intend to use it), this will be great to >> suss out issues hopefully a bit faster (for me anyhow) than >> manually debugging like I do now. >> >> If there is interest, I'd like to either crowdsource some funding >> for it and/or license it in some way. >> >> If not, then I'll keep it for myself, but thought I'd share and >> gauge interest. >> >> -Dan Strong >> http://DanStrong.com >> >> >> --------------------------------------------------------- This >> message is sent to you because you are subscribed to the mailing list >> . To unsubscribe, E-mail to: archives: >> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >> support@webdna.us > > --------------------------------------------------------- This message > is sent to you because you are subscribed to the mailing list . To > unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us -- Jym Duane - CTO - Purpose Media Creating Your Success Story Marketing : Television - Internet -Print Phone: (877) 443-1323 Email: jym@purposemedia.com Web: www.purposemedia.com Oregon - www.GuideToOregon.com PO Box 1725, Jacksonville, OR 97530 California - www.OrangeCounty.net PO Box 2025, Capistrano Beach, CA 92624 --------------040600080803070103020900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit very nice.
jym

On 8/6/2014 5:25 PM, Stuart Tremain wrote:
That looks really great Dan !!

After your question about error logs recently I got to thinking that there must be a better way rather than having to look at each directory and you have solved it !!

Adding things to the error template such as USERNAME & BROWSERNAME becomes possible allowing even better trouble shooting possibilities.

The idea of a webdna restart would be good too. I did have a look at doing that on a Windows server some time ago but ran into problems and dropped the idea, I have not investigated it on Linux since.

And being able to click through to the error would just about finish it off.

Nice job :)



Regards

Stuart Tremain
IDFK Web Developments
AUSTRALIA




On 7 Aug 2014, at 5:51 am, Dan Strong <dan@danstrong.com> wrote:

I guess I should specify intended upgrades as I see it right now:

1) Upgrade all tabular data to datatables for sorting, exporting as csv, etc.
2) Add alternate visualizations such as pie charts, etc.
3) Add email notifications upon user-defined threshholds
4) Create a main dashboard page which shows snapshot of WebDNA "health" at a glance (i.e "this page has suddenly started throwing errors, this error is becoming prevalent, this IP is generating the most errors, etc.), as well as any other useful things like a "restart webdna" button, etc.





On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong <dan@danstrong.com> wrote:

First draft, proof-of-concept, "plugin" for WebDNA for use in monitoring/visualizing ErrorLog.txt files site-wide and/or server-wide.

Probably not useful for small sites, but for larger sites and/or shared servers (where I intend to use it), this will be great to suss out issues hopefully a bit faster (for me anyhow) than manually debugging like I do now.

If there is interest, I'd like to either crowdsource some funding for it and/or license it in some way.

If not, then I'll keep it for myself, but thought I'd share and gauge interest.


--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us 
-- Jym Duane - CTO - Purpose MediaCreating Your Success StoryMarketing : Television - Internet -PrintPhone: (877) 443-1323   Email: jym@purposemedia.com   Web: www.purposemedia.comOregon - www.GuideToOregon.comPO Box 1725,  Jacksonville, OR 97530California - www.OrangeCounty.netPO Box 2025,  Capistrano Beach, CA 92624
--------------040600080803070103020900-- Jym Duane

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Disappearing Databases (2000) WebCatalog2 Feature Feedback (1996) retain raw [cart] submitted value (2004) [WebDNA] writing pdfs on the fly (Avery labels #5160) (2010) Associative lookup style? + bit more (1997) (ot) sitemap generator (1998) Table Loop Hoops (2000) [WebDNA] [OT] iTools FTP question (2010) PhotoMill -> PhotoMaster (1997) Not really WebCat (1997) WebCatalog can't find database (1997) Page Hanging (2006) OT - How to pay commissions to non US affiliates? (2000) WebCat2 several catalogs? (1997) Founditems (1998) how many users (2000) problems with 2 tags shakur (1997) Google does it... can WebDNA? Showing only the section with (2003) Using Plug-In while running 1.6.1 (1997) Server problem? (1998)