You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barrett Oglesby (Jira)" <ji...@apache.org> on 2019/12/19 23:13:00 UTC

[jira] [Updated] (GEODE-7216) The ExportStackTraceCommand should include a timestamp similar to jstack

     [ https://issues.apache.org/jira/browse/GEODE-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barrett Oglesby updated GEODE-7216:
-----------------------------------
    Fix Version/s: 1.11.0

> The ExportStackTraceCommand should include a timestamp similar to jstack
> ------------------------------------------------------------------------
>
>                 Key: GEODE-7216
>                 URL: https://issues.apache.org/jira/browse/GEODE-7216
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Barrett Oglesby
>            Assignee: Mario Kevo
>            Priority: Major
>             Fix For: 1.11.0
>
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> Currently the ExportStackTraceCommand dumps stack traces with a head for each member like:
> {noformat}
> *** Stack-trace for member server3 ***
> {noformat}
> It would be nice for support purposes if it included a timestamp like:
> {noformat}
> *** Stack-trace for member server3 at 2019-09-16 10:39:57 ***
> {noformat}
> That'll help correlate stack traces with logs and stats.
> Something like:
> {noformat}
> ps.append(STACK_TRACE_FOR_MEMBER).append(entry.getKey()).append(" at ")
>     .append(new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date())).append(" ***")
>     .append(System.lineSeparator());
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)