[docs] Migrate docs from AsciiDoc to Markdown (#27)

Co-authored-by: Mike Birnstiehl <[email protected]>

Author: colleenmcginnis

docs/docset.yml

@@ -0,0 +1,30 @@
+---
+mapped_pages:
+  - https://www.elastic.co/guide/en/ecs-logging/go-zerolog/current/intro.html
+  - https://www.elastic.co/guide/en/ecs-logging/go-zerolog/current/index.html
+---
+
+# ECS Logging Go (Zerolog) [intro]
+
+ECS loggers are formatter/encoder plugins for your favorite logging libraries. They make it easy to format your logs into ECS-compatible JSON.
+
+The encoder logs in JSON format and handles the logging of error fields in [ECS error format](ecs://docs/reference/ecs-error.md).
+
+By default, the following fields are added:
+
+```json
+{
+  "log.level": "info",
+  "@timestamp": "2020-09-13T10:48:03.000Z",
+  "message":" some logging info",
+  "ecs.version": "1.6.0"
+}
+```
+
+::::{tip}
+Want to learn more about ECS, ECS logging, and other available language plugins? See the [ECS logging guide](ecs-logging://docs/reference/intro.md).
+::::
+
+
+Ready to jump into `ecszerolog`? [Get started](/reference/setup.md).
+

docs/index.asciidoc

@@ -0,0 +1,143 @@
+---
+mapped_pages:
+  - https://www.elastic.co/guide/en/ecs-logging/go-zerolog/current/setup.html
+navigation_title: Get started
+---
+
+# Get started with ECS Logging Go (Zerolog) [setup]
+
+
+## Step 1: Install [setup-step-1]
+
+Add the package to your `go.mod` file:
+
+```go
+require go.elastic.co/ecszerolog main
+```
+
+
+## Step 2: Configure [setup-step-2]
+
+Set up a default logger. For example:
+
+```go
+logger := ecszerolog.New(os.Stdout)
+log.Logger = logger
+```
+
+
+## Examples [examples]
+
+
+### Use structured logging [use-structured-logging]
+
+```go
+// Add custom fields.
+log.Info().Msg("hello world").Str("custom", "foo")
+```
+
+The example above produces the following log output:
+
+```json
+{
+  "@timestamp": "2021-01-20T11:12:43.061+0800",
+  "custom":"foo",
+  "ecs.version": "1.6.0",
+  "log.level": "info",
+  "message":"hello world"
+}
+```
+
+
+## Step 3: Configure Filebeat [setup-step-3]
+
+:::::::{tab-set}
+
+::::::{tab-item} Log file
+1. Follow the [Filebeat quick start](beats://docs/reference/filebeat/filebeat-installation-configuration.md)
+2. Add the following configuration to your `filebeat.yaml` file.
+
+For Filebeat 7.16+
+
+```yaml
+filebeat.inputs:
+- type: filestream <1>
+  paths: /path/to/logs.json
+  parsers:
+    - ndjson:
+      overwrite_keys: true <2>
+      add_error_key: true <3>
+      expand_keys: true <4>
+
+processors: <5>
+  - add_host_metadata: ~
+  - add_cloud_metadata: ~
+  - add_docker_metadata: ~
+  - add_kubernetes_metadata: ~
+```
+
+1. Use the filestream input to read lines from active log files.
+2. Values from the decoded JSON object overwrite the fields that {{filebeat}} normally adds (type, source, offset, etc.) in case of conflicts.
+3. {{filebeat}} adds an "error.message" and "error.type: json" key in case of JSON unmarshalling errors.
+4. {{filebeat}} will recursively de-dot keys in the decoded JSON, and expand them into a hierarchical object structure.
+5. Processors enhance your data. See [processors](beats://docs/reference/filebeat/filtering-enhancing-data.md) to learn more.
+
+
+For Filebeat < 7.16
+
+```yaml
+filebeat.inputs:
+- type: log
+  paths: /path/to/logs.json
+  json.keys_under_root: true
+  json.overwrite_keys: true
+  json.add_error_key: true
+  json.expand_keys: true
+
+processors:
+- add_host_metadata: ~
+- add_cloud_metadata: ~
+- add_docker_metadata: ~
+- add_kubernetes_metadata: ~
+```
+::::::
+
+::::::{tab-item} Kubernetes
+1. Make sure your application logs to stdout/stderr.
+2. Follow the [Run Filebeat on Kubernetes](beats://docs/reference/filebeat/running-on-kubernetes.md) guide.
+3. Enable [hints-based autodiscover](beats://docs/reference/filebeat/configuration-autodiscover-hints.md) (uncomment the corresponding section in `filebeat-kubernetes.yaml`).
+4. Add these annotations to your pods that log using ECS loggers. This will make sure the logs are parsed appropriately.
+
+```yaml
+annotations:
+  co.elastic.logs/json.overwrite_keys: true <1>
+  co.elastic.logs/json.add_error_key: true <2>
+  co.elastic.logs/json.expand_keys: true <3>
+```
+
+1. Values from the decoded JSON object overwrite the fields that {{filebeat}} normally adds (type, source, offset, etc.) in case of conflicts.
+2. {{filebeat}} adds an "error.message" and "error.type: json" key in case of JSON unmarshalling errors.
+3. {{filebeat}} will recursively de-dot keys in the decoded JSON, and expand them into a hierarchical object structure.
+::::::
+
+::::::{tab-item} Docker
+1. Make sure your application logs to stdout/stderr.
+2. Follow the [Run Filebeat on Docker](beats://docs/reference/filebeat/running-on-docker.md) guide.
+3. Enable [hints-based autodiscover](beats://docs/reference/filebeat/configuration-autodiscover-hints.md).
+4. Add these labels to your containers that log using ECS loggers. This will make sure the logs are parsed appropriately.
+
+```yaml
+labels:
+  co.elastic.logs/json.overwrite_keys: true <1>
+  co.elastic.logs/json.add_error_key: true <2>
+  co.elastic.logs/json.expand_keys: true <3>
+```
+
+1. Values from the decoded JSON object overwrite the fields that {{filebeat}} normally adds (type, source, offset, etc.) in case of conflicts.
+2. {{filebeat}} adds an "error.message" and "error.type: json" key in case of JSON unmarshalling errors.
+3. {{filebeat}} will recursively de-dot keys in the decoded JSON, and expand them into a hierarchical object structure.
+::::::
+
+:::::::
+For more information, see the [Filebeat reference](beats://docs/reference/filebeat/configuring-howto-filebeat.md).
+

docs/introduction.asciidoc

@@ -0,0 +1,3 @@
+toc:
+  - file: index.md
+  - file: setup.md