Not DNS connections, but regular connections per downstream service.
https://github.com/apache/trafficserver/pull/1609
The HostDB stat also can be dumped into JSON. It could be convenient if you
would like to know the exact HostDB cache result for a specific service
name.
Leif Hedstrom 于2019年6月6日
> On Jun 6, 2019, at 18:57, zzz wrote:
>
> We have been using those pages to monitor Hostdb and connection count table
> in LI. We found it handy and useful. Not sure what’s the alternative way to
> do similar things.
Hmm, you mean dns connections ? Regular connection counts have metrics.
As
+1
On Thu, Jun 6, 2019 at 5:51 PM Steven R. Feltner
wrote:
> +1
>
> On 6/6/19, 8:32 PM, "Leif Hedstrom" wrote:
>
> This code is disabled and does not build by default. I think it’s time
> to remove this code path completely, it’s an insecure protocol, and I don’t
> think any of us enables
We have been using those pages to monitor Hostdb and connection count table
in LI. We found it handy and useful. Not sure what’s the alternative way to
do similar things.
There will be no performance impact unless you issue a request. When you
want to debug, the box is already in some bad state an
+1
On 6/6/19, 8:32 PM, "Leif Hedstrom" wrote:
This code is disabled and does not build by default. I think it’s time to
remove this code path completely, it’s an insecure protocol, and I don’t think
any of us enables this ?
— Leif
+1
Totally Agree - a much straightforward vote than disabling tlsv1.1 :=)
> On Jun 6, 2019, at 5:32 PM, Leif Hedstrom wrote:
>
> This code is disabled and does not build by default. I think it’s time to
> remove this code path completely, it’s an insecure protocol, and I don’t
> think any of
+1
On Thursday, June 6, 2019, 5:32:10 PM PDT, Leif Hedstrom
wrote:
This code is disabled and does not build by default. I think it’s time to
remove this code path completely, it’s an insecure protocol, and I don’t think
any of us enables this ?
— Leif
This code is disabled and does not build by default. I think it’s time to
remove this code path completely, it’s an insecure protocol, and I don’t think
any of us enables this ?
— Leif
Hi all,
we have this feature where ATS can server some “static” pages for stats and
introspection. I’d like to propose that we remove this feature for v9.0.0,
opening up the door for better implementations via the traffic_ctl reworks.
I understand that this would leave us without some of this f
> On Jun 4, 2019, at 18:15, Masaori Koshiba wrote:
>
> +1
>
> OpenSSL support TLSv1.2 from v1.0.1, and our minimum requirements of it is
> v1.0.2. from v9.0.0. There're no problems.
Well the thing to watch out for is if you have clients which don’t support v1.2
or later :).
I’ll make a PR
Hi,
I am trying to debug a crash I am seeing with 7.1.6. This crash happens
with no traffic and my custom plugin enabled. My plugin periodically
performs async fetches (using atscppapi) to retrieve data from a remote
server. The crash is happening in the continuation handler. When I try to
print th
11 matches
Mail list logo
