Merge branch 'develop' into pm-handbook

.github/ISSUE_TEMPLATE/content-issue.md

@@ -10,13 +10,8 @@ assignees: ''
 
 <!-- This repo is public. Anything you share here is visible to the world. -->
 
-### How can we make our docs better?
+## How can we make our docs better?
 
 * Is something confusing?
 * Is something inaccurate or missing?
-* Were you unable to complete a task? (What task?)
-
-### Anything else you'd like to share?
-
-Add other context like screenshots, links to other docs, and information about
-your environment (operating system, application framework, etc.).
+* Were you unable to complete a task? (What task?)

.github/ISSUE_TEMPLATE/site-bug-report.md

@@ -10,29 +10,29 @@ assignees: ''
 diagnose your issue as quickly as possible. This repo is public. Anything you 
 share here is visible to the world. -->
 
-### Description
+## Description
 
 A clear and concise description of what the bug is.
 
-### Steps to reproduce
+## Steps to reproduce
 
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
 
-### Expected behavior
+## Expected behavior
 
 A clear and concise description of what you expected to happen.
 
-### Screenshots
+## Screenshots
 
 If applicable, add screenshots to help explain your problem.
 
-### Additional context
+## Additional context
 
 Add any other context about the problem here.
 
-### Environment
+## Environment
 
 Run `gatsby info --clipboard` in your project directory and paste the output here.

.github/ISSUE_TEMPLATE/site-enhancement.md

@@ -13,18 +13,18 @@ share here is visible to the world. -->
 <!-- DISCLAIMER: Not every feature request will be worked on, but hearing about 
 what you want is important. Don't be afraid to add a feature request! -->
 
-### Is your feature request related to a problem? Please describe
+## Is your feature request related to a problem? Please describe
 
 A clear and concise description of what the problem is.
 
-### Describe the solution you'd like
+## Describe the solution you'd like
 
 A clear and concise description of what you want to happen. What is the expected outcome?
 
-### Describe why this important to you
+## Describe why this important to you
 
 Why should we work on this? What use cases does it support?
 
-### Additional context
+## Additional context
 
 Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -4,15 +4,12 @@
 もしドキュメントの日本語訳で問題を見つけた場合はPRではなくissueを提出してください。
 日本語訳へのPRについてはまだ取り込む準備ができていません。-->
 
