search

EngineerBetter / k8s-is-not-a-paas

Creative Commons Attribution Share Alike 4.0 International
52 stars 8 forks source link

Proposed Change: Log Aggregation #1

Open mxr-mwaters opened 4 years ago

mxr-mwaters commented 4 years ago

We have been using CF for many years now, and I propose that "Log Aggregation" be changed to "bring your own/configure".

We have had to do a lot of work to get CF logs centralized, parsed, searchable etc. Differences and different ways to get logs from the foundation vs logs from deployed applications have also been challenging to get configured correctly. Also, at least for us, none of these really were "configure", most of it was "bring your own".

If we have been wrong (with vendors telling we were doing best practices) I would love to understand what facilities now exist that perhaps have solved these issues and it truly is provided out of the box.

Thanks. Keep up the great work!

-Mike

DanielJonesEB commented 4 years ago

I think this is a fair point - sorry for not replying sooner, I've been busy. I'll leave this open and hopefully I'll get around to considering in more detail how the reality of things can be better expressed.

Thanks for engaging in the conversation!

pburkholder commented 3 years ago

While Log Aggregation seems to be "bring your own/configure" from the perspective of a team running CF, it is a nice OOB experience for product/development teams working on CF. At least that's the case for cloud.gov government agency customers, who have all their logs available to them in org/space-scoped Kibana.

Is log aggregation BYO for most teams on CloudFoundry?