## "Iterating on config changes":#iterating
## "Common problems and solutions":#common-problems
# "Initial user and login":#initial_user
+# "Monitoring and Metrics":#monitoring
# "After the installation":#post_install
h2(#introduction). Introduction
# @workbench2.${CLUSTER}.${DOMAIN}@
# @webshell.${CLUSTER}.${DOMAIN}@
# @shell.${CLUSTER}.${DOMAIN}@
+# @monitoring.${CLUSTER}.${DOMAIN}@
For more information, see "DNS entries and TLS certificates":install-manual-prerequisites.html#dnstls.
If you *did* configure a different authentication provider, the first user to log in will automatically be given Arvados admin privileges.
+h2(#monitoring). Monitoring and Metrics
+
+You can monitor the health and performance of the system using the admin dashboard:
+
+https://grafana.@${CLUSTER}.${DOMAIN}@
+
+Use the username and password you gave in @local.conf@ to log in.
+
h2(#post_install). After the installation
As part of the operation of @installer.sh@, it automatically creates a @git@ repository with your configuration templates. You should retain this repository but *be aware that it contains sensitive information* (passwords and tokens used by the Arvados services as well as cloud credentials if you used Terraform to create the infrastructure).
}
aliases = {
controller: ["ws"]
- workbench: ["workbench2", "webshell", "keep", "download", "*.collections"]
+ workbench: ["workbench2", "webshell", "keep", "download", "prometheus", "grafana", "*.collections"]
}
cname_by_host = flatten([
for host, aliases in local.aliases : [
]
])
}
-