Email configuration for errors

[cole]

@slodge

In our case, we don't actually want the email for content either

In that case, it sounds like EmailProvider = None may be what you want! Have you used that already? It prints the administrative messages to log rather than emailing.

@slodge

we'd love to see the logging structures changed to make them more Splunk parsable

Yes! I remembered this and is part of why I asked That is actually on our short list of things we aim to improve in the next few months, so hopefully we will have some nice features coming your way there! This is a great example with respect to the keys associated with logs, though, so I will make a note to be sure we test this use case!

Have you seen this post about a log forwarder? I thought you might be interested in this Unfortunately, I have been behind on everything and not able to try this out yet

Announcing a way to forward logs from RSConnect to Elasticsearch, Splunk, and many others

One of the things we've struggled with in using RSConnect is making Shiny app logs more useful. You can view logs for individual sessions in the browser (if you know what you're looking for), but there's no searching or aggregation of any kind. This is frustrating, because log aggregation is largely a solved problem -- there are many commercial and open-source options available, none of which RSConnect currently supports. To solve this for our own uses, I wrote an RSConnect-specific plugin for Fluent Bit. It works by watching for new logs written to the filesystem and querying the Connect API for additional metadata to link these logs back to specific applications. Fluent Bit can then be us…