Unify content relation mapping and add traffic analysis FAQ

Author: Haraguroicha

config/case-mapping.yaml config/content-relations.yamlconfig/case-mapping.yaml renamed to config/content-relations.yaml

@@ -1,4 +1,4 @@
-- case: /cases/uia-remote-network
+"/cases/uia-remote-network":
   services:
     - /services/office-network
   faq:
@@ -7,7 +7,7 @@
   tech:
     - /tech/wifi-controller-firmware-schedule
     - /tech/passive-inspection-report-workflow
-- case: /cases/ttw-remote-network
+"/cases/ttw-remote-network":
   services:
     - /services/office-network
     - /services/mdm
@@ -21,7 +21,7 @@
     - /tech/shared-dns-radius-isolation
     - /tech/jamf-trust-vpn-control
     - /tech/vpn-radius-certificate-lifecycle
-- case: /cases/tgw-remote-network
+"/cases/tgw-remote-network":
   services:
     - /services/office-network
     - /services/mdm
@@ -34,7 +34,7 @@
   tech:
     - /tech/jamf-trust-vpn-control
     - /tech/vpn-radius-certificate-lifecycle
-- case: /cases/cay-machine-room
+"/cases/cay-machine-room":
   services:
     - /services/idc-deployment
     - /services/virtualization-cloud
@@ -47,7 +47,7 @@
   tech:
     - /tech/onboarding-account-automation
     - /tech/datacenter-move-ups-improvement
-- case: /cases/jal-pa
+"/cases/jal-pa":
   services:
     - /services/office-network
     - /services/zero-trust
@@ -57,7 +57,7 @@
   tech:
     - /tech/network-license-takeover-checklist
     - /tech/controlled-ap-dual-path
-- case: /cases/cpa-jjp-network-audit
+"/cases/cpa-jjp-network-audit":
   services:
     - /services/office-network
   faq:
@@ -66,7 +66,7 @@
   tech:
     - /tech/it-inventory-recovery-manual
     - /tech/network-audit-template-delivery
-- case: /cases/klm-aua-erp
+"/cases/klm-aua-erp":
   services:
     - /services/virtualization-cloud
     - /services/backup-security
@@ -76,7 +76,7 @@
   tech:
     - /tech/pve-pbs-backup-schedule-validation
     - /tech/pve-quarterly-report-template
-- case: /cases/lgl-csa-vpn
+"/cases/lgl-csa-vpn":
   services:
     - /services/custom-dev
     - /services/zero-trust
@@ -86,15 +86,15 @@
   tech:
     - /tech/custom-app-review-transfer
     - /tech/app-ownership-transfer-process
-- case: /cases/lgl-hda-openvz-pve-eval
+"/cases/lgl-hda-openvz-pve-eval":
   services:
     - /services/virtualization-cloud
   faq:
     - /faq/closed-hypervisor-migration-plan
   tech:
     - /tech/closed-hypervisor-migration-validation
     - /tech/multi-stage-migration-checklist
-- case: /cases/lgl-awe-pve-vgpu-jamf
+"/cases/lgl-awe-pve-vgpu-jamf":
   services:
     - /services/virtualization-cloud
     - /services/mdm
@@ -104,7 +104,7 @@
   tech:
     - /tech/pve-vgpu-rollout-training
     - /tech/jamf-audit-cross-team
-- case: /cases/wzz-network-controller
+"/cases/wzz-network-controller":
   services:
     - /services/office-network
     - /services/hosting-operations
@@ -115,7 +115,7 @@
   tech:
     - /tech/unifi-controller-migration-light-ops
     - /tech/budget-nas-refresh-plan
-- case: /cases/lgl-tax-pve-io-wait
+"/cases/lgl-tax-pve-io-wait":
   services:
     - /services/virtualization-cloud
   faq:
@@ -124,7 +124,7 @@
   tech:
     - /tech/pve-io-wait-diagnostics-workflow
     - /tech/pve-backup-schedule-tuning-guide
-- case: /cases/lgl-cal-jamf-oidc
+"/cases/lgl-cal-jamf-oidc":
   services:
     - /services/mdm
     - /services/iam-zitadel
