Hello CF Community! We wanted to share a document[1] that describes some best practices, and solicit feedback for instrumenting workloads in cf-for-k8s. From a metric standpoint we are making good pro

#loggregator

Hello partners. Thank you very much for your answers and the contribution to the concern. But then, we can say that it is better not to implement the theme of Jommla in CF, according to what I see it

#cf #service #loggregator

Hi Adam, Congrats, excited to see this as an incubation proposal, following the Eirini example directly in the Runtime PMC. It is great to see these pieces of technology moving into the core of CF rig

#loggregator

Love it! The amount of ideas and experiments around integrations with other OSS efforts being shared this last couple of weeks is amazing to see. :)

#loggregator

Sounds good. Currently in my environment we disable user account creation instead using enterprise LDAP or OAuth. Supporting internal users and external users isn't something I've considered in my dep

#loggregator

One thing to watch out for using cf nozzle or cf top to try and calculate Noisy Neighbors by reading from the firehose. Reading with a single client can put back pressure on the Loggregator system by

#loggregator

In service to our mission of providing all users of Cloud Foundry observability of their systems the Loggregator team is excited to offer a new feature for App Developers to use external monitoring to

#loggregator

Recently the Loggregator team has been researching the implications of streaming and the lack of ordering guarantee associated with it. I wanted to post a few findings as it is a common inquiry and so

#loggregator

Here is the correct link for noisy neighbor - https://docs.google.com/document/d/19CI185yhEAD4wcdHoYTLJQZFkBhWZ4c17yBMxJ4yT-U/edit

#loggregator