From 0b6fc9c9322fd7c6ce94b1fc1a1662c6d4009e96 Mon Sep 17 00:00:00 2001 From: Gracjan Sadowicz Date: Tue, 1 Sep 2026 13:09:16 +0200 Subject: [PATCH] RDBTC-88 Link the Grafana Loki guide internally and refresh it for 7.2 Recommendations 1 and 2 from the review on #2633. Both places that should send readers to this guide were linking to the ravendb.net article instead, promoting an external near-duplicate that competes with the guide for the same query: * guides/how-is-my-database-today.mdx now uses ./slug * docs/monitoring/logging/overview.mdx now uses a relative path out of the version prefix, matching docs/monitoring/integrations/snmp/setup-zabbix.mdx 7.2 refresh of the guide itself: * Title and description no longer pin to 7.0, so they stop drifting with every release. The slug is unchanged, so no redirect is needed. * Applicability is stated in the intro (7.0 and later, including 7.2) instead of being implied by the title. * NLog.Targets.Loki bumped 2.2.0 -> 2.5.0, the current release on NuGet. * Link text in grafana-cloud-configuration-with-opentelemetry.mdx synced with the new title. Screenshots are still the Feb 2025 captures; see the PR description. Verified with DOCUSAURUS_STRICT=true npm run build:current: zero broken links, both references resolve to /guides/sending-your-ravendb-7-0-logs-to-grafana-cloud --- docs/monitoring/logging/overview.mdx | 4 ++-- ...rafana-cloud-configuration-with-opentelemetry.mdx | 2 +- guides/how-is-my-database-today.mdx | 2 +- ...ending-your-ravendb-7-0-logs-to-grafana-cloud.mdx | 12 +++++++----- 4 files changed, 11 insertions(+), 9 deletions(-) diff --git a/docs/monitoring/logging/overview.mdx b/docs/monitoring/logging/overview.mdx index 37c69274fc..8b1eb4add4 100644 --- a/docs/monitoring/logging/overview.mdx +++ b/docs/monitoring/logging/overview.mdx @@ -441,8 +441,8 @@ Then add a new `loki` target for this logger, specifying the properties required -For a complete guide to integrating RavenDB 7.0 logs with **Grafana Cloud** using **NLog and Loki**, -see [this article](https://ravendb.net/articles/sending-your-ravendb-7-0-logs-to-grafana-cloud). +For a complete guide to integrating RavenDB logs with **Grafana Cloud** using **NLog and Loki**, +see [Sending Your RavenDB Logs to Grafana Cloud](../../../guides/sending-your-ravendb-7-0-logs-to-grafana-cloud). diff --git a/guides/grafana-cloud-configuration-with-opentelemetry.mdx b/guides/grafana-cloud-configuration-with-opentelemetry.mdx index 9cbe6be3fb..80cf668a7d 100644 --- a/guides/grafana-cloud-configuration-with-opentelemetry.mdx +++ b/guides/grafana-cloud-configuration-with-opentelemetry.mdx @@ -169,4 +169,4 @@ And that’s it. Your dashboard now has a functioning metric. You can save this We prepared and connected your RavenDB database to the Grafana cloud using OpenTelemetry and also created a basic visualization of CPU usage for your new dashboard. This increases database observability and can be broadly expanded to meet your needs. -If you want your server logs flowing into the same Grafana stack, see [Sending Your RavenDB 7.0 Logs to Grafana Cloud](./sending-your-ravendb-7-0-logs-to-grafana-cloud). +If you want your server logs flowing into the same Grafana stack, see [Sending Your RavenDB Logs to Grafana Cloud](./sending-your-ravendb-7-0-logs-to-grafana-cloud). diff --git a/guides/how-is-my-database-today.mdx b/guides/how-is-my-database-today.mdx index 15aad438a0..2db40ab354 100644 --- a/guides/how-is-my-database-today.mdx +++ b/guides/how-is-my-database-today.mdx @@ -244,7 +244,7 @@ Problems it identifies: * Gradual degradation over time * Patterns not visible in short-term diagnostics -This option is more about preventing future problems than about already existing ones. It is that way because external monitoring, as the name suggests, is external, so it needs to be set up before an incident. For RavenDB, we have two monitoring setup guides: [Zabbix](https://ravendb.net/articles/set-up-zabbix-monitoring-for-ravendb-cloud) and [Grafana](https://ravendb.net/articles/sending-your-ravendb-7-0-logs-to-grafana-cloud). +This option is more about preventing future problems than about already existing ones. It is that way because external monitoring, as the name suggests, is external, so it needs to be set up before an incident. For RavenDB, we have two monitoring setup guides: [Zabbix](https://ravendb.net/articles/set-up-zabbix-monitoring-for-ravendb-cloud) and [Grafana](./sending-your-ravendb-7-0-logs-to-grafana-cloud). As we said, it’s about preventing future problems. External monitoring can help you set up alarms and dashboards to detect potential problems before they become actual issues. Native RavenDB mechanisms are good until you need long-term logs and dashboards that require customization. diff --git a/guides/sending-your-ravendb-7-0-logs-to-grafana-cloud.mdx b/guides/sending-your-ravendb-7-0-logs-to-grafana-cloud.mdx index b0c91419fb..9d6d1bc73a 100644 --- a/guides/sending-your-ravendb-7-0-logs-to-grafana-cloud.mdx +++ b/guides/sending-your-ravendb-7-0-logs-to-grafana-cloud.mdx @@ -1,8 +1,8 @@ --- -title: "Sending Your RavenDB 7.0 Logs to Grafana Cloud" +title: "Sending Your RavenDB Logs to Grafana Cloud" tags: [monitoring, integration, administration] icon: "grafana" -description: "Route RavenDB 7.0 server logs to Grafana Cloud by configuring the NLog Loki target, then view and filter them in Grafana Explore." +description: "Route RavenDB server logs to Grafana Cloud by configuring the NLog Loki target, then view and filter them in Grafana Explore." published_at: 2025-02-25 author: "Paweł Lachowski" see_also: @@ -39,7 +39,9 @@ import Image from "@theme/IdealImage"; ## Introduction -With RavenDB 7.0, we've introduced the NLog system, bringing log management and monitoring to a whole new level. This upgrade unlocks new and useful NLog integrations, now compatible with RavenDB. In this guide, we will leverage that upgrade, and show you how to connect RavenDB logs to Grafana Cloud using Grafana Loki. You can also use this guide as a reference for connecting your database to other integrations. +RavenDB 7.0 introduced the NLog logging system, bringing log management and monitoring to a whole new level. This upgrade unlocks new and useful NLog integrations, now compatible with RavenDB. In this guide, we will leverage that upgrade, and show you how to connect RavenDB logs to Grafana Cloud using Grafana Loki. You can also use this guide as a reference for connecting your database to other integrations. + +The `settings.json` keys and the `NLog.config` markup shown here apply to RavenDB 7.0 and later, including the current 7.2 release. ## Prerequisites @@ -83,12 +85,12 @@ Let's get back on the topic of setting up connection. We already have most of th { // rest of the settings on top // ... - "Logs.NuGet.AdditionalPackages": { "NLog.Targets.Loki": "2.2.0" }, + "Logs.NuGet.AdditionalPackages": { "NLog.Targets.Loki": "2.5.0" }, "Logs.ConfigPath": "NLog.config", } ``` -It will provide you the required package (**This article is using the 2.2.0 version. Please check if there is a newer version. The latest version is available [here](https://github.com/corentinaltepe/nlog.loki).**) and reroute your NLog settings into a newly created file. The first one is downloading a NuGet package that lets us connect NLog with Loki, while the second one overrides NLog config path. **Keep in mind that RavenDB needs an internet connection to handle everything for you.** +It will provide you the required package (**this guide pins 2.5.0; check [NLog.Targets.Loki on NuGet](https://www.nuget.org/packages/NLog.Targets.Loki) for a newer release before you copy it**) and reroute your NLog settings into a newly created file. The first one is downloading a NuGet package that lets us connect NLog with Loki, while the second one overrides NLog config path. **Keep in mind that RavenDB needs an internet connection to handle everything for you.** ### Step 2: Register the NLog.Loki extension