In Setting up your Apps Script Environment for Dogger, I showed how you could set up a mini environment wrapper so you could always use the same back end environment and serve up logging data to external, non apps script clients.
It is possible to use the cDogger library directly instead, which avoids having to set up your own library, but it also needs a little more set up in your script you want to log from.
The steps are
In these examples I'll show how to get a sheet handler, a parse.com , and a mongolab handler directly, but you can substitute for any other driver if you prefer.
The libraries needed for parse.mongolab and sheet demos are
you can get info about them below
For parse.com (see DriverParse for more info)
for Sheets (see DriverSheet for more info)
For MongoLab (see Driver MongoLab for more info)
Get Dogger handlers
Here's the simulated workload that'll be doing the logging
and in the parse.com dashboard
And in the mongolab dashboard
Of course it looks better and more consistent if you use the Multi user apps script logger polymer client, but for that you need to have set up yourDoggerServer as described in Setting up your Apps Script Environment for Dogger
For more on this see Multi user apps script logger, Polymer and Database abstraction with google apps script
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Polymer > Multi user apps script logger >