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": "20251229060538|4016",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 4026,
"ns": 0,
"title": "Standard Procedure for Managed Switch Firmware Upgrade",
"pageid": 0,
"logpage": 2431,
"params": {},
"type": "delete",
"action": "delete",
"user": "Saurabh",
"timestamp": "2026-01-07T07:20:38Z",
"comment": "content was: \"= Switch Firmware Upgrade Procedure = == 1. Purpose == This document provides a standardized firmware upgrade procedure for managed network switches deployed across customer and internal environments. The objective is to ensure secure, stable, and consistent firmware management while minimizing service disruption, configuration loss, and operational risk. The procedure defines m...\", and the only contributor was \"[[Special:Contributions/Kalyan|Kalyan]]\" ([[User talk:Kalyan|talk]])"
},
{
"logid": 4025,
"ns": 0,
"title": "Step-by-Step Firmware Upgrade Procedure for Managed Network Switches (Including TP-Link Switches as example)",
"pageid": 2433,
"logpage": 2433,
"params": {},
"type": "create",
"action": "create",
"user": "Jamshad",
"timestamp": "2026-01-07T06:53:59Z",
"comment": "Created page with \"'''Purpose''' This document outlines a standardized procedure for performing firmware upgrades on managed network switches. The procedure is designed to minimize impact on network operations and includes detailed steps for pre-upgrade assessment, configuration backup, firmware upgrade execution, and post-upgrade validation. Additionally, this document provides a vendor-specific example illustrating the upgrade process for TP-Link managed switches. ==Scope== This procedu...\""
},
{
"logid": 4024,
"ns": 0,
"title": "Operational Guide for Per-Policy Bandwidth and Traffic Consumption Analysis on Palo Alto Firewalls",
"pageid": 2432,
"logpage": 2432,
"params": {},
"type": "create",
"action": "create",
"user": "Kalyan",
"timestamp": "2026-01-03T09:59:20Z",
"comment": "Created page with \"= Operational Guide for Per-Policy Bandwidth and Traffic Consumption Analysis on Palo Alto Firewalls = == Purpose == This Knowledge Base explains how to generate and analyze bandwidth usage and per\u2013security policy data consumption on Palo Alto Firewalls. It is useful for tracking traffic related to specific internal servers, applications, or dedicated traffic flows by leveraging ACC \u2192 Network Activity and Traffic Logs. == Scope == This KB covers: * Generating bandw...\""
},
{
"logid": 4023,
"ns": 0,
"title": "Standard Procedure for Managed Switch Firmware Upgrade",
"pageid": 0,
"logpage": 2431,
"params": {},
"type": "create",
"action": "create",
"user": "Kalyan",
"timestamp": "2026-01-03T09:35:50Z",
"comment": "Created page with \"= Switch Firmware Upgrade Procedure = == 1. Purpose == This document provides a standardized firmware upgrade procedure for managed network switches deployed across customer and internal environments. The objective is to ensure secure, stable, and consistent firmware management while minimizing service disruption, configuration loss, and operational risk. The procedure defines mandatory pre-upgrade checks, configuration backup requirements, controlled upgrade execution,...\""
},
{
"logid": 4022,
"ns": 0,
"title": "Configuring SSL VPN User with Full Internal Network Access on FortiGate Firewall",
"pageid": 2430,
"logpage": 2430,
"params": {},
"type": "create",
"action": "create",
"user": "Jamshad",
"timestamp": "2026-01-03T08:26:43Z",
"comment": "Created page with \"'''Purpose''' This article explains how to configure an SSL VPN user with full access to internal networks on a FortiGate firewall. It covers SSL VPN user creation, tunnel configuration, firewall policy setup, validation, and best practices. '''Scope''' * SSL VPN user creation * SSL VPN tunnel configuration * Internal network access using split-tunnel or full-tunnel * Firewall policy configuration * Validation and best practices [[Main_Page|Home]] > Enterprise secu...\""
},
{
"logid": 4021,
"ns": 0,
"title": "Configuring Alerts for a Particular Host Group",
"pageid": 2429,
"logpage": 2429,
"params": {},
"type": "create",
"action": "create",
"user": "Kamal",
"timestamp": "2025-12-31T07:36:19Z",
"comment": "Created page with \"[[Main Page | Home]] > [[Zabbix]] > [[Configuring Alerts for a Particular Host Group]]\""
},
{
"logid": 4020,
"ns": 0,
"title": "Zabbix",
"pageid": 2428,
"logpage": 2428,
"params": {},
"type": "create",
"action": "create",
"user": "Kamal",
"timestamp": "2025-12-31T07:35:38Z",
"comment": "Created page with \"[[Main Page | Home]] > [[Zabbix]] *[[Configuring Alerts for a Particular Host Group]]\""
},
{
"logid": 4019,
"ns": 2,
"title": "User:Bhadreshwar",
"pageid": 0,
"logpage": 0,
"params": {
"userid": 27
},
"type": "newusers",
"action": "create2",
"user": "Saurabh",
"timestamp": "2025-12-30T09:02:24Z",
"comment": ""
},
{
"logid": 4018,
"ns": 0,
"title": "CentOS 7.x Rocks Cluster OpenPBS pbs sched Startup Fix After Reboot",
"pageid": 2427,
"logpage": 2426,
"params": {
"target_ns": 0,
"target_title": "PBS pbs sched Startup Fix After Reboot"
},
"type": "move",
"action": "move",
"user": "Akshay",
"timestamp": "2025-12-29T07:40:51Z",
"comment": ""
},
{
"logid": 4017,
"ns": 0,
"title": "CentOS 7.x Rocks Cluster OpenPBS pbs sched Startup Fix After Reboot",
"pageid": 2427,
"logpage": 2426,
"params": {},
"type": "create",
"action": "create",
"user": "Akshay",
"timestamp": "2025-12-29T07:28:48Z",
"comment": "Created page with \"[[Main Page|Home]] > [[CentOS]] > [[CentOS 7.x]] > [[CentOS 7.x Rocks cluster 7.0]] > [[CentOS 7.x Rocks Cluster OpenPBS pbs_sched Startup Fix After Reboot]] == CentOS 7.x Rocks Cluster OpenPBS pbs_sched Startup Fix After Reboot == '''Background:''' As per the Rocks cluster architecture, the master node has two hostnames: * A '''public hostname''' * A '''private hostname''' In OpenPBS, all scheduler and node communication happens strictly through hostnames. OpenPBS...\""
}
]
}
}