@@ -134,7 +134,7 @@
   tech:
     - /tech/zitadel-jamf-connect-validation-lab
     - /tech/oidc-test-logs-communication
-- case: /cases/lgl-nax-gpu-passthrough
+"/cases/lgl-nax-gpu-passthrough":
   services:
     - /services/virtualization-cloud
     - /services/it-outsourcing
@@ -144,7 +144,7 @@
   tech:
     - /tech/offline-pve-gpu-passthrough
     - /tech/on-site-troubleshooting-handbook
-- case: /cases/ana-unifi-controller
+"/cases/ana-unifi-controller":
   services:
     - /services/office-network
     - /services/it-outsourcing
@@ -155,7 +155,7 @@
   tech:
     - /tech/unifi-controller-migration-light-ops
     - /tech/budget-nas-refresh-plan
-- case: /cases/cay-server-farm
+"/cases/cay-server-farm":
   services:
     - /services/idc-deployment
     - /services/container-devops
@@ -166,9 +166,7 @@
   tech:
     - /tech/operations-handover-package
     - /tech/it-refresh-migration-blueprint
-    - /tech/akvorado-flow-collector-overview
-    - /tech/akvorado-traffic-analysis-workflow
-- case: /cases/cay-dns-filter
+"/cases/cay-dns-filter":
   services:
     - /services/office-network
     - /services/zero-trust
@@ -178,7 +176,7 @@
   tech:
     - /tech/shared-dns-radius-isolation
     - /tech/remote-inspection-reporting
-- case: /cases/cay-ldap-onboarding
+"/cases/cay-ldap-onboarding":
   services:
     - /services/office-network
     - /services/iam-zitadel
@@ -190,7 +188,7 @@
     - /tech/onboarding-account-automation
     - /tech/operations-handover-package
     - /tech/vpn-radius-certificate-lifecycle
-- case: /cases/cay-azure-erp
+"/cases/cay-azure-erp":
   services:
     - /services/virtualization-cloud
     - /services/backup-security
@@ -200,7 +198,7 @@
   tech:
     - /tech/pve-pbs-backup-schedule-validation
     - /tech/pve-quarterly-report-template
-- case: /cases/ttw-mdm
+"/cases/ttw-mdm":
   services:
     - /services/mdm
   faq:
@@ -209,7 +207,7 @@
   tech:
     - /tech/jamf-audit-cross-team
     - /tech/jamf-trust-vpn-control
-- case: /cases/tgw-mdm
+"/cases/tgw-mdm":
   services:
     - /services/mdm
   faq:
@@ -218,7 +216,7 @@
   tech:
     - /tech/jamf-audit-cross-team
     - /tech/jamf-trust-vpn-control
-- case: /cases/tgw-zero-trust-monitoring
+"/cases/tgw-zero-trust-monitoring":
   services:
     - /services/zero-trust
     - /services/it-monitoring
@@ -228,7 +226,7 @@
   tech:
     - /tech/jamf-trust-vpn-control
     - /tech/remote-inspection-reporting
-- case: /cases/wzz-nas-migration
+"/cases/wzz-nas-migration":
   services:
     - /services/hosting-operations
     - /services/backup-security
@@ -238,7 +236,7 @@
   tech:
     - /tech/budget-nas-refresh-plan
     - /tech/pve-backup-schedule-tuning-guide
-- case: /cases/wzz-contract-strategy
+"/cases/wzz-contract-strategy":
   services:
     - /services/it-outsourcing
     - /services/office-network
@@ -248,3 +246,23 @@
   tech:
     - /tech/operations-handover-package
     - /tech/it-refresh-migration-blueprint
+"/tech/akvorado-flow-collector-overview":
+  services:
+    - /services/it-monitoring
+    - /services/office-network
+    - /services/idc-deployment
+  faq:
+    - /faq/akvorado-vs-snmp-monitoring
+    - /faq/akvorado-data-quality-checks
+  tech:
+    - /tech/akvorado-traffic-analysis-workflow
+"/tech/akvorado-traffic-analysis-workflow":
+  services:
+    - /services/it-monitoring
+    - /services/office-network
+    - /services/idc-deployment
+  faq:
+    - /faq/akvorado-vs-snmp-monitoring
+    - /faq/akvorado-data-quality-checks
+  tech:
+    - /tech/akvorado-flow-collector-overview

