...clickable links. 1. https://lists.cloudfoundry.org/g/cf-dev/topic/oratos_containerized/18106811?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,18106811 2. https://docs.google.com/document/d/1Pjba

#loggregator

As many of you know, the Loggregator team has been experimenting with containerizing the Loggregator and Log cache components for use in a K8s context. I posted about these efforts previously[1], and

#loggregator

Mike - I am not sure, but probably. I'll ping some folks that would know and have them chime in. Adam

Hi Benjamin - The bosh-hm-fowrarder is still available outside of the Loggregator repo, just not supported by the Loggregator team any longer. The supported replacement called bosh-system-metrics forw

ορατός • (oratós) m (feminine ορατή, neuter ορατό) visible, in sight, seen As a follow up to Wednesday's special interest group call about K8s and Cloud Foundry I wanted to share a backlog[1] and slac

#loggregator

Chip - we'd love to demo the experiments with k8s loggregator deployment and log-cache integrations and how that can create a consistent observability experience across both CFAR and CFCR.

Guillaume - The slack channel is the best way to get in touch. One note the PM listed on the cloudfoundry.org site is incorrect. Nadja Conklin has taken over as PM and the team is located here in Denv

This is an interesting idea and related to a couple of feature ideas we (Loggregator) have been doing some research on. Ultimately you would likely want that metric to be available in Loggregator so y

Yeah. Currently the user name / password is simply passed into the app. I expect well at least implement a better hook into CUPS next and for user roles that can create users we could shell out and cr

#loggregator

Back Story The Loggregator team has recently been seeing a ton of benefit from developing CLI plugins. Specifically they are quick to develop, and distribute and lend themselves well to rapid iteratio

#loggregator

One of the benefits we see of having re-engineered the persistance layer of Loggregator (see log-cache announcement) is a simpler architecture which can be deployed to multiple times within Cloud Foun

Problem Summary The current implementation of recent logs and container metrics on CF Application Runtime is slow and increases latency as operators scale up their deployments. Over the past year we h

We recently dropped the v on Loggregator releases. I can't say there was a ton of fore-thought put into this, but it seems more consistent with our other Loggregator supported releases.

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

I can see that overlap, but there is an important scope difference to point out here. The Noisy Neighbor Nozzle requires Operator scope to read from the firehose and is intended for Platform wide moni

#loggregator

Nearly all log reliability problems on CF can be attributed to two main factors. Improper scaling or "noisy neighbor" applications. For the former you can install logmon, check the scaling recommendat

#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

Hi Matthias - We have this vision as well and we recently just got together to discuss related topics as a new initiative and there has been some chatter about it in the Loggregator github repo. Histo

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

Bernd - Happy New Year! I linked another proposal I have been working on that expands on the ideas of containerizing loggregator and the benefits of "unified logging" (or I like to refer to it as egre