Permalink
Browse files

Fix refs

  • Loading branch information...
thomashumio committed Jun 21, 2018
1 parent 593c13e commit 7992b10952e5bd4e866ade6e5c6aa03d665172be
@@ -2,6 +2,7 @@
title: "Alerts"
weight: 675
category_title: Overview
aliases: ["/features/alerts/notifiers/"]
---
Humio has built-in support for alerting.
Every repository has it's own individual set of alerts.
@@ -97,7 +97,7 @@ end times as relative times if you specify them as strings.

When providing a timestamp, relative time modifiers are specified relative to "now".

See the relative time syntax [here]({{< relref "relative_time_syntax.md" >}})
See the relative time syntax [here]({{< ref "relative-time-syntax.md" >}})

{{% notice note %}}
Relative time modifiers are always relative to now.
@@ -1,5 +1,6 @@
---
title: "Relative Time Syntax"
aliases: ["appendix/relative_time_syntax", "/searching_logs/advanced_topics/relative_time_syntax/"]
---

In many places in Humio you have to specify a time interval. For example
@@ -127,7 +127,7 @@ The configuration file has these parameters:
You can replace them in the file or set them as ENV parameters when starting Filebeat.
If you are running without authentication leave out the whole line `username: ${INGEST_TOKEN}`.
or set the `INGEST_TOKEN` to a dummy value.
Otherwise [create an ingest token as described here]({{< ref "ingest_tokens.md" >}}).
Otherwise [create an ingest token as described here]({{< ref "ingest-tokens.md" >}}).


Note, that in the filebeat configuration we specify that Humio should use the built-in parser `bro-json` to parse the data.
@@ -42,7 +42,7 @@ output.elasticsearch:

* `$HOST` - address/hostname of your Humio server (e.g. `cloud.humio.com`)
* `$REPOSITORY_NAME` - name of your repository on your server (e.g. `sandbox`)
* `$INGEST_TOKEN` - [ingest token]({{< relref "ingest_tokens.md" >}}) for your repository, (e.g. a string such as `fS6Kdlb0clqe0UwPcc4slvNFP3Qn1COzG9DEVLw7v0Ii`).
* `$INGEST_TOKEN` - [ingest token]({{< relref "ingest-tokens.md" >}}) for your repository, (e.g. a string such as `fS6Kdlb0clqe0UwPcc4slvNFP3Qn1COzG9DEVLw7v0Ii`).
* `PATH_TO_YOUR_APPLICATION_LOG` - the file path to the log file you want to send.
* `PARSER_NAME` - the name of either one of the built-in parsers such as `kv` (Key-Value) or a [custom parser]({{< relref "parsers/_index.md" >}}).

@@ -3,6 +3,7 @@ title: "Filebeat"
categories: ["Integration", "DataShipper"]
categories_weight: -100
pageImage: /integrations/filebeat.svg
aliases: ["/sending-data/data-shippers/beats/filebeat/"]
---

