You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (Jira)" <ji...@apache.org> on 2020/09/01 22:41:00 UTC

[jira] [Assigned] (GEODE-1383) LogBanner is missing from rolled log files

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

Kirk Lund reassigned GEODE-1383:
--------------------------------

    Assignee: Kirk Lund

> LogBanner is missing from rolled log files
> ------------------------------------------
>
>                 Key: GEODE-1383
>                 URL: https://issues.apache.org/jira/browse/GEODE-1383
>             Project: Geode
>          Issue Type: Bug
>          Components: logging
>            Reporter: Jens Deppe
>            Assignee: Kirk Lund
>            Priority: Major
>              Labels: LogBanner, observability, starter
>
> Please add gemfire,heap, xml configuration information to start of every log file
> We often have situations where we have difficulty establishing the configuration or JVM startup arguments, or XML configuration without multiple interactions with the customer, even when they've provided logs. When the customer has rolled over enough, and we overwrite the "parent" first log, we then lose all of that detail from startup that often proves very helpful.
> If it would be easy to incorporate this startup configuration information into the beginning of each log file as we rollover, we would always have it and be able to be more productive debugging prod issues and ultimately have happier users.



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