update docs and blog posts

Author: Amper

cmd/mcp-victorialogs/resources/vm/docs/victorialogs/Articles.md

@@ -1,11 +1,11 @@
 ---
-weight: 29
+weight: 70
 title: Articles
 menu:
  docs:
  parent: 'victorialogs'
  identifier: "victorialogs-articles"
- weight: 29
+ weight: 70
 tags: []
 ---
 

cmd/mcp-victorialogs/resources/vm/docs/victorialogs/CHANGELOG.md

@@ -1,11 +1,11 @@
 ---
-weight: 6
+weight: 13
 title: FAQ
 menu:
  docs:
  identifier: "victorialogs-faq"
  parent: "victorialogs"
- weight: 6
+ weight: 13
  title: FAQ
 tags:
  - logs
@@ -79,7 +79,7 @@ See [this article](https://itnext.io/why-victorialogs-is-a-better-alternative-to
 ## What is the difference between VictoriaLogs and ClickHouse?
 
 ClickHouse is an extremely fast and efficient analytical database. It can be used for logs storage, analysis and processing.
-VictoriaLogs is designed solely for logs. VictoriaLogs uses [similar design ideas as ClickHouse](#how-does-victorialogs-work) for achieving high performance.
+VictoriaLogs is designed solely for logs. VictoriaLogs uses [similar design ideas as ClickHouse](https://docs.victoriametrics.com/victorialogs/faq/#how-does-victorialogs-work) for achieving high performance.
 
 - ClickHouse is good for logs if you know the set of [log fields](https://docs.victoriametrics.com/victorialogs/keyconcepts/#data-model)
  and the expected query types beforehand. Then you can create a table with a column per each log field, and use the most optimal settings for the table -
@@ -243,11 +243,11 @@ or [Grafana plugin for VictoriaLogs](https://docs.victoriametrics.com/victorialo
 then make sure the selected time range covers the last day. Otherwise, the query above returns
 results on the intersection of the last day and the selected time range.
 
-See [why the log field occupies a lot of disk space](#why-the-log-field-occupies-a-lot-of-disk-space).
+See [why the log field occupies a lot of disk space](https://docs.victoriametrics.com/victorialogs/faq/#why-the-log-field-occupies-a-lot-of-disk-space).
 
 ## Why the log field occupies a lot of disk space?
 
-See [how to determine which log fields occupy the most of disk space](#how-to-determine-which-log-fields-occupy-the-most-of-disk-space).
+See [how to determine which log fields occupy the most of disk space](https://docs.victoriametrics.com/victorialogs/faq/#how-to-determine-which-log-fields-occupy-the-most-of-disk-space).
 Log field may occupy a lot of disk space if it contains values with many unique parts (aka "random" values).
 Such values do not compress well, so they occupy a lot of disk space. If you want reducing the amounts of occupied disk space,
 then either remove the given log field from the [ingested](https://docs.victoriametrics.com/victorialogs/data-ingestion/) logs

cmd/mcp-victorialogs/resources/vm/docs/victorialogs/FAQ.md

@@ -23,10 +23,10 @@ before you start working with VictoriaLogs.
 
 There are the following options exist:
 
-- [To run pre-built binaries](#pre-built-binaries)
-- [To run Docker image](#docker-image)
-- [To run in Kubernetes with Helm charts](#helm-charts)
-- [To build VictoriaLogs from source code](#building-from-source-code)
+- [To run pre-built binaries](https://docs.victoriametrics.com/victorialogs/quickstart/#pre-built-binaries)
+- [To run Docker image](https://docs.victoriametrics.com/victorialogs/quickstart/#docker-image)
+- [To run in Kubernetes with Helm charts](https://docs.victoriametrics.com/victorialogs/quickstart/#helm-charts)
+- [To build VictoriaLogs from source code](https://docs.victoriametrics.com/victorialogs/quickstart/#building-from-source-code)
 
 ### Pre-built binaries
 
@@ -36,8 +36,8 @@ Just download archive for the needed Operating system and architecture, unpack i
 For example, the following commands download VictoriaLogs archive for Linux/amd64, unpack and run it:
 
 ```sh
-curl -L -O https://github.com/VictoriaMetrics/VictoriaLogs/releases/download/v1.30.0/victoria-logs-linux-amd64-v1.30.0.tar.gz
-tar xzf victoria-logs-linux-amd64-v1.30.0.tar.gz
+curl -L -O https://github.com/VictoriaMetrics/VictoriaLogs/releases/download/v1.35.0/victoria-logs-linux-amd64-v1.35.0.tar.gz
+tar xzf victoria-logs-linux-amd64-v1.35.0.tar.gz
 ./victoria-logs-prod -storageDataPath=victoria-logs-data
 ```
 
@@ -49,7 +49,7 @@ the needed indexes during [data ingestion](https://docs.victoriametrics.com/vict
 
 See also:
 
-- [How to configure VictoriaLogs](#how-to-configure-victorialogs)
+- [How to configure VictoriaLogs](https://docs.victoriametrics.com/victorialogs/quickstart/#how-to-configure-victorialogs)
 - [How to ingest logs into VictoriaLogs](https://docs.victoriametrics.com/victorialogs/data-ingestion/)
 - [How to query VictoriaLogs](https://docs.victoriametrics.com/victorialogs/querying/)
 
@@ -60,20 +60,20 @@ Here is the command to run VictoriaLogs in a Docker container:
 
 ```sh
 docker run --rm -it -p 9428:9428 -v ./victoria-logs-data:/victoria-logs-data \
- docker.io/victoriametrics/victoria-logs:v1.30.0 -storageDataPath=victoria-logs-data
+ docker.io/victoriametrics/victoria-logs:v1.35.0 -storageDataPath=victoria-logs-data
 ```
 
 See also:
 
-- [How to configure VictoriaLogs](#how-to-configure-victorialogs)
+- [How to configure VictoriaLogs](https://docs.victoriametrics.com/victorialogs/quickstart/#how-to-configure-victorialogs)
 - [How to ingest logs into VictoriaLogs](https://docs.victoriametrics.com/victorialogs/data-ingestion/)
 - [How to query VictoriaLogs](https://docs.victoriametrics.com/victorialogs/querying/)
 
 ### Helm charts
 
 You can run VictoriaLogs in Kubernetes environment
-with [VictoriaLogs single](https://docs.victoriametrics.com/helm/victorialogs-single/)
-or [cluster](https://docs.victoriametrics.com/helm/victorialogs-cluster) helm charts.
+with [VictoriaLogs single](https://docs.victoriametrics.com/helm/victoria-logs-single/)
+or [cluster](https://docs.victoriametrics.com/helm/victoria-logs-cluster/) helm charts.
 
 ### Building from source code
 
@@ -121,7 +121,7 @@ This will build `victoria-logs-prod` executable inside the `bin` folder.
 
 See also:
 
-- [How to configure VictoriaLogs](#how-to-configure-victorialogs)
+- [How to configure VictoriaLogs](https://docs.victoriametrics.com/victorialogs/quickstart/#how-to-configure-victorialogs)
 - [How to ingest logs into VictoriaLogs](https://docs.victoriametrics.com/victorialogs/data-ingestion/)
 - [How to query VictoriaLogs](https://docs.victoriametrics.com/victorialogs/querying/)
 
@@ -165,6 +165,6 @@ Docker-compose demos that integrate VictoriaLogs and various log collectors:
 - [Vector demo](https://github.com/VictoriaMetrics/VictoriaLogs/tree/master/deployment/docker/victorialogs/vector)
 - [Promtail demo](https://github.com/VictoriaMetrics/VictoriaLogs/tree/master/deployment/docker/victorialogs/promtail)
 
-You can use [VictoriaLogs single](https://docs.victoriametrics.com/helm/victorialogs-single/)
-or [cluster](https://docs.victoriametrics.com/helm/victorialogs-cluster) helm charts as a demo for running Vector
+You can use [VictoriaLogs single](https://docs.victoriametrics.com/helm/victoria-logs-single/)
+or [cluster](https://docs.victoriametrics.com/helm/victoria-logs-cluster/) helm charts as a demo for running Vector
 in Kubernetes with VictoriaLogs.