Update README links (#43)

Author: pirgeo

README.md

@@ -2,14 +2,15 @@
 
 > This project is developed, maintained and supported by Dynatrace.
 
-A fluentd output plugin for sending logs to the Dynatrace [Generic log ingest API v2](https://www.dynatrace.com/support/help/shortlink/log-monitoring-log-data-ingestion).
+A fluentd output plugin for sending logs to the Dynatrace [Generic log ingest API v2](https://docs.dynatrace.com/docs/shortlink/log-monitoring-log-data-ingestion).
+For more information, see [the Dynatrace documentation on streaming logs with Fluentd](https://docs.dynatrace.com/docs/shortlink/log-monitoring-stream-logs-with-fluentd).
 
 ## Requirements
 
 - An instance of fluentd >= v1.0 from which logs should be exported
 - Ruby version >= 2.7.0
-- An ActiveGate with the Generic log ingest API v2 enabled as described in the [Dynatrace documentation](https://www.dynatrace.com/support/help/shortlink/log-monitoring-log-data-ingestion)
-- A [Dynatrace API token](https://www.dynatrace.com/support/help/shortlink/api-authentication) with the `logs.ingest` (Ingest Logs) scope
+- An ActiveGate with the Generic log ingest API v2 enabled as described in the [Dynatrace documentation](https://docs.dynatrace.com/docs/shortlink/log-monitoring-log-data-ingestion)
+- A [Dynatrace API token](https://docs.dynatrace.com/docs/shortlink/api-authentication) with the `logs.ingest` (Ingest Logs) scope
 
 ## Installation
 
@@ -60,13 +61,13 @@ The `@type` directive tells fluentd which plugin should be used for the correspo
 
 - `required`
 
-This is the full URL of the [Generic log ingest API v2](https://www.dynatrace.com/support/help/shortlink/log-monitoring-log-data-ingestion) endpoint on your ActiveGate.
+This is the full URL of the [Generic log ingest API v2](https://docs.dynatrace.com/docs/shortlink/log-monitoring-log-data-ingestion) endpoint on your ActiveGate.
 
 ### `api_token`
 
 - `required`
 
-This is the [Dynatrace API token](https://www.dynatrace.com/support/help/shortlink/api-authentication) which will be used to authenticate log ingest requests. It should be assigned only the `logs.ingest` (Ingest Logs) scope.
+This is the [Dynatrace API token](https://docs.dynatrace.com/docs/shortlink/api-authentication) which will be used to authenticate log ingest requests. It should be assigned only the `logs.ingest` (Ingest Logs) scope.
 
 ### `ssl_verify_none`
 

example/README.md

@@ -7,14 +7,14 @@ It is possible to have FluentD ingest the logs of your kubernetes nodes and let
 Generally needed:
 
 - A Dynatrace namespace, if you do not already have one
-- An [API Token](https://www.dynatrace.com/support/help/dynatrace-api/basics/dynatrace-api-authentication/) with "Ingest logs" permission
+- An [API Token](https://docs.dynatrace.com/docs/shortlink/api-authentication) with "Ingest logs" permission
 - The dynatrace-monitoring service-account
 
    ``kubectl apply -f service-account.yaml``
 
 Only needed in combination with a Dynatrace ActiveGate:
 
-- A [PaaS Token](https://www.dynatrace.com/support/help/get-started/access-tokens/)
+- A [PaaS Token](https://docs.dynatrace.com/docs/shortlink/token)
 - Available persistent storage in your Kubernetes cluster
 
 ## Decide on a log ingest endpoint