On Mon, Oct 23, 2017 at 10:17 AM, Joshua Fox <[email protected]> wrote: > > But it seems strange to have to write any code. It seems that > Splunk/Sumo/ELK should have some builtin log ingestors requiring nothing > more than a configuration in GCP or a provided log4j Handler. >
I agree! I don't actually know these vendors products very well, but I suspect they must have something? I do have experience writing things that consume the Stackdriver logging export (I absolutely love the BigQuery export, and have experimented with the PubSub log export, although we didn't end up using it "in production"). The reason I suggest doing this, which could be more work, is that we have found that a number of the other stackdriver logs have been useful. If you want all your logs in one place, and you want the HTTP load balancer logs, container engine logs, or other things, then you may end up needing to figure this out at some point anyway. Good luck! Evan -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CACRPLjj%3D876jWia%2ByZJndqBHgZ0XgzX%3DG_-4xg449Wn-27kZ9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
