Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.newrelic.com/docs/apis/nerdgraph/examples/use-nerdgraph-manage-license-keys-user-keys/ below:

NerdGraph tutorial: Manage API keys

This doc contains tutorials on how to use NerdGraph to programmatically manage some New Relic API keys: the license key, the browser key, and the . For general information about our keys, see API keys.

You can use the API keys UI to create and manage keys. Alternatively, you can use NerdGraph's ApiAccess field to programmatically create and manage the following types of keys:

• User keys, required for using NerdGraph

• Data ingest keys, including:

  • The : required for the ingest of most data to New Relic, except for data and data
  • Browser key: required for the ingest of browser monitoring data

One common use case for this feature is the ability to rotate keys for security purposes. Note that you can't use this NerdGraph functionality to delete the license key or browser key that was originally created with an account; those original keys can't be deleted. You can only create additional license keys and manage the ones you've created.

Notes about this functionality:

• All mutations can accept multiple keys as arguments, and will return details about successful changes and errors. See examples below for details.
• All mutations (create, update and delete) will result in an NrAuditEvent that can be queried for auditing purposes. For details, see Audit events.
• Regarding ingest keys:
  • License and Browser keys are categorized by NerdGraph as ingest keys. This is because their main use is to allow data ingest.
  • You can create up to 1,000 keys of each ingest key type, which allows for key rotation.
  • You can't manage or delete original account ingest keys but you can contact New Relic support to rotate these; you can only create additional ingest or user keys and manage keys you've created.

Things to note before using these example queries:

• To understand the data structure, we recommend experimenting with queries using the GraphiQL explorer .
• You can also create, view, and delete user keys using the UI.

To create multiple keys (user key or ingest key) in a single mutation, for multiple accounts and key types. Note that the mutation can return successfully created keys as well as any errors encountered trying to create keys.

Example of creating a key:

        accountId: YOUR_ACCOUNT_ID
      ... on ApiAccessIngestKey {
      ... on ApiAccessIngestKeyError {

Results will vary depending on your data. Use the GraphiQL explorer to experiment with mutations and queries.

Here's an example of using this query to create a user key:

To create a user key, you'd change the above query slightly, in the keys section:

    keys: { user: { accountId: YOUR_ACCOUNT_ID, userId: YOUR_USER_ID } }
      ... on ApiAccessIngestKey {
      ... on ApiAccessIngestKeyError {

The update mutation takes the key ID, not the key string, to identify keys.

      ingest: { keyId: KEY_ID, name: "Updated name", notes: "A new note!" }

Results will vary depending on your data. Use the GraphiQL explorer to experiment with mutations and queries.

The delete mutation takes the key ID, not the key string, to identify keys. Deleted keys will no longer grant access to New Relic systems and will no longer be returned by queries to the API access GraphQL API.

  apiAccessDeleteKeys(keys: { ingestKeyIds: INGEST_KEY_ID }) {

Results will vary depending on your data. Use the GraphiQL explorer to experiment with mutations and queries.

You can access ingest and user keys by querying a single key or all keys, scoped to the actor. If querying for a single key, you must provide the key ID and type (INGEST or USER). Querying for multiple keys is done via a key search, which uses a mandatory types list and an optional scope to filter results. User keys belonging to other users will be obfuscated in the results.

Single key example query:

      key(id: "INGEST_KEY_ID", keyType: INGEST) {
        ... on ApiAccessIngestKey {

Key search example query:

      keySearch(query: { types: INGEST, scope: { ingestTypes: BROWSER } }) {
          ... on ApiAccessIngestKey {

Results will vary depending on your data. Use the GraphiQL explorer to experiment with mutations and queries.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4