docs/content-relations.md

@@ -0,0 +1,9 @@
+# Content Relations
+
+`config/content-relations.yaml` is the single source of truth for case, service, FAQ, and tech relationships. Each top-level key is an absolute content slug, and each value may include:
+
+- `services`: service slugs shown on the source article and used to surface the article from matching service and case pages.
+- `faq`: FAQ slugs shown on the source article and surfaced from matching service and case pages.
+- `tech`: related tech article slugs shown on the source article and used for inverse tech relationships.
+
+Case entries should use their case slug as the top-level key. Tool-focused or educational tech articles should use their tech slug directly instead of being attached to an unrelated case.

src/components/RelationShipArticleList.vue

@@ -5,11 +5,11 @@ import { useI18n } from 'vue-i18n'
 import YAML from 'yaml'
 import FaqArticleCard from './FaqArticleCard.vue'
 import ArticlePreview from './ArticlePreview.vue'
-import mappingRaw from '../../config/case-mapping.yaml?raw'
+import relationsRaw from '../../config/content-relations.yaml?raw'
 import { resolveContentInfo, buildLocalizedPath } from '@/utils/contentIndex'
 import { useFallbackNotice } from '@/composables/useFallbackNotice'
 
-const caseMappings = YAML.parse(mappingRaw) || []
+const relations = YAML.parse(relationsRaw) || {}
 
 const { locale, availableLocales, fallbackLocale } = useI18n()
 const supportedLocales = computed(() => availableLocales || [])
@@ -79,53 +79,92 @@ const detectPageType = (slug) => {
 	return null
 }
 
-const findCaseEntry = (slug) => caseMappings.find((entry) => entry.case === slug)
+const normalizeRelationEntry = (slug, entry = {}) => ({
+	slug,
+	services: toArray(entry.services),
+	faq: toArray(entry.faq),
+	tech: toArray(entry.tech),
+})
+
+const relationEntries = Object.entries(relations).map(([slug, entry]) => normalizeRelationEntry(slug, entry))
+
+const isCaseSlug = (slug) => slug.startsWith('/cases/')
+const isTechSlug = (slug) => slug.startsWith('/tech/')
+
+const findRelationEntry = (slug) => normalizeRelationEntry(slug, relations[slug])
 
-const findCasesByService = (serviceSlug) =>
-	caseMappings.filter((entry) => entry.services?.includes(serviceSlug))
+const findRelationEntriesByService = (serviceSlug) =>
+	relationEntries.filter((entry) => entry.services.includes(serviceSlug))
+
+const findRelationEntriesByTech = (techSlug) =>
+	relationEntries.filter((entry) => entry.tech.includes(techSlug))
+
+const dedupeRelationEntries = (entries) => {
+	const seen = new Set()
+	return entries.filter((entry) => {
+		if (!entry.slug || seen.has(entry.slug)) return false
+		seen.add(entry.slug)
+		return true
+	})
+}
 
