docs: Add logging infrastructure guide for Kubernetes deployments

[JAORMX]

• Add comprehensive logging infrastructure documentation covering standard and audit logs
• Document log format specifications with field definitions
• Include configuration examples for operator and MCPServer resources
• Add log collection strategies and enterprise tool integration (ELK, Splunk, Datadog)
• Update sidebar navigation to include the new guide
• Add contextual reference from deploy-operator-helm.md

Addresses: https://github.com/stacklok/toolhive-enterprise/issues/39

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs-website	Ready	Preview	Comment	Sep 12, 2025 9:02am

[Copilot]

Pull Request Overview

This PR adds comprehensive logging infrastructure documentation for ToolHive Kubernetes deployments, covering standard application logs and audit logs for security and compliance monitoring.

Key changes:

• Comprehensive logging guide covering log formats, configuration, and enterprise tool integration
• Audit logging specifications with detailed field definitions and event types
• Log collection strategies using Kubernetes native tools and enterprise systems (ELK, Splunk, Datadog)

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 10 comments.

File	Description
sidebars.ts	Add logging infrastructure guide to the Kubernetes guides section
docs/toolhive/guides-k8s/logging-infrastructure.md	New comprehensive guide covering logging setup, configuration, parsing, and enterprise integrations
docs/toolhive/guides-k8s/deploy-operator-helm.md	Add contextual reference to the new logging infrastructure guide

[danbarr]

@JAORMX Is this still a WIP? The build is failing because the next steps section links to nonexistent pages.

[JAORMX]

Ah, I can't see the logs of the build.

[danbarr]

Ah, I can't see the logs of the build.

Oh, right. The dev server (npm run start) just warns about broken links, but the production build fails out. You can run npm run build locally / in the dev container to see the same thing that Vercel is running, it'll tell you exactly what/where the broken links are.

[JAORMX]

Gotcha, I'll fix it tomorrow