Contributors: mboynes
Tags: alleyinteractive, wp-new-relic-transactions
Stable tag: 0.1.0
Requires at least: 5.9
Tested up to: 6.1
Requires PHP: 8.0
License: GPL v2 or later
A companion plugin when using New Relic with WordPress, to improve the recorded transaction data.
You can install the package via composer:
composer require alleyinteractive/wp-new-relic-transactionsSimply activate the plugin in WordPress, no further action is necessary.
This plugin will name the requests, and apply the given custom attributes/parameters:
| Request type | Transaction Name |
|---|---|
| homepage and front page | homepage |
| feed | feed or feed.{feed type} |
| embed | embedParam: embed |
| 404 | error.404 |
| search | searchParam: s |
| privacy policy | privacy_policy |
| post type archive | archive.post_type.{post type} |
| taxonomy archive | taxonomy or taxonomy.{taxonomy}Params: term_id, slug |
| attachment | attachment |
| single post | post or post.{post type}Param: post_id |
| author archive | archive.author |
| date archive | archive.date |
| misc archive | archive |
| REST API request | {VERB} {Route}Params: wp-api = true, wp-api-route |
REST API requests get a special formatting. When possible, dynamic portions of the URL are replaced with angle brackets surrounding the name of the parameter. Further, the HTTP verb is included in the name.
For instance: GET /wp/v2/posts/\<id\>
In addition to the above, requests should also include the following attributes/parameters for non-REST requests:
logged-in: Is the user logged in or notpaged:trueif the request is pagedpage: The page number if the request is paged
Please see CHANGELOG for more information on what has changed recently.
This project is actively maintained by Alley Interactive. Like what you see? Come work with us.
The GNU General Public License (GPL) license. Please see License File for more information.