Re: [WebDNA] WebDNA Health Monitor

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111501
interpreted = N
texte = --Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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: >=20 > 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. >=20 >=20 >=20 > -Dan Strong > http://DanStrong.com >=20 >=20 > On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong wrote: > https://danstrong.com/webdna-health-monitor/ >=20 > First draft, proof-of-concept, "plugin" for WebDNA for use in = monitoring/visualizing ErrorLog.txt files site-wide and/or server-wide. >=20 > 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. >=20 > If there is interest, I'd like to either crowdsource some funding for = it and/or license it in some way. >=20 > If not, then I'll keep it for myself, but thought I'd share and gauge = interest. >=20 > -Dan Strong > http://DanStrong.com >=20 > --------------------------------------------------------- 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 --Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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:
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.


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

= --Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B-- 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)
--Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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: >=20 > 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. >=20 >=20 >=20 > -Dan Strong > http://DanStrong.com >=20 >=20 > On Wed, Aug 6, 2014 at 12:35 PM, Dan Strong wrote: > https://danstrong.com/webdna-health-monitor/ >=20 > First draft, proof-of-concept, "plugin" for WebDNA for use in = monitoring/visualizing ErrorLog.txt files site-wide and/or server-wide. >=20 > 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. >=20 > If there is interest, I'd like to either crowdsource some funding for = it and/or license it in some way. >=20 > If not, then I'll keep it for myself, but thought I'd share and gauge = interest. >=20 > -Dan Strong > http://DanStrong.com >=20 > --------------------------------------------------------- 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 --Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii 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:
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.


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

= --Apple-Mail=_AE8B271A-8A7A-49FC-879E-066B376E1B9B-- Stuart Tremain

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:

WebCatalog can't find database (1997) Attention all list readers (1997) WebDNA Solutions ... sorry! (1997) WebCat2: Master Counter snippet (1997) modified storedbuilder (was: show me your store) (2003) Sort of a Dilema! (1998) EIMS Problems (1997) showif and cart (1997) turning every 5th line red (1998) Separate server for jpg/gif files (1998) RE: Missing contexts on NT (1997) WebCatalog can't find database (1997) [WebDNA] Grep help - catch all URLs (2010) Searching multiple fields (1997) Major problem SOLVED! (1999) Special characters & [sendmail] (1998) Mozilla/4. and Browser Info.txt (1997) [WriteFile] problems (1997) RE: creating writefile data from a nested search (1997) Orders.db problem (2003)