MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20250829103957|73",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 83,
"ns": 0,
"title": "Connecting to a Kubernetes Pod for JMX Debugging",
"pageid": 72,
"logpage": 72,
"revid": 335,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-09-05T10:42:02Z",
"comment": "Created page with \"= Connecting to a Kubernetes Pod for JMX Debugging = This guide provides a comprehensive walkthrough for developers to permanently configure access to a Kubernetes cluster and connect to a Java application for JMX monitoring. This method is suitable for long-term development and debugging needs. The process involves three main stages: # Installing the Kubernetes command-line tool, '''kubectl'''. # Configuring permanent access to the cluster by merging the provided '''k...\""
},
{
"logid": 82,
"ns": 0,
"title": "Diagnosing Resource Issues in a Kubernetes Cluster",
"pageid": 71,
"logpage": 71,
"revid": 332,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-09-04T12:08:55Z",
"comment": "Created page with \"== Diagnosing Resource Issues in a Kubernetes Cluster == This guide provides a systematic approach to identifying and diagnosing CPU and memory resource problems within a Kubernetes cluster. It covers checking node and pod resource utilization, from a cluster-wide overview to a detailed analysis of a single node. === 1. Prerequisite: Install the Metrics Server === The <code>kubectl top</code> command is the primary tool for checking real-time resource usage. This comman...\""
},
{
"logid": 81,
"ns": 0,
"title": "Setting Up a WireGuard Client with Policy-Based Routing on OpenWrt",
"pageid": 70,
"logpage": 70,
"revid": 331,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-09-02T20:20:54Z",
"comment": "Created page with \"== Setting Up a WireGuard Client with Policy-Based Routing on OpenWrt == This guide outlines how to configure an OpenWrt router to connect to a commercial or private WireGuard VPN as a client and then use Policy-Based Routing (PBR) to selectively route traffic from specific devices on your LAN through the VPN tunnel. This allows some devices to benefit from the VPN while others use the standard, faster WAN connection. === 1. Install Required Packages === First, connect...\""
},
{
"logid": 80,
"ns": 0,
"title": "Solving VPN-Related Network Timeouts on OpenWrt",
"pageid": 69,
"logpage": 69,
"revid": 329,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-09-02T20:17:43Z",
"comment": "Created page with \"== Solving VPN-Related Network Timeouts on OpenWrt == This guide documents the diagnosis and resolution of a common network issue: intermittent connection timeouts for specific services when traffic is routed through a VPN tunnel (e.g., WireGuard, ZeroTier) on an OpenWrt router. The root cause is a Path MTU Discovery (PMTUD) black hole, and the solution is to enable TCP MSS Clamping in the firewall. === 1. The Problem: Connection Timeouts and Stalls === The primary symp...\""
},
{
"logid": 79,
"ns": 0,
"title": "Monitor Proxmox with Prometheus Exporter on Kubernetes",
"pageid": 68,
"logpage": 67,
"revid": 327,
"params": {
"target_ns": 0,
"target_title": "Monitoring PVE 8 via Prometheus on Kubernetes"
},
"type": "move",
"action": "move",
"user": "Gyurci08",
"timestamp": "2025-08-29T17:26:05Z",
"comment": ""
},
{
"logid": 78,
"ns": 0,
"title": "Monitor Proxmox with Prometheus Exporter on Kubernetes",
"pageid": 68,
"logpage": 67,
"revid": 309,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-08-29T13:32:21Z",
"comment": "Created page with \"== Monitor Proxmox with Prometheus Exporter on Kubernetes == This guide outlines how to deploy the `prometheus-pve-exporter` to a Kubernetes cluster to monitor a remote Proxmox VE host using a secure API token. This is the recommended authentication method. The process involves a minimal, one-time setup on the Proxmox host and the deployment of a single multi-document YAML file to Kubernetes. === 1. Create a Read-Only User and API Token on Proxmox === The only action re...\""
},
{
"logid": 77,
"ns": 0,
"title": "Monitoring a macOS Host with Prometheus Node Exporter",
"pageid": 66,
"logpage": 62,
"revid": 307,
"params": {
"target_ns": 0,
"target_title": "Monitoring a MacOS Host with Prometheus Node Exporter"
},
"type": "move",
"action": "move",
"user": "Gyurci08",
"timestamp": "2025-08-29T11:08:47Z",
"comment": ""
},
{
"logid": 76,
"ns": 0,
"title": "Create macOS gitlab-runner",
"pageid": 65,
"logpage": 32,
"revid": 304,
"params": {
"target_ns": 0,
"target_title": "Create MacOS gitlab-runner"
},
"type": "move",
"action": "move",
"user": "Gyurci08",
"timestamp": "2025-08-29T11:07:56Z",
"comment": ""
},
{
"logid": 75,
"ns": 14,
"title": "Category:GitLab",
"pageid": 64,
"logpage": 64,
"revid": 303,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-08-29T11:06:03Z",
"comment": "Created page with \"[[Category:Automation & Tooling]]\""
},
{
"logid": 74,
"ns": 0,
"title": "MacOS Services",
"pageid": 63,
"logpage": 63,
"revid": 296,
"params": {},
"type": "create",
"action": "create",
"user": "Gyurci08",
"timestamp": "2025-08-29T10:50:17Z",
"comment": "Created page with \"[[Category:MacOS]] == macOS Services (launchd) == === Description === On macOS, `launchd` is the system-wide service manager that starts, stops, and manages daemons and agents. You can interact with it using the `launchctl` command-line tool. Services are defined in two main types: * '''LaunchAgents''': These are executed for a specific user only when that user logs into a graphical session. * '''LaunchDaemons''': These are invoked when the system boots and run indepen...\""
}
]
}
}