docs(logging): Add a basic usage example and tutorial

docs/plugins/wpgraphql-logging/tutorial/learn-logging/index.md

@@ -1,73 +1,202 @@
 ---
-title: "Tutorial Learn WPGRaphQL Logging Plugin"
-description: "Learn how to install and configure the WPGraphQL Logging Plugin, then customize it using its extensible architecture."
+title: "Get Started with WPGraphQL Logging"
+description: "Learn how to install and configure the WPGraphQL Logging plugin, view logged data, and extend it with custom context data."
 ---
 
-@TODO
+In this tutorial, you will install and configure the WPGraphQL Logging plugin to track GraphQL queries in your WordPress site. By the end, you will have a working logging system that captures query data, and you will know how to extend it with custom context data.
 
-## Introduction
+We will use WPGraphQL IDE to run queries, view logs in the WordPress admin, and write PHP code to extend the plugin's functionality.
 
-This tutorial will guide you through the core features of the WPGraphQL Logging Plugin. You will install and set up the plugin, and then you will see log data appear instantly.
+> [!TIP]
+> This tutorial assumes you're working with a local WordPress development environment. If you don't have one, you can set one up using [Local](https://localwp.com/).
 
-Next, we will extend the plugin by:
+## What you'll build
 
-- Subscribing to an event to add more context data
-- Displaying this new data on the admin grid
-- Adding a rule to the list of rules for the rule manager
-- Writing data to a new file handler
+By following this tutorial, you will create:
 
+* A working WPGraphQL Logging setup that tracks GraphQL queries
+* Custom context data added to logs using the event system
+* A configured admin interface to view and filter logged queries
 
-By the end of this tutorial, you will be able to navigate and configure the plugin, and you will have the confidence to extend its functionality to suit your specific needs.
+## Prerequisites
 
-### Prerequisites
+Before starting, make sure you have:
 
-In order to complete this tutorial, you should:
+* WordPress 6.5 or higher installed
+* PHP 8.1.2 or higher
+* WPGraphQL 2.3 or higher installed and activated
+* Basic familiarity with WordPress, WPGraphQL, and PHP
+* The ability to add PHP code to a custom plugin or theme's functions.php
 
-- Be familiar with WordPress, WPGraphQL & PHP
-- Be familiar with installing a plugin for WordPress
-- Be comfortable to be able to add PHP code to a custom plugin
+## Step 1: Install the WPGraphQL Logging plugin
 
-Before you get started you need the following 
+First, we will install the WPGraphQL Logging plugin. Since this plugin extends WPGraphQL, make sure you have WPGraphQL installed and activated before proceeding.
 
+Download the latest release from the GitHub repository:
 
-## Setup
+Visit <https://github.com/wpengine/hwptoolkit/releases/latest/download/wpgraphql-logging.zip> and download the plugin zip file.
 
+Install and activate the plugin through your WordPress admin.
 
-### 1. Install the Plugin
+![WordPress plugins page showing WPGraphQL Logging plugin activated with a blue "Deactivate" link, alongside the WPGraphQL plugin also showing as active](../screenshots/logging-plugin-installed.png)
 
-### 2. Setup the configuration
+## Step 2: Configure the logging plugin
 
+Now we will configure the logging settings to start capturing queries.
 
-## Logging & Viewing Data
+In WordPress admin, go to GraphQL Logs > Settings.
 
-- Using WPGraphQL IDE
-- Logging a query
-- Show the user
+You should see the Basic Configuration tab with several settings. Notice the default configuration:
 
+* **Enabled**: Checked (logging is on)
+* **Exclude Queries**: `__schema,GetSeedNode` (to skip introspection queries)
+* **Data Sampling Rate**: 10% (only logs 10% of queries by default)
+* **Log Points**: All events selected
 
-## Extending and adding data to the logs
+![GraphQL Logs Settings page showing the Basic Configuration tab with default settings including Enabled checkbox checked, Exclude Queries field populated with "__schema,GetSeedNode", and Data Sampling Rate dropdown showing "10% (Every 10th request)"](../screenshots/logging-plugin-settings.png)
 
-### Event
+Let's adjust the sampling rate so we see logs more consistently:
 
-### Admin Grid
+1. Find the "Data Sampling Rate" dropdown
+2. Change it to "100% (All requests)"
+3. Scroll down and click "Save Changes"
 
+You should see a success message confirming your settings were saved.
 
-### Add Configuration
+## Step 3: Generate log entries
 
-### Rule Manager
+Now we will run some GraphQL queries to generate log data.
 
+Go back to GraphQL > GraphiQL IDE.
 
-### Updating the handler
+Run the following query:
 
+```graphql
+query GetPosts {
+  posts(first: 3) {
+    nodes {
+      id
+      title
+      date
+    }
+  }
+}
+```
 
+Click the "Play" button. You should see your posts in the response.
 
-## Conclusion
+Now run a different query:
 
+```graphql
+query GetPages {
+  pages(first: 3) {
+    nodes {
+      id
+      title
+      content
+    }
+  }
+}
+```
 
+Notice how we're running queries with named operations (`GetPosts` and `GetPages`). These names will help us identify queries in the logs.
 
+## Step 4: View your logs
 
+Let's look at the logged query data.
 
+In WordPress admin, go to GraphQL Logs > All Logs.
 
-## Contributing
+You should see a table displaying your logged queries. Each row represents one GraphQL query execution.
 
-We welcome and appreciate contributions from the community. If you'd like to help improve this documentation, please check out our [Contributing Guide](https://github.com/wpengine/hwptoolkit/blob/main/CONTRIBUTING.md) for more details on how to get started.
+![All Logs page showing a table with logged GraphQL query entries](../screenshots/logging-plugin-all-logs.png)
+
+Notice the information captured for each log entry:
+
+* **Date**: When the query was executed
+* **Query**: The query itself (GetPosts, GetPages)
+* **Level**: The log level (usually INFO for successful queries)
+* **Event**: Which point in the request lifecycle was logged
+
+Click on any log entry to see more details. You should see a detail view with the full query text, variables (if any), and additional context data.
+
+![Log entry details page showing full query text, variables, and context data](../screenshots/logging-plugin-details.png)
+
+## Step 5: Add custom context data to logs
+
+Now we will extend the logging system by adding custom context data to each log entry.
+
+The plugin uses an event system that allows you to transform log payloads before they're saved. We will subscribe to an event and add custom data.
+
+> [!TIP]
+> For more detailed information about the event system and available events, see the [How To: Add Data to an Event](../../how-to/event-add-context/index.md) guide.
+
+Create a custom plugin file or add to your theme's `functions.php`:
+
+```php
+<?php
+use WPGraphQL\Logging\Plugin;
+use WPGraphQL\Logging\Events\Events;
+use Monolog\Level;
+
+// Add custom context to the PRE_REQUEST event
+add_action( 'init', function() {
+    Plugin::transform( Events::PRE_REQUEST, function( array $payload ): array {
+        $payload['context']['environment'] = wp_get_environment_type();
+        $payload['context']['app_id']      = 'my-headless-app';
+
+        // Optional: change the log level for this specific event
+        $payload['level'] = Level::Error;
+
+        return $payload;
+    }, 10 );
+} );
+```
+
+This code subscribes to the `PRE_REQUEST` event and adds custom context data to the log:
+* `environment`: The current WordPress environment type (production, staging, development, or local)
+* `app_id`: A custom identifier for your application (useful when logging from multiple apps)
+* `level`: Changes the log level to Error for this event (optional demonstration)
+
+The transform function runs during the `init` action, modifying the payload before it's logged. Notice how we use the `Plugin::transform()` helper method and the `Events::PRE_REQUEST` constant to target a specific lifecycle event.
+
+Save your file and refresh your WordPress site to ensure the code is loaded.
+
+## Step 6: Test the custom context data
+
+Let's verify that our custom context data is being added to logs.
+
+Go back to GraphQL > GraphiQL IDE and run another query:
+
+```graphql
+query TestCustomContext {
+  posts(first: 1) {
+    nodes {
+      title
+    }
+  }
+}
+```
+
+Now go to GraphQL Logs > All Logs.
+
+You should see your new `TestCustomContext` queries. Find the one with "WPGraphQL Pre Request" event and click on it to view the details.
+
+In the context data section, you should now see your custom fields:
+
+![Log entry detail showing custom context fields including environment, app_id, and the modified log level (Error) alongside standard context data](../screenshots/logging-plugin-extra-context.png)
+
+Notice how your custom data appears alongside the default context data like memory usage and request information. Also note that the log level changed to "Error" because we modified it in the transform function. This demonstrates how easily you can extend the logging system to capture application-specific data and even modify logging behavior dynamically.
+
+## Next steps
+
+Now that you have a working WPGraphQL Logging setup and understand how to extend it, you can:
+
+* Add more sophisticated custom context data based on your application's needs - see [How To: Add Data to an Event](../../how-to/event-add-context/index.md)
+* Create custom rules that check configuration values or query patterns - see [How To: Add or Remove a Rule](../../how-to/logger-add-remove-rules/index.md)
+* Export logs to CSV for offline analysis
+* Configure data retention policies in the Data Management tab
+* Add custom processors to transform log data - see [How To: Add a Processor](../../how-to/logger-add-processor/index.md)
+* Implement custom handlers to send logs to external services - see [How To: Add a Handler](../../how-to/logger-add-handler/index.md)
+
+For more details about extending the plugin, see the [How-To Guides](https://github.com/wpengine/hwptoolkit/tree/main/docs/plugins/wpgraphql-logging) which include guides for adding custom processors, handlers, and admin interface customizations.

plugins/wpgraphql-logging/.gitignore

@@ -56,3 +56,6 @@ tests/_data/
 
 # Playwright outputs
 artifacts
+
+# Keep example SQL files
+!examples/**/*.sql

plugins/wpgraphql-logging/examples/wpgraphql-logging-nextjs/.wp-env.json

@@ -0,0 +1,23 @@
+{
+  "phpVersion": "8.1",
+  "plugins": [
+    "https://github.com/wp-graphql/wp-graphql/releases/latest/download/wp-graphql.zip",
+    "https://github.com/wpengine/hwptoolkit/releases/latest/download/wpgraphql-logging.zip"
+  ],
+  "config": {
+    "WP_DEBUG": true,
+    "SCRIPT_DEBUG": false,
+    "GRAPHQL_DEBUG": true,
+    "WP_DEBUG_LOG": true,
+    "WP_DEBUG_DISPLAY": false,
+    "SAVEQUERIES": false
+  },
+  "mappings": {
+    "db": "./wp-env/db",
+    "wp-content/uploads": "./wp-env/uploads",
+    ".htaccess": "./wp-env/setup/.htaccess"
+  },
+  "lifecycleScripts": {
+    "afterStart": "wp-env run cli -- wp rewrite structure '/%postname%/' && wp-env run cli -- wp rewrite flush"
+  }
+}