[Filebeat](https://www.elastic.co/products/beats/filebeat) is a lightweight,
@@ -87,7 +88,7 @@ You must make the following changes to the sample configuration:
Note that the URL specifies the repository that Humio sends events to.
In the example, the URL points to Humio in the cloud, which is fine if you are using our hosted service.
It is important to specify the port number in the URL otherwise Filebeat defaults to using 9200.
* Insert an [ingest token]({{< relref "ingest_tokens.md" >}}) from the repository as the username.
* Insert an [ingest token]({{< relref "ingest-tokens.md" >}}) from the repository as the username.

* Specify the text encoding to use when reading files using the `encoding` field.
If the log files use special, non-ASCII characters, then set the encoding here. For example, `utf-8` or `latin1`.
@@ -58,7 +58,7 @@ template(name="humiotemplate"
```

Remember to replace `$HOST` with your Humio host, i.e. `cloud.humio.com`
and `$INGEST_TOKEN` with an [ingest token]({{< relref "ingest_tokens.md" >}})
and `$INGEST_TOKEN` with an [ingest token]({{< relref "ingest-tokens.md" >}})
for your repository.

Furthermore `bulkmode` and `usehttps` _has_ to be set to `on` for
@@ -76,6 +76,6 @@ Where:

* `$HOST` - is the name of your Humio server.
* `$REPOSITORY_NAME` - is the name of your repository on your server.
* `$INGEST_TOKEN` - is the [ingest token]({{< relref "ingest_tokens.md" >}}) for your repository.
* `$INGEST_TOKEN` - is the [ingest token]({{< relref "ingest-tokens.md" >}}) for your repository.

See also the page on [Beats]({{< relref "sending_data/data-shippers/beats/_index.md" >}}) for more information.
@@ -166,7 +166,7 @@ spec:
```

Don't forget to replace `$HOST` with the hostname of your Humio instance,
i.e. `cloud.humio.com` and `$INGEST_TOKEN` with your [ingest-token]({{< relref "ingest_tokens.md" >}}).
i.e. `cloud.humio.com` and `$INGEST_TOKEN` with your [ingest-token]({{< relref "ingest-tokens.md" >}}).

{{% notice note %}}
Remember if you're an on-prem solution without TLS, the
@@ -6,7 +6,7 @@ category_title: "Overview"

There are steps to getting your data into Humio:

1. [Generating an Ingest Token]({{< ref "ingest_tokens.md" >}}) Token - A special API token only for the Ingest API.
1. [Generating an Ingest Token]({{< ref "ingest-tokens.md" >}}) Token - A special API token only for the Ingest API.
1. Sending data - Which is the subject of this page
1. Parsing and ingesting data - Described in the [Parsers sections]({{< ref "parsers/_index.md" >}})

@@ -57,7 +57,7 @@ graph LR;
## Platform Integrations {#platform-integrations}

If you want to get logs and metrics from your deployment platform, e.g. a Kubernetes cluster or your company PaaS,
you can use one of our [Platform Integrations]({{sending-data-to-humio}}).
you can use one of our [Platform Integrations]({{< ref "sending-data-to-humio/_index.md" >}}).

**Example Flow**
Depending on your platform the data flow will look slightly different. Some systems
@@ -1,6 +1,7 @@
---
title: "Ingest Tokens"
weight: 1
aliases: ["sending-data-to-humio/ingest_tokens"]
---

Humio has two kinds of API tokens. The _Personal API Tokens_ and _Ingest Tokens_.
@@ -54,7 +54,7 @@ and not "View" since they cannot be used for storage).

### 2.2 Find your Ingest Token

Once you have chosen a repository you need get an access token called an [ingest token]({{< relref "ingest_tokens.md" >}}).
Once you have chosen a repository you need get an access token called an [ingest token]({{< relref "ingest-tokens.md" >}}).
You can find the _default_ ingest token generated for your repository by going to:

`Settings` __→__ `Ingest Tokens` __→__ `Click the Eye Icon`
@@ -2,4 +2,4 @@ Where:

* `$HOST` - is the address/hostname of your Humio server (e.g. `cloud.humio.com`)
* `$REPOSITORY_NAME` - is the name of your repository on your server (e.g. `sandbox`)
* `$INGEST_TOKEN` - is the [ingest token]({{ relref . "sending-data/ingest_tokens" }}) for your repository, (e.g. a string such as `fS6Kdlb0clqe0UwPcc4slvNFP3Qn1COzG9DEVLw7v0Ii`).
* `$INGEST_TOKEN` - is the [ingest token]({{ ref . "ingest-tokens.md" }}) for your repository, (e.g. a string such as `fS6Kdlb0clqe0UwPcc4slvNFP3Qn1COzG9DEVLw7v0Ii`).

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

@anagrius This link is quite broken. Not sure how to fix it?

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

Just remove the DOT (.)

[ingest token]({{ ref . "ingest-tokens.md" }})

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

[ingest token]({{ ref "ingest-tokens.md" }})

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

Same story I'm afraid. I end up at /integrations/platform-integrations/docker/%7B%7B%20ref%20%22ingest-tokens.md%22%20%7D%7D

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

Ok, Hugo assumes there is only one file with a perticular filename. In this case a file called ingest-tokens.md was ALSO added to the docker docks.

Two options either rename that file, or specify the full path to file you want:

[ingest token]({{ ref "sending-data-to-humio/ingest-tokens.md" }})

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

No luck. Wasn't the whole point of using these ugly refs that shouldn't get dead links?

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

No luck?

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

Oh, maybe add {{< ref ... >}}

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

If I add those [ingest token]({{< ref "/sending-data-to-humio/ingest-tokens.md" >}}) I get a completely different error:

"…/docs.humio.com/layouts/partials/common-rest-params.md:4:1": parse failed: template: partials/common-rest-params.md:4: unexpected "<" in command

This comment has been minimized.

@anagrius

anagrius via email Jan 10, 2019

Contributor

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

Makes no difference. As I read it, it's complaining about the <.

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

Why it would say unexpected token I don't know

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

There must be a link you can copy

This comment has been minimized.

@mwl

mwl Jan 10, 2019

Contributor

markdownify doesn't support the same syntax as the Hugo Markdown parser?

This comment has been minimized.

@anagrius

anagrius Jan 10, 2019

Contributor

Maybe not there many dialects

@@ -11,7 +11,7 @@ please read the [brief overview of log management](log-management-overview.md).

First, decide which log data sources you want to put into Humio.

Second, find or create an [ingest token]({{< ref "ingest_tokens.md" >}}).
Second, find or create an [ingest token]({{< ref "ingest-tokens.md" >}}).

Third, go through the [Integrations](index.md#integrations) and see if you
can find the integration you need. For example, if what you want is:

0 comments on commit 7992b10

Please sign in to comment.