[GEODE-10150] alter runtime command and change loglevel command docs bug & improvements

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.14.4
• Fix Version/s: 1.12.10, 1.13.9, 1.14.5, 1.15.0
• Component/s: docs
• Labels: pull-request-available
• Assignee: Dave Barnes
• Reporter: Deepak Khopade
• Created: 22/Mar/22 20:36
• Updated: 22/Jun/22 20:46
• Resolved: 23/Mar/22 18:53

Description

The parameters information for gfsh>alter runtime --log-level shows an incorrect parameter name in a table where all parameter's description is provided. The actual expects --log-level but the row in a table says --loglevel. See the screenshot attached. (https://gemfire.docs.pivotal.io/910/geode/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B)

Another important point is, we should add a line on both the links below to state the difference when using these commands (alter runtime and change loglevel).
https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B
https://geode.apache.org/docs/guide/114/tools_modules/gfsh/command-pages/change.html

When I tried both of these commands, it has been found that for locator we need to use gfsh>change loglevel --loglevel=config --member=locator and gfsh>alter runtime --log-level for cache server members. The alter runtime --log-level command doesn't work for Locators.

So adding a line or changing an existing line on the docs will help new customers.

Issue Links

• links to: GitHub Pull Request #7474

Sub-Tasks

• check log levels for gfsh commands: Open