[
https://issues.apache.org/jira/browse/NIFI-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-4221:
--------------------------------
Description:
Currently the application startup time is printed in nanoseconds in the app
log. While this is very precise, because of the scale of these values, it can
require mental math to detect delays or variance from the standard/average
timing. I think it would be helpful to print a "human-readable" (i.e. broken
out into larger units) start time alongside the nanosecond precision time:
{code}
2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
initialization took 15127377569 nanoseconds.
{code}
to:
{code}
2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
initialization took 15127377569 nanoseconds (15 seconds).
{code}
While currently it's simply a matter of moving the decimal over the right
number of places, some deployments on cloud systems (especially those with low
entropy before NIFI-3313 was resolved) could take minutes to deploy. Being able
to parse these values in meaningful dimensions at a glance is helpful.
Update: This is also the case with NAR unpacking time: {{2017-06-05
19:39:50,095 INFO [main] org.apache.nifi.nar.NarUnpacker NAR loading process
took 11056718205 nanoseconds.}}
was:
Currently the application startup time is printed in nanoseconds in the app
log. While this is very precise, because of the scale of these values, it can
require mental math to detect delays or variance from the standard/average
timing. I think it would be helpful to print a "human-readable" (i.e. broken
out into larger units) start time alongside the nanosecond precision time:
{code}
2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
initialization took 15127377569 nanoseconds.
{code}
to:
{code}
2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
initialization took 15127377569 nanoseconds (15 seconds).
{code}
While currently it's simply a matter of moving the decimal over the right
number of places, some deployments on cloud systems (especially those with low
entropy before NIFI-3313 was resolved) could take minutes to deploy. Being able
to parse these values in meaningful dimensions at a glance is helpful.
> Print app startup in human-readable time
> ----------------------------------------
>
> Key: NIFI-4221
> URL: https://issues.apache.org/jira/browse/NIFI-4221
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.3.0
> Reporter: Andy LoPresto
> Priority: Minor
> Labels: logs, time
>
> Currently the application startup time is printed in nanoseconds in the app
> log. While this is very precise, because of the scale of these values, it can
> require mental math to detect delays or variance from the standard/average
> timing. I think it would be helpful to print a "human-readable" (i.e. broken
> out into larger units) start time alongside the nanosecond precision time:
> {code}
> 2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
> initialization took 15127377569 nanoseconds.
> {code}
> to:
> {code}
> 2017-07-24 14:00:14,159 INFO [main] org.apache.nifi.NiFi Controller
> initialization took 15127377569 nanoseconds (15 seconds).
> {code}
> While currently it's simply a matter of moving the decimal over the right
> number of places, some deployments on cloud systems (especially those with
> low entropy before NIFI-3313 was resolved) could take minutes to deploy.
> Being able to parse these values in meaningful dimensions at a glance is
> helpful.
> Update: This is also the case with NAR unpacking time: {{2017-06-05
> 19:39:50,095 INFO [main] org.apache.nifi.nar.NarUnpacker NAR loading process
> took 11056718205 nanoseconds.}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
