surekhasaharan commented on a change in pull request #10047:
URL: https://github.com/apache/druid/pull/10047#discussion_r444005511
##########
File path: docs/operations/druid-console.md
##########
@@ -22,20 +22,26 @@ title: "Web console"
~ under the License.
-->
+Druid include a console for managing datasources, segments, tasks, data
processes (Historicals and MiddleManagers), and coordinator dynamic
configuration. Users can also run SQL and native Druid queries in the console.
The Druid Console is hosted by the [Router](../design/router.md) process.
-In addition, the following cluster settings must be enabled:
+The following cluster settings must be enabled, as they are by default:
- the Router's [management
proxy](../design/router.html#enabling-the-management-proxy) must be enabled.
- the Broker processes in the cluster must have [Druid
SQL](../querying/sql.md) enabled.
-After enabling Druid SQL on the Brokers and deploying a Router with the
management proxy enabled, the Druid console can be accessed at:
+The Druid console can be accessed at:
```
http://<ROUTER_IP>:<ROUTER_PORT>
```
+> It is important to note that any Druid console user will have, effectively,
the same machine permission as
Review comment:
would it read better, if we write "the same file permissions as the user
under which Druid runs", or just "the same permission as...", "machine
permission" seems weird to me.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
