Ah yes, that worked great!
was able to generate
```
{"data":{"foo":["a"]},"timestamp":"2019-03-31T11:22:57",
"level":"INFO","name":"log-name"}
```
using
```
(log-message app-logger 'info "" (hasheq 'foo '("a")))
```
On Sunday, March 31, 2019 at 8:43:00 AM UTC-4, Matthew Flatt wrote:
>
> At Sun, 31 Mar 2019 05:13:45 -0700 (PDT), Darren Newton wrote:
> > However, I would like to pass a jsexpr? to the logger [...]
> >
> > As far as I can tell, the log procs only accept strings.
>
> The primitive `log-message` function accepts arbitrary data for the
> logged message after the message string. That data is communicated to
> each log receiver.
>
> The `log-info`, etc., macros currently support only a message string,
> but you can create your own macro if that's helpful. If you know that
> some receiver will exist a `log-level?` test as built into the existing
> macros isn't helpful, and you might just as well call `log-message`
> directly.
>
>
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
