Turbonomic

 View Only

Turbonomic and New Relic: New Uses Access Model

By Dmitry Glushkov posted Fri August 16, 2024 08:34 AM

  

Summary 

Since July 2020 New Relic offers two primary user models: the Original User Model and the New User Model (also known as New Relic One User Model). The Original User Model is being phased out, and new accounts are now defaulted to the New User Model. 

Original User Model: 

  • Role assignment was managed at the account level.
  • Only a fixed set of roles were available, limiting flexibility. 

New User Model: 

  • The New User Model introduces a more flexible and granular approach to roles and permissions.
  • Roles and access are managed through a system of capabilities, allowing for more customized user roles.
  • This model supports federated user management through single sign-on (SSO) and offers improved security features. 

 

 

User Key Utilization in Turbonomic

In the newer versions (starting from 8.13.3) Turbonomic fully supports the New Relic New User Model and effectively uses the User Key (New Relic User API key) for its operations. 

 

  • The User Key is essential for authenticating Turbonomic’s access to New Relic’s API endpoints.
  • Turbonomic uses this key to establish a secure connection with New Relic, allowing it to retrieve the necessary data for monitoring and optimization.
  • The User Key is primarily used to interact with New Relic's GraphQL API, which provides a more flexible and efficient way to query data.

 

Support for Multi-Account Environments 

With support for the New User Model, Turbonomic can efficiently operate in environments where multiple New Relic accounts are managed under a single organizational structure. 

The User Key serves as the central mechanism through which Turbonomic gains access to New Relic data. The permissions attached to this key dictate which New Relic accounts Turbonomic can interact with. By configuring the User Key within the New Relic UI, administrators can ensure that Turbonomic only accesses data from the intended accounts, enhancing security and control. 

For more information on configuring Newrelic User access see:  

https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial/ 

 

 

Comprehensive Recommendations

Turbonomic collects critical data from New Relic, which aggregates information across various domains, including the APM (Application Performance Management) domain and the Infrastructure domain. For Turbonomic to deliver the most valuable and comprehensive recommendations, it requires access to data from both of these domains. 

  • The APM domain provides insights into application performance, including metrics such as response times, throughput, and error rates. This data is crucial for understanding how applications are performing in real-time and identifying potential areas for optimization.
  • The Infrastructure domain offers data related to the underlying resources that support these applications, such as virtual machines, CPU usage, memory utilization, and other infrastructure-related metrics. This data helps Turbonomic assess whether the infrastructure is appropriately sized and performing efficiently. 

To enable Turbonomic to access and utilize this critical data, it is essential to ensure that the User Key used for API requests has the necessary permissions to access all relevant data within both the APM and Infrastructure domains. This configuration should be verified and managed within the New Relic UI, ensuring that the User Key has comprehensive access to all the data Turbonomic needs to provide effective recommendations. 

 

 

 

 

 

0 comments
11 views

Permalink