-### Give us some context
+Please follow [conventional commit standards](https://www.conventionalcommits.org/en/v1.0.0/)
+in your commit messages and pull request title.
+
+## Give us some context
 
 * What problems does this PR solve?
 * Add any context that will help us review your changes such as testing notes,
   links to related docs, screenshots, etc.
-* If your issue relates to an existing GitHub issue, please link to it.
-
-### Are you making a change to site code?
-
-If you're changing site code (rather than the content of a doc), please follow
-[conventional commit standards](https://www.conventionalcommits.org/en/v1.0.0/)
-in your commit messages and pull request title.
+* If your issue relates to an existing GitHub issue, please link to it.

.github/workflows/auto-comment.yml

@@ -0,0 +1,16 @@
+name: Auto Comment
+on: [issues, pull_request_target]
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: wow-actions/auto-comment@v1
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          pullRequestOpened: |
+            Hi @{{ author }} 👋
+            Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.
+
+          issuesOpened: |
+            Hi @{{ author }} 👋
+            Thank you for filing an issue! We'll triage your issue and let you know if we have questions, and then route it to the appropriate team so we can get it solved.

README.md

@@ -26,13 +26,13 @@ Issues are a quick way to give us feedback about our docs. We'll review your iss
 
 If you'd like to get more directly involved, you can edit the docs yourself! Here's how:
 
-1. Every doc page on docs.newrelic.com has an **Edit page** button in the right sidebar and the footer. Click it to get started making a change. This will take you to GitHub and the source file for that doc page. 
+1. Every doc page on docs.newrelic.com has an **Edit page** button in the right sidebar and the footer. Click it to get started making a change. This will take you to GitHub and the source file for that doc page.
 2. Edit the file by clicking on the pencil icon. Make your changes, then click **Commit changes**. This will automatically create a fork in your GitHub account with the changes.
 3. Finally, follow the prompts to create a pull request and submit your changes for review. From there our writers will check out your pull request, comment with any feedback, and merge your change.
 
 If you'd like more information on how to edit our docs, see our [content contribution guide](https://docs.newrelic.com/docs/style-guide/writing-guidelines/create-edit-content/). Additionally, our [Style guide](https://docs.newrelic.com/docs/style-guide) will give you some insight into how we think about writing and documentation, as well as our flavor of Markdown.
 
-Reading the style guide is totally optional! Our writers are here to make sure everything is formatted and worded right. We're looking your technical insight and knowhow. Let us handle the little details for you.
+Reading the style guide is totally optional! Our writers are here to make sure everything is formatted and worded right. We're looking for your technical insight and knowhow. Let us handle the little details for you.
 
 If you'd like to go deeper with development, see our [Contributors guide](CONTRIBUTING.md) for information on how to fork our site, build it locally, and submit pull requests.
 

gatsby-config.js

@@ -50,6 +50,7 @@ module.exports = {
     {
       resolve: '@newrelic/gatsby-theme-newrelic',
       options: {
+        oneTrustID: 'e66f9ef1-3a12-4043-b7c0-1a2ea66f6d41',
         forceTrailingSlashes: true,
         layout: {
           contentPadding: '2rem',
@@ -183,6 +184,7 @@ module.exports = {
           },
         },
         tessen: {
+          tessenVersion: '1.14.0',
           product: 'DOC',
           subproduct: 'TDOC',
           segmentWriteKey: 'AEfP8c1VSuFxhMdk3jYFQrYQV9sHbUXx',
@@ -196,13 +198,6 @@ module.exports = {
             }),
           },
         },
-        googleTagManager: {
-          trackingId: 'UA-3047412-33',
-          src: 'https://www.googletagmanager.com/gtag/js',
-          options: {
-            anonymize_ip: true,
-          },
-        },
       },
     },
     {

package.json

@@ -9,7 +9,7 @@
     "@github-docs/frontmatter": "^1.3.1",
     "@mdx-js/mdx": "^2.0.0-next.8",
     "@mdx-js/react": "^2.0.0-next.8",
-    "@newrelic/gatsby-theme-newrelic": "^2.5.2",
+    "@newrelic/gatsby-theme-newrelic": "^3.1.2",
     "@splitsoftware/splitio-react": "^1.2.4",
     "babel-jest": "^26.3.0",
     "common-tags": "^1.8.0",

src/content/docs/accounts/accounts-billing/account-setup/troubleshoot-new-relics-password-email-address-login-problems.mdx

@@ -43,22 +43,22 @@ New Relic requires a valid email address and a [valid password](/docs/accounts-p
     4. When you receive a confirmation email from New Relic, select the password reset link, and [follow New Relic's password requirements](/docs/accounts-partnerships/accounts/account-maintenance/change-passwords-user-preferences#requirements) to complete the process to reset your password.
 
     <Callout variant="important">
-      The password reset link expires after 12 hours. If you do not quickly receive an email from New Relic, check your [spam filters](/docs/accounts-partnerships/accounts/account-setup/create-your-new-relic-account#email-whitelist), contact your organization's email administrator for troubleshooting suggestions, get support at [support.newrelic.com](https://support.newrelic.com), or send an email to `account_recovery@newrelic.com`.
+      The password reset link expires after 12 hours. If you do not quickly receive an email from New Relic, check your [spam filters](/docs/accounts-partnerships/accounts/account-setup/create-your-new-relic-account#email-whitelist), contact your organization's email administrator for troubleshooting suggestions, get support at [support.newrelic.com](https://support.newrelic.com).
     </Callout>
   </Collapser>
 
   <Collapser
     id="reset-password"
     title="Reset password."
   >
-    If you forgot your own password or need to request a password reset for your account email, you can use New Relic's [self-service options](#forgot-password). Admin-level users cannot reset passwords for other users. If you need to reset someone else's password, get support at [support.newrelic.com](https://support.newrelic.com), or send an email to `account_recovery@newrelic.com`.
+    If you forgot your own password or need to request a password reset for your account email, you can use New Relic's [self-service options](#forgot-password). Admin-level users cannot reset passwords for other users. If you need to reset someone else's password, get support at [support.newrelic.com](https://support.newrelic.com).
   </Collapser>
 
   <Collapser
     id="account-login-errors"
     title="Password error messages."
   >
-    If you complete the signup process and are unable to log in to your account due to password error messages, get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    If you complete the signup process and are unable to log in to your account due to password error messages, get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 
   <Collapser
@@ -68,7 +68,7 @@ New Relic requires a valid email address and a [valid password](/docs/accounts-p
     If you want to change your password but you see a message that the password reset link expired, try using a private browser or clearing your browser cache and cookies.
 
     <Callout variant="important">
-      The password reset link expires after 12 hours. If you do not quickly receive an email from New Relic after you select the reset link, check your [spam filters](/docs/accounts-partnerships/accounts/account-setup/create-your-new-relic-account#email-whitelist), contact your organization's email administrator for troubleshooting suggestions, get support at [support.newrelic.com](https://support.newrelic.com), or send an email to `account_recovery@newrelic.com`.
+      The password reset link expires after 12 hours. If you do not quickly receive an email from New Relic after you select the reset link, check your [spam filters](/docs/accounts-partnerships/accounts/account-setup/create-your-new-relic-account#email-whitelist), contact your organization's email administrator for troubleshooting suggestions, get support at [support.newrelic.com](https://support.newrelic.com).
     </Callout>
   </Collapser>
 
@@ -99,21 +99,21 @@ New Relic requires a valid email address and a [valid password](/docs/accounts-p
     If you don't receive an email from New Relic:
 
     * Check your [spam filters](/docs/accounts-partnerships/accounts/account-setup/create-your-new-relic-account#email-whitelist). If applicable, [add New Relic to your email allow list](/docs/accounts/accounts/account-maintenance/account-email-settings#email-whitelist).
-    * Get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    * Get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 
   <Collapser
     id="forgot-email"
     title="Email address does not work or email error messages."
   >
-    If you complete the signup process and are unable to log in to your account due to email or password error messages, get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    If you complete the signup process and are unable to log in to your account due to email or password error messages, get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 
   <Collapser
     id="account-exists"
     title="Received message that your email account already exists."
   >
-    If you are trying to create a new account and receive a message that your email account already exists, get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    If you are trying to create a new account and receive a message that your email account already exists, get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 
   <Collapser
@@ -129,7 +129,7 @@ New Relic requires a valid email address and a [valid password](/docs/accounts-p
       **Private browsing**, also known as **incognito mode**, is a privacy feature to disable browsing history and the web cache. To open a private browsing window, you can use the keyboard shortcut `CTRL+Shift+N` on Windows and `Command+Shift+N` on Mac for most browsing applications.
     </Callout>
 
-    If this still doesn't solve your problem, get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    If this still doesn't solve your problem, get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 
   <Collapser
@@ -172,7 +172,7 @@ Some general system problems and solutions:
 
     * Bypass your password manager.
     * Use a different browser to sign up with New Relic.
-    * Get support at [support.newrelic.com](https://support.newrelic.com/home), or send an email to `account_recovery@newrelic.com`.
+    * Get support at [support.newrelic.com](https://support.newrelic.com/home).
   </Collapser>
 </CollapserGroup>
 

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-users/usage-queries-alerts.mdx

@@ -166,7 +166,7 @@ Here are some user-related query examples. For details on how users are counted,
 To help [manage your billable data](/docs/telemetry-data-platform/get-data-new-relic/manage-data/manage-your-data), you can set alerts to notify you of unexpected increases in usage. Learn how to create alerts with [NRQL queries here](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/#create).
 
 <Callout variant="caution">
-  When creating alert conditions, you should set the [Evaluation offset](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions#evaluation-offset) value to 60 minutes or your conditions may not trigger.
+  When creating alert conditions, you should use the Event Timer method, which works very well with infrequent data.
 </Callout>
 
 Here are some NRQL alert condition examples. For attribute definitions, see [Attributes](#attributes).

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles.mdx

@@ -38,7 +38,7 @@ To see if you can access these user management features, go to the [user managem
 
 For users on the [New Relic One user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model/#user-models), to find your user management options: From the [account dropdown](/docs/using-new-relic/welcome-new-relic/get-started/glossary#account-dropdown), select **Administration**. There are two user management UI pages there: 
 
-* **User management**: Use this to add users, update user information, and approve [upgrade requests](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#session-mgmt).
+* **User management**: Use this to add users, [update user type](#edit-user-type) (basic versus full user) and other information, and approve [user type upgrade requests](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#session-mgmt).
 * **Organization and access**: Use this page to create and manage groups, roles, and access grants, and to set up [SAML SSO and SCIM provisioning](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more).
 
 Want to see videos of the user management UI in action? See our [user management videos](/docs/accounts/accounts-billing/new-relic-one-user-management/user-mgmt-videos).
@@ -94,6 +94,28 @@ Here are some example user management procedures:
 
 See the [user management tutorial](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model#add-users).
 
+  </Collapser>
+
+    <Collapser
+    id="edit-user-type"
+    title="Edit user type (basic user versus full user)"
+  >
+
+Note that there are [limits around how many times full users can be changed to basic users](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/#user-count). 
+
+<Callout variant="important">
+If you're using [automated user management](/docs/accounts/accounts/automated-user-management/automated-user-provisioning-single-sign) to provision and manage your users, you have [other options for managing user type](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#user-upgrade). 
+</Callout>
+
+To change the user type of one or more users: 
+
+1. On the [**User management** page](#find), click the checkboxes for the users whose user type you want to edit. 
+2. Once you start selecting users, an option will appear for **Edit type**. 
+
+You can also edit the user type and group of a specific user by clicking on that user. 
+
+![New Relic user management UI - edit user type](./images/user-management-edit-user-type.png "Edit user type in the UI")
+
   </Collapser>
 
   <Collapser

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx

@@ -193,11 +193,13 @@ Our default functionality is to manage user type from New Relic. This is the opt
 
 Our [SCIM API](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim#manage-user-type) lets you manage user type (basic user versus full user) from your identity provider instead of in the New Relic user management UI. **When you enable this, you can no longer change or manage your users' user type from New Relic.**
 
+To enable this setting, your authentication domain **Source of users** must have [SCIM enabled](#source-users). 
+
 Currently, we only have instructions for [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration). For other identity provider services, you can configure your identity provider to send us user type using our [SCIM API user type specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type).
 
-Notes on using this: 
-* To enable this setting, your authentication domain **Source of users** section must have [SCIM enabled](#source-users). 
-* When you enable **Manage user type with SCIM**, you're prompted to create a custom URL and message that basic users see when they go to New Relic UI pages not available to them. That custom message helps them understand your specific process for upgrading. 
+How basic users' requests to become full users are handled: 
+* When you enable **Manage user type with SCIM**, the default option is that your basic users are shown a message explaining that they need to "reach out to your manager or IT department" to become full users. 
+* Optionally, you can customize that message and add a link to a customized page. For example, you might add a custom message that explains to contact a specific person or department. Or you might use our [SCIM API specifications](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim/#manage-user-type) to set up an implementation that programmatically handles user type change requests and automatically changes basic users to full users. 
 
 </Collapser>