techdocsmith commented on code in PR #12593:
URL: https://github.com/apache/druid/pull/12593#discussion_r889421481
##########
docs/operations/druid-console.md:
##########
@@ -41,36 +39,50 @@ http://<ROUTER_IP>:<ROUTER_PORT>
will show console users the files that the underlying user has permissions to.
In general, avoid running Druid as
root user. Consider creating a dedicated user account for running Druid.
-Below is a description of the high-level features and functionality of the
Druid Console
+This topic presents the high-level features and functionality of the Druid
console.
## Home
-The home view provides a high level overview of the cluster.
+The **Home** view provides a high-level overview of the cluster.
Each card is clickable and links to the appropriate view.
-The legacy menu allows you to go to the [legacy coordinator and overlord
consoles](./management-uis.md#legacy-consoles) should you need them.
+
+The **Home** view displays the following cards:
+
+* __Status__. Click this card for information on the Druid version and any
extensions loaded on the cluster.
+* [Datasources](#datasources)
+* [Segments](#segments)
+* [Supervisors](#supervisors-and-tasks)
+* [Tasks](#supervisors-and-tasks)
+* [Services](#services)
+* [Lookups](#lookups)
+
+You can access the [data loader](#data-loader) and [lookups view](#lookups)
from the top-level navigation of the **Home** view.
## Data loader
-The data loader view allows you to load data by building an ingestion spec
with a step-by-step wizard.
+The data loader allows you to load data by building an ingestion spec with a
step-by-step wizard.
Review Comment:
```suggestion
You can use the data loader build an ingestion spec with a step-by-step
wizard.
```
##########
docs/operations/druid-console.md:
##########
@@ -102,27 +117,30 @@ Click on the magnifying glass for any task to see more
detail about it.
-## Servers
+## Services
-The servers tab lets you see the current status of the nodes making up your
cluster.
+The **Services** view lets you see the current status of the nodes making up
your cluster.
You can group the nodes by type or by tier to get meaningful summary
statistics.
## Query
-The query view lets you issue [DruidSQL](../querying/sql.md) queries and
display the results as a table.
-The view will attempt to infer your query and let you modify via contextual
actions such as adding filters and changing the sort order when possible.
+The **Query** view lets you issue [Druid SQL](../querying/sql.md) queries and
display the results as a table.
+The view will attempt to infer your query and let you modify the query via
contextual actions such as adding filters and changing the sort order when
possible.
+
+From the ellipsis menu beside **Run**, you can view your query history, see
the native query translation for a given Druid SQL query, and set the [query
context](../querying/query-context.md).
The query view can also issue queries in Druid's [native query
format](../querying/querying.md), which is JSON over HTTP.
-To send a native Druid query, you must start your query with `{` and format it
as JSON.
+To send a native Druid query, start your query with `{` and format it as a
JSON object.
Review Comment:
Don't all JSON objects begin with `{`?
##########
docs/operations/druid-console.md:
##########
@@ -22,17 +22,15 @@ title: "Web console"
~ under the License.
-->
-Druid includes a console for managing datasources, segments, tasks, data
processes (Historicals and MiddleManagers), and coordinator dynamic
configuration. You can also run SQL and native Druid queries in the console.
+Druid includes a web console for loading data, managing datasources and tasks,
and viewing server status and segment information.
+You can also run SQL and native Druid queries in the console.
-The Druid Console is hosted by the [Router](../design/router.md) process.
-
-The following cluster settings must be enabled, as they are by default:
-
-- the Router's [management
proxy](../design/router.md#enabling-the-management-proxy) must be enabled.
-- the Broker processes in the cluster must have [Druid
SQL](../querying/sql.md) enabled.
-
-You can access the Druid console at:
+The following cluster settings must be enabled to use the Druid console. Note
that these settings are enabled by default.
Review Comment:
```suggestion
Enable the following cluster settings o use the Druid console. Note that
these settings are enabled by default.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
