Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1227
@sekimura You want to take stab at adding this as Lua definitions? I
assume the intent would be to expose some of these constants in an internal Lua
table?
---
If your project is set up for
Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/1227
Well it is trivial to make those constants available in the Lua API. I
don't think these things are worth adding log tags on their own.
---
If your project is set up for it, you can reply to
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1227
Hmmm, logging most metrics seems somewhat useless. What would be useful
would be to have generic access to the underlying data that is used to update
the metrics for that transactions.
Github user sekimura commented on the issue:
https://github.com/apache/trafficserver/pull/1227
+1 to " a logging tag that can log an arbitrary metric"
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/1227
I really don't think this is worth a log tag. It is trivial to add this
information as Lua constants to be consumed by `logging.config`. Alternatively,
a logging tag that can log an arbitrary
