[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file
[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1383: - Description: 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. was: 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. > Please add gemfire,heap, xml configuration information to start of every log > file > - > > 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, 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 (v7.6.3#76005)
[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file
[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1383: - Issue Type: Bug (was: Improvement) > Please add gemfire,heap, xml configuration information to start of every log > file > - > > 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, starter > > 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 (v7.6.3#76005)
[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file
[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-1383: - Description: 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. was: 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 working on tickets and improve customer satisfaction. > Please add gemfire,heap, xml configuration information to start of every log > file > - > > Key: GEODE-1383 > URL: https://issues.apache.org/jira/browse/GEODE-1383 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Jens Deppe >Priority: Major > Labels: LogBanner, starter > > 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 (v7.6.3#76005)
[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file
[ https://issues.apache.org/jira/browse/GEODE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-1383: - Labels: LogBanner starter (was: LogBanner) > Please add gemfire,heap, xml configuration information to start of every log > file > - > > Key: GEODE-1383 > URL: https://issues.apache.org/jira/browse/GEODE-1383 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Jens Deppe >Priority: Major > Labels: LogBanner, starter > > 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 working on tickets and improve customer > satisfaction. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
