On 11 Feb 2019, at 23:54, Johannes Tuchscherer <jtuchscherer@...> wrote:

Hi there,

Following the last thread about the deprecation of the /containermetrics endpoint, the Loggregator team would like to continue on its path of deprecations. Next on the chopping block is the /firehose endpoint. We understand that this endpoint is used by a few integrations, so we will provide reference implementations and documents for migrating away from the firehose to the newer loggregator endpoints (namely, the RLP Gateway and LogCache). Depending on the feedback we receive to this email, we would like to proceed with the removal of the firehose endpoint in three months - meaning that the loggregator release being cut in three month’s time won't have support for that endpoint anymore.

You can find some example consumers and the documentation of the RLP here:

Go: https://github.com/cloudfoundry/log-stream-cli

Go Client: https://github.com/cloudfoundry/go-loggregator/blob/master/rlp_gateway_client.go

Java: https://github.com/cloudfoundry-community/jmx-consumer-release/tree/develop/src/jmxconsumer

Docs: https://github.com/cloudfoundry/loggregator/blob/master/docs/rlp_gateway.md

Here are some example consumers and the documentation of the Log Cache:

Go: https://github.com/cloudfoundry/log-cache-cli

Go Client: https://github.com/cloudfoundry/log-cache/tree/master/pkg/client

Docs: https://github.com/cloudfoundry/log-cache/blob/master/README.md

Our desire to remove endpoints on the trafficcontroller is based on our plan to get rid of the trafficcontroller - and then everything in loggregator that still references the V1 api and protocol. This will help us to significantly reduce code complexity, but it will also allow us to operate much more efficiently. This should result in reduced overhead for the logging pipeline and ultimately lower infrastructure costs for the logging components in a CF deployment.

Please let us know if you have any comments or concerns.

Johannes

PM of #loggregator