Skip to content

Commit

Permalink
Merge branch 'newrelic:develop' into net-agent-90
Browse files Browse the repository at this point in the history
  • Loading branch information
vuqtran88 committed Sep 7, 2021
2 parents 9af0221 + bbd47a6 commit 4eeb8a7
Show file tree
Hide file tree
Showing 36 changed files with 556 additions and 235 deletions.
9 changes: 8 additions & 1 deletion gatsby-config.js
Expand Up @@ -131,14 +131,21 @@ module.exports = {
return {
q: tags ? tags.map(quote).join(' OR ') : title,
search_fields: {
page: ['tags^10', 'body^5', 'title^1.5', '*'],
page: [
'tags^10',
'quick_start_name^8',
'body^5',
'title^1.5',
'*',
],
},
filters: {
page: {
type: [
`docs${postfix}`,
`developer${postfix}`,
`opensource${postfix}`,
`quick_starts${postfix}`,
],
document_type: [
'!views_page_menu',
Expand Down
Expand Up @@ -75,7 +75,7 @@ To create a new domain from the authentication domain UI page, click **Create ne
From the [authentication domain UI](#ui), you can set one of two options for how users are added to New Relic:

* **Manual:** This means that your users are added manually to New Relic from the [**User management** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles/#where).
* **SCIM:** Our automated user management (AUM) feature allows you to use SCIM provisioning to import and manage users from your identity provider. For instructions, see [Automated user management](/docs/accounts/accounts/automated-user-management/automated-user-provisioning-single-sign).
* **SCIM:** Our automated user management (AUM) feature allows you to use SCIM provisioning to import and manage users from your identity provider. For instructions, see [Automated user management](/docs/accounts/accounts/automated-user-management/automated-user-provisioning-single-sign).

Note that once you enable SCIM for an authentication domain, you can't turn it off. This means that if you later want SCIM disabled for that domain, you must instead create a new one.

Expand Down Expand Up @@ -169,7 +169,7 @@ In the [authentication domain UI](#ui), under **Management**, you can control so
* [User upgrade requests](#user-upgrade)


## User upgrade requests [#user-upgrade]
## Manage user type [#user-upgrade]

In the [authentication domain UI](#ui), under **Management**, you can control how basic users upgrade to [full users](/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure). You have different options depending on whether you are managing user type in New Relic or via SCIM:

Expand All @@ -178,7 +178,7 @@ In the [authentication domain UI](#ui), under **Management**, you can control ho
id="manage-user-type-new-relic"
title="Manage user type in New Relic (default)"
>
Our default functionality is to manage user type in New Relic. This is the option you'd use if you weren't managing user type via [SCIM](#source-users). These default options include:
Our default functionality is to manage user type in New Relic. This is the option you'd use if you weren't managing user type via [SCIM](#source-users). If this is chosen, your options for managing upgrade requests include:
* Allow basic users to self-upgrade: this allows basic users to be able to quickly upgrade in order to respond to issues.
* Require review by admins (users with the [**Authentication domain manager** role](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/#standard-roles)). With this setting, admins receive an email when an upgrade request is made, and can manage requests in the [**User management** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles/#where).

Expand All @@ -189,7 +189,13 @@ Our default functionality is to manage user type in New Relic. This is the optio
title="Manage user type with SCIM"
>

If you've [enabled SCIM](#source-users) in the authentication domain UI, you can use our [SCIM API](/docs/accounts/accounts/automated-user-management/tutorial-manage-users-groups-scim#manage-user-type) to manage user type. (This is not yet available for the [Azure AD](/docs/accounts/accounts/automated-user-management/azure-ad-scimsso-application-configuration), [Okta](/docs/accounts/accounts/automated-user-management/okta-scimsso-application-configuration), or [OneLogin](/docs/accounts/accounts/automated-user-management/onelogin-scimsso-application-configuration) New Relic apps.) The upgrade request UI allows you to create a custom URL and message that basic users will see when they go to New Relic features that are off limits to them, and that message will help them understand your specific process for upgrading.
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't manage user type from the New Relic side.

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, you must first go to the authentication domain **Source of users** section and [enable SCIM](#source-users).
* When you enable this setting, 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.

</Collapser>

Expand Down
Expand Up @@ -41,8 +41,8 @@ The user type (basic user or full user) determines whether a user has access to
Below are details on the two user types. Note that billing-related aspects only apply if you're on [New Relic One pricing](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-changes-pricing-user-model#pricing-plans).

* **Basic user**. Details:
* These users are free and have access to a wide range of features, including running queries of data, making custom charts and dashboards, and setting up alerts. Unlike full users, they do **not** have access to our Full-Stack Observability features and some advanced Applied Intelligence features (for a comparison of abilities, see [Capabilities](#user-capabilities)).
* Basic users will see prompts for upgrading to a full user when they attempt to access unavailable features. For details, see [Upgrade](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#session-mgmt).
* These users are free and have access to a wide range of features, including setting up and configuring any New Relic data-reporting tool, running queries of your data, using our logs UI, making custom charts and dashboards, and setting up alerts. Unlike full users, they do **not** have access to our Full-Stack Observability features and some Applied Intelligence features (for a detailed comparison, see [Capabilities](#user-capabilities)).
* Basic users will see prompts to become a full user when they attempt to access unavailable features. For details, see [Upgrade](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#session-mgmt).
* **Full user**. Details:
* Full users have access to our Full-Stack Observability features, which include curated UI experiences like APM, infrastructure monitoring, browser monitoring, mobile monitoring, synthetic monitors, access to New Relic One apps, and more. For details, see [Capabilities](#user-capabilities).
* [Standard edition](https://newrelic.com/pricing) includes one free full user and up to five total full users.
Expand Down Expand Up @@ -168,7 +168,7 @@ Below is a table comparing what basic users and full users can do. In short: bas

<tr>
<td>
Logs in context with other UI experiences
Logs in context
</td>

<td className="fcenter">
Expand Down Expand Up @@ -361,7 +361,7 @@ Below is a table comparing what basic users and full users can do. In short: bas

<tr>
<td>
Data ingest from any source (our agents, integrations, and APIs)
Data ingest from any source (agents, integrations, APIs)
</td>

<td className="fcenter">
Expand Down Expand Up @@ -464,7 +464,7 @@ Below is a table comparing what basic users and full users can do. In short: bas

<tr>
<td>
Logs UI
Query and chart log data
</td>

<td className="fcenter">
Expand Down
Expand Up @@ -78,7 +78,12 @@ After saving the provisioning rules, the New Relic SCIM/SSO application is ready

When your users are provisioned in New Relic, you're able to see them in the [**User management** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles/#where).

Users provisioned via your identity provider start out as [full users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type). If your organization is on [New Relic One pricing](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), these users are billable. To convert users to free [basic users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type), use the [User management UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#add-users).
Users provisioned via your identity provider start out as [full users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type). If your organization is on [New Relic One pricing](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), these users are billable.

To convert users to free [basic users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type), you can use one of two options:

* Use the [User management UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#add-users) to set users to basic.
* [Configure the Azure app to send user type.](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#manage-user-type-scim)


## Step 6. Assign access grants [#assign-users]
Expand Down
Expand Up @@ -132,7 +132,12 @@ Assign the New Relic SCIM/SSO application to a user:

When your users are provisioned in New Relic, you're able to see them in the [**User management** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles/#where).

Users provisioned via your identity provider start out as [full users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type). If your organization is on [New Relic One pricing](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), these users are billable. To convert users to free [basic users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type), use the [User management UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#add-users).
Users provisioned via your identity provider start out as [full users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type). If your organization is on [New Relic One pricing](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), these users are billable.

To convert users to free [basic users](/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure#user-type), you can use one of two options:

* Use the [User management UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#add-users) to set users to basic.
* [Configure the OneLogin app to send user type.](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more/#manage-user-type-scim)

## Step 6. Assign access grants [#assign-users]

Expand Down
Expand Up @@ -277,7 +277,21 @@ The following integration packages must be imported along with the [newrelic](ht
</td>

<td>
Instrument database calls to Postgres
Instrument database calls to Postgres using the database/sql library and pq
</td>
</tr>

<tr>
<td>
[jackc/pgx](https://github.com/jackc/pgx)
</td>

<td>
[v3/integrations/nrpgx](https://godoc.org/github.com/newrelic/go-agent/v3/integrations/nrpgx)
</td>

<td>
Instrument database calls to Postgres using the database/sql library and jackc/pgx
</td>
</tr>

Expand Down
Expand Up @@ -68,13 +68,13 @@ For any installation, you will need your New Relic [license key](/docs/subscript
<td>
* AWS Linux 2
* Red Hat Enterprise Linux (RHEL) 5 or higher
* CentOS 5.5 or higher (except 5.6)
* CentOS 6 or higher

<Callout variant="important">
As of January 2021, we will discontinue support for CentOS 5. For more information, see our [PHP agent release notes v9.15.0](/docs/release-notes/agent-release-notes/php-release-notes/php-agent-9150293) and our [Explorers Hub post](https://discuss.newrelic.com/t/important-upcoming-changes-to-capabilities-across-browser-php-python-mobile-and-android-agents/123951).
</Callout>
* Debian 5.0 ("lenny") or higher
* Ubuntu 9.10 ("Karmic Koala") or higher
* Debian 7.0 ("wheezy") or higher
* Ubuntu LTS 14.04 ("Trusty Tahr") or higher or Ubuntu non-LTS 19.04 ("Disco Dingo") or higher.
* Any other Linux distribution with:

* Kernel version 2.6.13 or higher (2.6.26 or higher highly recommended)
Expand Down Expand Up @@ -147,7 +147,7 @@ Supported PHP frameworks include:
<tbody>
<tr>
<td>
CakePHP 1.2, 1.3, and 2.x
CakePHP 2.x
</td>

<td>
Expand All @@ -169,15 +169,11 @@ Supported PHP frameworks include:
<td>
[Drupal 6.x, 7.x, 8.x, and 9.x](/docs/agents/php-agent/frameworks-libraries/drupal-specific-functionality)
</td>

<td>
Silex 1.x and 2.x
</td>
</tr>

<tr>
<td>
Joomla 1.5, 1.6, 2.x, and 3.x
Joomla 3.x
</td>

<td>
Expand All @@ -191,7 +187,7 @@ Supported PHP frameworks include:
</td>

<td>
Symfony 1.x, 2.x, 3.x, 4.x, 5.x
Symfony 3.x, 4.x, 5.x
</td>
</tr>

Expand Down
Expand Up @@ -162,7 +162,7 @@ Attention <!channel>
Recommendations for learning more:

* To learn more about NerdGraph, see [Introduction to NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph).
* See the Docs site's Alerts [landing page](/docs/alerts).
* See the [alerts landing page](/docs/alerts).
* Browse [New Relic's Explorers Hub](https://discuss.newrelic.com/c/telemetry-data-platform/alerts "Link opens in a new window.") for community discussions about Alerts.
* [Find additional help or file a support ticket](/docs/accounts-partnerships/getting-started-new-relic/find-help-or-file-support-ticket).
* Review the [Alerts licenses attributions](/docs/licenses/product-or-service-licenses/new-relic-alerts), [data usage limits](/docs/licenses/license-information/general-usage-licenses/new-relic-data-usage-limits-policies), and [other notices](/docs/licenses/license-information).
Expand Up @@ -85,7 +85,7 @@ Errors for custom attributes will be included in events on the [JS Errors page](

### Get JavaScript/jQuery for HTML elements [#jquery-example]

This example uses JavaScript/jQuery to get the values of the following HTML elements on the Drupal-generated pages for New Relic's Docs site:
This example uses JavaScript/jQuery to get the values of the following HTML elements on a Drupal-generated page:

* `<link rel="shortlink" href="/node/1111" />`
* `<h1>Using NRQL</h1>`
Expand Down

0 comments on commit 4eeb8a7

Please sign in to comment.