Re: [Proposal] Deprecation of the firehose endpoint
toggle quoted messageShow quoted text
Thanks for the feedback. We actually created PRs for both, firehose-exporter and to firehose-to-syslog. We will continue working with the maintainers to get these pulled in.
A 6 month deprecation window works for Stratos - that should be fine for us to update.
If you can work with the firehose-exporter project to get that updated and off the firehose within the next 2 or 3 months, that would be super helpful and give us time to integrate and test, assuming its a drop-in replacement for the current firehose based version.
thanks for the continuous stream of feedback. We are definitely going to support the firehose-exporter and firehose-to-syslog projects off the firehose to the RLP. The stories in our backlog are coming up soon. Stanislav, do you think that looking at what we did with the firehose-to-syslog project would help you to migrate the kafka-firehose-nozzle?
Also, based on the feedback I have received so far I am open to increasing the deprecation window to 6 months. Would that be acceptable?
We are heavy users of loggregator and we have the same concerns as others in the thread.
We use loggregator for:
- storing all application logs for 6 month (regulations requirement) using kafka-firehose-nozzle
- getting all platform metrics for monitoring purposes using kafka-firehose-nozzle
- getting all applications metrics to provide monitoring dashboard using kafka-firehose-nozzle and cf-metrics-refinery (see https://cloudfoundry.slack.com/messages/C6WFZ5K0F/p1531268612000101)
Another concern is autoscaler (https://github.com/cloudfoundry-incubator/app-autoscaler-release). It is relying on loggregator and I haven't seen any updates on moving out of it yet.
Join email@example.com to automatically receive all group messages.