[
https://issues.apache.org/jira/browse/METRON-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346974#comment-16346974
]
ASF GitHub Bot commented on METRON-1433:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/915
Perhaps we can leverage parts of the performance logging code for this
purpose? The frequency/sampling bit was something I had wanted to add for
some time now.
https://github.com/apache/metron/pull/665
On Wed, Jan 31, 2018 at 7:58 AM, Casey Stella <[email protected]>
wrote:
> @mraliagha <https://github.com/mraliagha> Well, if it's being used
> explicitly and on an on-going manner, then I'll remove this PR. Do you
> think there's some value to being able to slice and dice in the global
> config the ability to turn on and off these by:
>
> - type - threatintel vs enrichment
> - adapter - stellar vs hbase vs geo
> - frequency - kinda like a tracer, have 1 in k messages have them
>
> Thoughts?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/metron/pull/915#issuecomment-361957549>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAoMCxo9Z9PA_DgTESxTJKuUkOE18kVqks5tQH-OgaJpZM4RxWHH>
> .
>
> Only emit debugging timing fields in enrichment when debugging is turned on
> ---------------------------------------------------------------------------
>
> Key: METRON-1433
> URL: https://issues.apache.org/jira/browse/METRON-1433
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Priority: Major
>
> Right now we always emit performance debugging fields in the split/join
> bolts. We should only do that when debug logging is turned on for
> org.apache.metron.enrichment.bolt
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
