Fix broken links, avoid redirects, etc.

content/docs/concepts/data_model.md

@@ -32,7 +32,7 @@ must match the regex `[a-zA-Z_][a-zA-Z0-9_]`.
 
 Label values may contain any Unicode characters.
 
-See also the [best practices for naming metrics and labels](/docs/practices/naming).
+See also the [best practices for naming metrics and labels](/docs/practices/naming/).
 
 ## Samples
 Samples form the actual time series data. Each sample consists of:

content/docs/instrumenting/clientlibs.md

@@ -22,4 +22,4 @@ sends the current state of all tracked metrics to the server.
 
 If no client library is available for your language, or you want to avoid
 dependencies, you may also implement one of the supported [exposition
-formats](/docs/instrumenting/exposition_formats) yourself to expose metrics.
+formats](/docs/instrumenting/exposition_formats/) yourself to expose metrics.

content/docs/instrumenting/exposition_formats.md

@@ -17,5 +17,5 @@ For details on each format and the content negotiation options, see the
 [Client Data Exposition Format](https://docs.google.com/document/d/1ZjyKiKxZV83VI9ZKAXRGKaUKK2BIWCT7oiGBKDBpjEY/edit?usp=sharing)
 document.
 
-The majority of users should use the existing [client libraries](../clientlibs)
+The majority of users should use the existing [client libraries](/docs/instrumenting/clientlibs/)
 that already implement the exposition formats.

content/docs/introduction/faq.md

@@ -9,11 +9,11 @@ sort_rank: 5
 
 ### What is Prometheus?
 Prometheus is an open-source systems monitoring and alerting toolkit
-with an active ecosystem. See the [overview](../overview).
+with an active ecosystem. See the [overview](/docs/introduction/overview/).
 
 ### How does Prometheus compare against \[other monitoring system\]?
 
-See the [comparison](../comparison) page.
+See the [comparison](/docs/introduction/comparison/) page.
 
 ### What dependencies does Prometheus have?
 
@@ -44,7 +44,7 @@ not be considered a major point when considering a monitoring system.
 The [Push vs Pull for Monitoring](http://www.boxever.com/push-vs-pull-for-monitoring)
 blog post by Brian Brazil goes into more detail.
 
-For cases where you must push, we offer the [Pushgateway](../../instrumenting/pushing).
+For cases where you must push, we offer the [Pushgateway](/docs/instrumenting/pushing/).
 
 ### Who wrote Prometheus?
 
@@ -53,7 +53,7 @@ Prometheus was initially started privately by
 [Julius Volz](http://juliusv.com). The majority of its
 development has been sponsored by [SoundCloud](https://soundcloud.com).
 
-Other companies making active contributions include [Boxever](www.boxever.com)
+Other companies making active contributions include [Boxever](http://www.boxever.com/)
 and [Docker](https://www.docker.com). A full list can be found in the
 [CONTRIBUTORS](https://github.com/prometheus/prometheus/blob/master/CONTRIBUTORS.md)
 file in each repository.
@@ -71,12 +71,12 @@ After extensive research it has been determined that the correct plural of
 ### Can I send alerts?
 
 Yes, with the experimental [Alertmanager](https://github.com/prometheus/alertmanager).
-[PagerDuty](https://www.pagerduty.com/) and email are supported.
+[PagerDuty](http://www.pagerduty.com/) and email are supported.
 
 ### Can I create dashboards?
 
-Yes, with [PromDash](../../visualization/promdash/) and [Console
-templates](visualization/consoles/).
+Yes, with [PromDash](/docs/visualization/promdash/) and [Console
+templates](/docs/visualization/consoles/).
 
 ## Instrumentation
 
@@ -89,7 +89,7 @@ Currently there are client libraries for:
 * [Ruby](https://github.com/prometheus/client_ruby)
 
 If you are interested in contributing a client library for a new language, see
-the [exposition formats](../../instrumenting/exposition_formats/).
+the [exposition formats](/docs/instrumenting/exposition_formats/).
 
 ### Can I monitor machines?
 
@@ -99,13 +99,13 @@ disk utilization, filesystem fullness and network bandwidth.
 
 ### Can I monitor batch jobs?
 
-Yes, using the [Pushgateway](../../instrumenting/pushing). See also the
-[best practices](../../practices/instrumentation/#batch-jobs) for monitoring batch
+Yes, using the [Pushgateway](/docs/instrumenting/pushing/). See also the
+[best practices](/docs/practices/instrumentation/#batch-jobs) for monitoring batch
 jobs.
 
 ### What applications can Prometheus monitor out of the box?
 
-See [exporters for third-party systems](../../instrumenting/exporters).
+See [exporters for third-party systems](/docs/instrumenting/exporters/).
 
 ### Which Java client should I use?
 

content/docs/introduction/getting_started.md

@@ -71,7 +71,7 @@ job: {
 ```
 
 Prometheus configuration is supplied in an ASCII form of [protocol
-buffers](https://developers.google.com/protocol-buffers/docs/overview). The
+buffers](https://developers.google.com/protocol-buffers/docs/overview/). The
 [schema definition](https://github.com/prometheus/prometheus/blob/master/config/config.proto)
 has a complete documentation of all available configuration options.
 
@@ -128,7 +128,7 @@ count(prometheus_target_interval_length_seconds)
 ```
 
 For further details about the expression language, see the
-[expression language documentation](/docs/querying/basics).
+[expression language documentation](/docs/querying/basics/).
 
 ## Using the graphing interface
 

content/docs/practices/consoles.md

@@ -31,7 +31,7 @@ If you find yourself exceeding these, it could make sense to demote the visibili
 less important information, possibly splitting out some subsystems to a new console.
 For example, you could graph aggregated rather than broken-down data, move
 it to the right-hand-side table, or even remove data completely if it is rarely
-useful - you can always look at it in the [expression browser](../../visualization/browser/)!
+useful - you can always look at it in the [expression browser](/docs/visualization/browser/)!
 
 Finally, it is difficult for a set of consoles to serve more than one master.
 What you want to know when oncall (what's broken?) tends to be very different

content/docs/practices/instrumentation.md

@@ -170,7 +170,7 @@ As a rule of thumb, no part of a metric name should ever be procedurally
 generated (use labels instead). The one exception is when proxying metrics
 from another monitoring/instrumentation system.
 
-See also the [naming](../naming) section.
+See also the [naming](/docs/practices/naming/) section.
 
 ### Do not overuse labels
 

content/docs/practices/rules.md

@@ -5,7 +5,7 @@ sort_rank: 5
 
 # Recording rules
 
-A consistent naming scheme for [recording rules](../../operating/rules) makes it
+A consistent naming scheme for [recording rules](/docs/querying/rules/) makes it
 easier to interpret the meaning of a rule at a glance. It also avoids mistakes by 
 making incorrect or meaningless calculations stand out. 
 

content/docs/querying/basics.md

@@ -13,7 +13,7 @@ browser, or consumed by external systems via the HTTP API.
 ## Examples
 
 This document is meant as a reference. For learning, it might be easier to
-start with a couple of [examples](/docs/querying/examples).
+start with a couple of [examples](/docs/querying/examples/).
 
 ## Expression Language Data Types
 
@@ -110,12 +110,12 @@ a `job` label set to `prometheus`:
 ## Operators
 
 Prometheus supports many binary and aggregation operators. These are described
-in detail in the [expression language operators](/docs/querying/operators) page.
+in detail in the [expression language operators](/docs/querying/operators/) page.
 
 ## Functions
 
 Prometheus supports several functions to operate on data. These are described
-in detail in the [expression language functions](/docs/querying/functions) page.
+in detail in the [expression language functions](/docs/querying/functions/) page.
 
 ## Gotchas
 
@@ -149,7 +149,7 @@ Prometheus's expression browser until the result set seems reasonable
 (hundreds, not thousands, of time series at most).  Only when you have filtered
 or aggregated your data sufficiently, switch to graph mode. If the expression
 still takes too long to graph ad-hoc, pre-record it via a [recording
-rule](../rules/#recording-rules).
+rule](/docs/querying/rules/#recording-rules).
 
 This is especially relevant for Prometheus's query language, where a bare
 metric name selector like `api_http_requests_total` could expand to thousands

content/docs/querying/rules.md

@@ -123,7 +123,7 @@ Prometheus's alerting rules are good at figuring what is broken *right now*,
 but they are not a fully-fledged notification solution. Another layer is needed
 to add summarization, notification rate limiting, silencing and alert
 dependencies on top of the simple alert definitions. In Prometheus' ecosystem,
-the [Alert Manager](http://github.com/prometheus/alertmanager) takes on this
+the [Alert Manager](https://github.com/prometheus/alertmanager) takes on this
 role. Thus, Prometheus may be configured to periodically send information about
 alert states to an Alert Manager instance, which then takes care of dispatching
 the right notifications. The Alert Manager instance may be configured via the

content/docs/visualization/browser.md

@@ -7,4 +7,4 @@ sort_rank: 1
 
 The expression browser is available at `/graph` on the Prometheus server, allowing you to enter any expression and see its result either in a table or graphed over time.
 
-This is primarily useful for ad-hoc queries and debugging. For consoles, use [PromDash](../promdash/) or [Console templates](../consoles/).
+This is primarily useful for ad-hoc queries and debugging. For consoles, use [PromDash](/docs/visualization/promdash/) or [Console templates](/docs/visualization/consoles/).

content/docs/visualization/consoles.md

@@ -11,7 +11,7 @@ from the Prometheus server.
 
 Console templates are the most powerful way to create templates that can be
 easily managed in source control. There is a learning curve though, so users new
-to this style of monitoring should try out [PromDash](../promdash/) first.
+to this style of monitoring should try out [PromDash](/docs/visualization/promdash/) first.
 
 ## Getting started
 
@@ -62,7 +62,7 @@ table. The main content has a queries-per-second graph.
 </tr>
 <tr>
   <td>CPU</td>
-  <td>{{ template "prom_query_drilldown" (args 
+  <td>{{ template "prom_query_drilldown" (args
       "avg by(job)(rate(process_cpu_seconds_total{job='myjob'}[5m]))"
       "s/s" "humanizeNoSmallPrefix") }}
   </td>
@@ -87,8 +87,8 @@ new PromConsole.Graph({
   node: document.querySelector("#queryGraph"),
   expr: "sum(rate(http_query_count{job='myjob'}[5m]))",
   name: "Queries",
-  yAxisFormatter: PromConsole.NumberFormatter.humanizeNoSmallPrefix, 
-  yHoverFormatter: PromConsole.NumberFormatter.humanizeNoSmallPrefix, 
+  yAxisFormatter: PromConsole.NumberFormatter.humanizeNoSmallPrefix,
+  yHoverFormatter: PromConsole.NumberFormatter.humanizeNoSmallPrefix,
   yUnits: "/s",
   yTitle: "Queries"
 })
@@ -102,8 +102,8 @@ new PromConsole.Graph({
 The `prom_right_table_head` and `prom_right_table_tail` templates contain the
 right-hand-side table. This is optional.
 
-`prom_query_drilldown` is a template that will evaluate the expression passed to it, format it, 
-and link to the expression in the [expression browser](../browser). The first
+`prom_query_drilldown` is a template that will evaluate the expression passed to it, format it,
+and link to the expression in the [expression browser](/docs/visualization/browser/). The first
 argument is the expression. The second argument is the unit to use. The third
 argument is how to format the output. Only the first argument is requred.
 

content/docs/visualization/template_examples.md

@@ -53,7 +53,7 @@ samples were returned to avoid an execution error. For example this could
 happen if a scrape or rule evaluation has not run yet, or a host was down.
 
 The included `prom_query_drilldown` template handles this, allows for
-formatting of results, and linking to the [expression browser](../browser/).
+formatting of results, and linking to the [expression browser](/docs/visualization/browser/).
 
 ## Using console URL parameters
 
@@ -90,8 +90,8 @@ available inside the loop as `.` is now the loop variable.
 ## Defining reusable templates
 
 Prometheus supports defining templates that can be reused. This is particularly
-powerful when combined with 
-[console library](../template_reference/#console-templates) support, allowing
+powerful when combined with
+[console library](/docs/visualization/template_reference/#console-templates) support, allowing
 sharing of templates across consoles.
 
 ```

content/docs/visualization/template_reference.md

@@ -66,8 +66,8 @@ versions.
 | title         | string        | string  | [strings.Title](http://golang.org/pkg/strings/#Title), capitalises first character of each word.|
 | match         | pattern, text | boolean | [regexp.MatchString](http://golang.org/pkg/regexp/#MatchString) Tests for a regexp match. |
 | reReplaceAll  | pattern, replacement, text | string | [Regexp.ReplaceAllString](http://golang.org/pkg/regexp/#Regexp.ReplaceAllString) Regexp substitution. |
-| graphLink  | expr | string | Returns path to graph view in the [expression browser](../browser) for the expression. |
-| tableLink  | expr | string | Returns path to tabular view in the [expression browser](../browser) for the expression. |
+| graphLink  | expr | string | Returns path to graph view in the [expression browser](/docs/visualization/browser/) for the expression. |
+| tableLink  | expr | string | Returns path to tabular view in the [expression browser](/docs/visualization/browser/) for the expression. |
 
 ### Others
 

content/index.html

@@ -38,7 +38,7 @@ title: Home
     <div class="col-md-3">
       <h2><i class="fa fa-warning"></i> Alerting</h2>
       <p class="desc">Alerts are defined based on Prometheus's flexible query language and maintain dimensional information. An alertmanager handles notifications and silencing.</p>
-      <p><a class="btn btn-default" href="/docs/operating/rules/#alerting-rules" role="button">View details &raquo;</a></p>
+      <p><a class="btn btn-default" href="/docs/querying/rules/#alerting-rules" role="button">View details &raquo;</a></p>
     </div>
     <div class="col-md-3">
       <h2><i class="fa fa-cloud-upload"></i> Exporters</h2>

layouts/header.html

@@ -48,8 +48,8 @@
         <div class="collapse navbar-collapse" id="navbar">
           <ul class="nav navbar-nav navbar-right main-nav">
             <li><a href="/">Overview</a></li>
-            <li><a href="/docs/introduction/overview">Documentation</a></li>
-            <li><a href="/community">Community</a></li>
+            <li><a href="/docs/introduction/overview/">Documentation</a></li>
+            <li><a href="/community/">Community</a></li>
             <li><a href="https://github.com/prometheus"><i class="fa fa-github"></i> Github</a></li>
           </ul>
         </div>

layouts/jumbotron.html

@@ -4,7 +4,7 @@
   <div class="container">
     <h1><img src="/assets/prometheus_logo.svg" alt="Prometheus logo"> Prometheus</h1>
     <p class="subtitle">An open-source service monitoring system and time series database.</p>
-    <p><a class="btn btn-default btn-lg" href="/docs/introduction/getting_started" role="button">Get Started</a></p>
+    <p><a class="btn btn-default btn-lg" href="/docs/introduction/getting_started/" role="button">Get Started</a></p>
   </div>
 </div>