-const findCasesByTech = (techSlug) =>
-	caseMappings.filter((entry) => entry.tech?.includes(techSlug))
+const findTechEntriesByServices = (serviceSlugs) =>
+	dedupeRelationEntries(
+		toArray(serviceSlugs)
+			.flatMap((serviceSlug) => findRelationEntriesByService(serviceSlug))
+			.filter((entry) => isTechSlug(entry.slug)),
+	)
 
 const relatedData = computed(() => {
 	const slug = currentSlug.value
 	const type = detectPageType(slug)
 	const localeValue = locale.value
-	//console.log('[RelationShipArticleList] computing relations for', slug, type, localeValue, caseMappings)
+	//console.log('[RelationShipArticleList] computing relations for', slug, type, localeValue, relations)
 	if (!type) return { cases: [], services: [], tech: [], faq: [] }
 	let caseSlugs = []
 	let serviceSlugs = []
 	let techSlugs = []
 	let faqSlugs = []
-  const serviceEntry = findCasesByService(slug)
-  const caseEntry = findCaseEntry(slug)
-  const techEntry = findCasesByTech(slug)
+	const relationEntry = findRelationEntry(slug)
+	const entriesByService = findRelationEntriesByService(slug)
+	const entriesByTech = findRelationEntriesByTech(slug)
 	switch (type) {
 		case 'service':
-			caseSlugs = serviceEntry.map((entry) => entry.case)
-			faqSlugs = serviceEntry.flatMap((entry) => entry.faq || [])
-			techSlugs = serviceEntry.flatMap((entry) => entry.tech || [])
+			caseSlugs = entriesByService.filter((entry) => isCaseSlug(entry.slug)).map((entry) => entry.slug)
+			faqSlugs = entriesByService.flatMap((entry) => entry.faq)
+			techSlugs = entriesByService.flatMap((entry) =>
+				isTechSlug(entry.slug) ? [entry.slug] : entry.tech,
+			)
 			break;
 		case 'case':
-			if (caseEntry) {
-				serviceSlugs = caseEntry.services || []
-				faqSlugs = caseEntry.faq || []
-				techSlugs = caseEntry.tech || []
-			}
+			serviceSlugs = relationEntry.services
+			faqSlugs = relationEntry.faq
+			techSlugs = relationEntry.tech
+			const serviceTechEntries = findTechEntriesByServices(serviceSlugs)
+			faqSlugs.push(...serviceTechEntries.flatMap((entry) => entry.faq))
+			techSlugs.push(...serviceTechEntries.map((entry) => entry.slug))
 			break;
 		case 'tech':
-			caseSlugs = techEntry.map((entry) => entry.case)
-			serviceSlugs = techEntry.flatMap((entry) => entry.services || [])
-			faqSlugs = techEntry.flatMap((entry) => entry.faq || [])
+			caseSlugs = entriesByTech.filter((entry) => isCaseSlug(entry.slug)).map((entry) => entry.slug)
+			serviceSlugs = entriesByTech
+				.filter((entry) => isCaseSlug(entry.slug))
+				.flatMap((entry) => entry.services)
+			faqSlugs = entriesByTech
+				.filter((entry) => isCaseSlug(entry.slug))
+				.flatMap((entry) => entry.faq)
+			serviceSlugs.push(...relationEntry.services)
+			faqSlugs.push(...relationEntry.faq)
+			techSlugs.push(...relationEntry.tech)
+			techSlugs.push(...entriesByTech.filter((entry) => isTechSlug(entry.slug)).map((entry) => entry.slug))
 			break;
 		default:
 			break;
 	}
 
-	caseSlugs = unique(caseSlugs)
-	serviceSlugs = unique(serviceSlugs)
-	techSlugs = unique(techSlugs)
-	faqSlugs = unique(faqSlugs)
+	caseSlugs = unique(caseSlugs).filter(Boolean)
+	serviceSlugs = unique(serviceSlugs).filter(Boolean)
+	techSlugs = unique(techSlugs).filter(Boolean)
+	faqSlugs = unique(faqSlugs).filter(Boolean)
 
 	//console.log('[RelationShipArticleList] unique relations for', slug, type, localeValue, caseSlugs, serviceSlugs, techSlugs, faqSlugs)
 

src/content/faq/akvorado-data-quality-checks/index.en.md

@@ -0,0 +1,15 @@
+---
+type: faq
+slug: faq/akvorado-data-quality-checks
+title: |
+  What data-quality checks are needed before trusting Akvorado Top Talkers?
+description: |
+  Follow [Akvorado Traffic Analysis Tutorial](/tech/akvorado-traffic-analysis-workflow): confirm exporters keep sending flows, Inlet counters increase, Outlet writes into ClickHouse, and sampling plus SNMP enrichment remain stable.
+ogType: article
+index: false
+deploy: true
+sitemap:
+  priority: 0.4
+  changefreq: monthly
+  lastmod: build
+---