+1
-Bryan
> On Jul 31, 2018, at 12:05 PM, Leif Hedstrom wrote:
>
>
>
>> On Jul 28, 2018, at 11:10 AM, Alan Carroll
>> wrote:
>>
>> +1
>>
>
> Not a lot of input here, but since no one has objected to this, I will make a
> PR with this deprecation. Functionality will be retained for the
> On Jul 28, 2018, at 11:10 AM, Alan Carroll
> wrote:
>
> +1
>
Not a lot of input here, but since no one has objected to this, I will make a
PR with this deprecation. Functionality will be retained for the lifetime of
the v8.0.0 LTS release.
Cheers,
— Leif
+1
On Thu, Jul 26, 2018 at 3:06 PM Leif Hedstrom wrote:
>
>
> > On Jul 26, 2018, at 2:05 PM, Derek Dagit
> wrote:
> >
> > Sounds good.
> >
> >> 3) Perhaps most importantly, this is not a problem that ATS should
> solve iMO. There are much better systems out there, such as Kafka, Elastic
> Searc
> On Jul 26, 2018, at 2:05 PM, Derek Dagit wrote:
>
> Sounds good.
>
>> 3) Perhaps most importantly, this is not a problem that ATS should solve
>> iMO. There are much better systems out there, such as Kafka, Elastic Search,
>> Splunk etc., all which solves this problem in a much better way
Sounds good.
> 3) Perhaps most importantly, this is not a problem that ATS should solve iMO.
> There are much better systems out there, such as Kafka, Elastic Search,
> Splunk etc., all which solves this problem in a much better way.
Would we offer a recommendation along these lines during whil
Hi all,
I’d like to mark the log collation feature as deprecated for the v8.0.0
release, such that we can remove it from v9.0.0. I have a number of reasons for
this
1) It’s generally really broken. For example, the orphaned logs files are not
handled in any reasonable way, making the feature I
