@@ -67,7 +75,14 @@ Information about the mutation result when installing an alert policy template
Nr1CatalogAlertPolicyTemplate!
-The template that was used for the installation
+The template that was used for the installation * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -76,7 +91,14 @@ The template that was used for the installation
Nr1CatalogAlertPolicyOutline!
-An outline of the created alert policy
+An outline of the created alert policy * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -85,7 +107,15 @@ An outline of the created alert policy
### Nr1CatalogInstallDashboardTemplateResult
-Information about the mutation result when installing a dashboard template
+Information about the mutation result when installing a dashboard template * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -102,7 +132,14 @@ Information about the mutation result when installing a dashboard template
Nr1CatalogDashboardOutline!
-An outline of the created dashboard
+An outline of the created dashboard * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -111,7 +148,14 @@ An outline of the created dashboard
Nr1CatalogDashboardTemplate!
-The template that was used for the installation
+The template that was used for the installation * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -120,7 +164,15 @@ The template that was used for the installation
### Nr1CatalogInstallPlan
-An installer that uses install plan steps
+An installer that uses install plan steps * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -137,7 +189,14 @@ An installer that uses install plan steps
-The list of install plan steps necessary to execute the installation of the quickstart
+The list of install plan steps necessary to execute the installation of the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -146,7 +205,14 @@ The list of install plan steps necessary to execute the installation of the quic
-The type of installer
+The type of installer * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -155,7 +221,15 @@ The type of installer
### Nr1CatalogInstallPlanStep
-Information pertaining to a specific step in the installation plan
+Information pertaining to a specific step in the installation plan * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -172,7 +246,14 @@ Information pertaining to a specific step in the installation plan
String
-A short form description for the install plan step
+A short form description for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -181,7 +262,14 @@ A short form description for the install plan step
String!
-The human-readable name for the install plan step
+The human-readable name for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -190,7 +278,14 @@ The human-readable name for the install plan step
-Provides context about how the fallback install plan step should proceed
+Provides context about how the fallback install plan step should proceed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -199,7 +294,14 @@ Provides context about how the fallback install plan step should proceed
String!
-Used as a heading for the install plan step
+Used as a heading for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -208,7 +310,14 @@ Used as a heading for the install plan step
ID!
-The unique identifier for the install plan step
+The unique identifier for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -217,7 +326,14 @@ The unique identifier for the install plan step
-Provides context about how the primary install plan step should proceed
+Provides context about how the primary install plan step should proceed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -226,7 +342,14 @@ Provides context about how the primary install plan step should proceed
-Provides context about where the install will occur
+Provides context about where the install will occur * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -235,7 +358,15 @@ Provides context about where the install will occur
### Nr1CatalogInstallPlanTarget
-Represents the location of an install
+Represents the location of an install * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -252,7 +383,14 @@ Represents the location of an install
-Provides context on the location the install will take place
+Provides context on the location the install will take place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -261,7 +399,14 @@ Provides context on the location the install will take place
-Provides context for the operating system that will be targeted
+Provides context for the operating system that will be targeted * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -270,7 +415,14 @@ Provides context for the operating system that will be targeted
-Provides context for the type of installation that will take place
+Provides context for the type of installation that will take place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -279,7 +431,15 @@ Provides context for the type of installation that will take place
### Nr1CatalogQuickstart
-Information about the quickstart
+Information about the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -296,7 +456,14 @@ Information about the quickstart
Boolean!
-Determines if this is a featured quickstart
+Determines if this is a featured quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -305,7 +472,14 @@ Determines if this is a featured quickstart
ID!
-The unique identifier for the quickstart
+The unique identifier for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -314,7 +488,14 @@ The unique identifier for the quickstart
-Metadata associated with the quickstart
+Metadata associated with the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -323,7 +504,14 @@ Metadata associated with the quickstart
String
-Specifies the URL where the source definition for the quickstart can be found
+Specifies the URL where the source definition for the quickstart can be found * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -332,7 +520,14 @@ Specifies the URL where the source definition for the quickstart can be found
Nr1CatalogSupportLevel!
-Level of support expected for the quickstart
+Level of support expected for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -341,7 +536,15 @@ Level of support expected for the quickstart
### Nr1CatalogQuickstartAlert
-Information about an alert in a quickstart
+Information about an alert in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -358,7 +561,14 @@ Information about an alert in a quickstart
ID!
-The unique identifier for the alert
+The unique identifier for the alert * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -373,7 +583,14 @@ This field is no longer supported. Please use Nr1CatalogQuickstartAlertCondition
-Metadata associated with the alert
+Metadata associated with the alert * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -388,7 +605,15 @@ This field is no longer supported. Please use Nr1CatalogQuickstartAlertCondition
### Nr1CatalogQuickstartAlertCondition
-Information about an alert condition in a quickstart
+Information about an alert condition in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -405,7 +630,14 @@ Information about an alert condition in a quickstart
ID!
-The unique identifier for the alert condition
+The unique identifier for the alert condition * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -414,7 +646,14 @@ The unique identifier for the alert condition
-Metadata associated with the alert condition
+Metadata associated with the alert condition * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -423,7 +662,15 @@ Metadata associated with the alert condition
### Nr1CatalogQuickstartAlertConditionMetadata
-Metadata associated with the alert condition in a quickstart
+Metadata associated with the alert condition in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -440,7 +687,14 @@ Metadata associated with the alert condition in a quickstart
String
-A short form description for the alert condition
+A short form description for the alert condition * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -449,7 +703,14 @@ A short form description for the alert condition
String
-The human-readable name for the alert condition
+The human-readable name for the alert condition * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -458,7 +719,14 @@ The human-readable name for the alert condition
-Determines the type of alert condition that will be created
+Determines the type of alert condition that will be created * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -467,7 +735,15 @@ Determines the type of alert condition that will be created
### Nr1CatalogQuickstartAlertMetadata
-Metadata associated with the alert in a quickstart
+Metadata associated with the alert in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -484,7 +760,14 @@ Metadata associated with the alert in a quickstart
String
-A short form description for the alert.
+A short form description for the alert. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -499,7 +782,14 @@ This field is no longer supported. Please use Nr1CatalogQuickstartAlertCondition
String
-The human-readable name for the alert.
+The human-readable name for the alert. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -514,7 +804,15 @@ This field is no longer supported. Please use Nr1CatalogQuickstartAlertCondition
### Nr1CatalogQuickstartDashboard
-Information about a dashboard in a quickstart
+Information about a dashboard in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -531,7 +829,14 @@ Information about a dashboard in a quickstart
ID!
-The unique identifier for the dashboard
+The unique identifier for the dashboard * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -540,7 +845,14 @@ The unique identifier for the dashboard
-Metadata associated with the dashboard
+Metadata associated with the dashboard * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -549,7 +861,15 @@ Metadata associated with the dashboard
### Nr1CatalogQuickstartDashboardMetadata
-Metadata associated with the dashboard in a quickstart
+Metadata associated with the dashboard in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -566,7 +886,14 @@ Metadata associated with the dashboard in a quickstart
String
-A short form description for the dashboard.
+A short form description for the dashboard. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -575,7 +902,14 @@ A short form description for the dashboard.
String
-The human-readable name for the dashboard.
+The human-readable name for the dashboard. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -584,7 +918,14 @@ The human-readable name for the dashboard.
[Nr1CatalogPreview!]!
-A list of previews for the dashboard, such as screenshots.
+A list of previews for the dashboard, such as screenshots. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -593,7 +934,15 @@ A list of previews for the dashboard, such as screenshots.
### Nr1CatalogQuickstartDocumentation
-Information about a documentation component in a quickstart
+Information about a documentation component in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -610,7 +959,14 @@ Information about a documentation component in a quickstart
-Metadata associated with the dashboard
+Metadata associated with the dashboard * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -619,7 +975,15 @@ Metadata associated with the dashboard
### Nr1CatalogQuickstartDocumentationMetadata
-Metadata associated with the documentation component in a quickstart
+Metadata associated with the documentation component in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -636,7 +1000,14 @@ Metadata associated with the documentation component in a quickstart
String
-A short form description for the documentation component.
+A short form description for the documentation component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -645,7 +1016,14 @@ A short form description for the documentation component.
String
-The human-readable name for the documentation component.
+The human-readable name for the documentation component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -654,7 +1032,14 @@ The human-readable name for the documentation component.
String!
-The documentation URL
+The documentation URL * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -663,7 +1048,15 @@ The documentation URL
### Nr1CatalogQuickstartInstallPlan
-Information about an install plan component in a quickstart
+Information about an install plan component in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -680,7 +1073,14 @@ Information about an install plan component in a quickstart
-Metadata associated with the install plan
+Metadata associated with the install plan * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -695,7 +1095,15 @@ This field is no longer supported. Please use installer instead.
### Nr1CatalogQuickstartInstallPlanMetadata
-Metadata associated with the install plan in a quickstart
+Metadata associated with the install plan in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -712,7 +1120,14 @@ Metadata associated with the install plan in a quickstart
String
-A short form description for the documentation component.
+A short form description for the documentation component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -727,7 +1142,14 @@ This field is no longer supported. Please use installer instead.
String
-The human-readable name for the install plan component.
+The human-readable name for the install plan component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
⚠️ DEPRECATED
@@ -742,7 +1164,15 @@ This field is no longer supported. Please use installer instead.
### Nr1CatalogQuickstartMetadata
-Metadata associated with the quickstart that is available in New Relic I/O
+Metadata associated with the quickstart that is available in New Relic I/O * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -759,7 +1189,14 @@ Metadata associated with the quickstart that is available in New Relic I/O
[Nr1CatalogAuthor!]!
-Authors for the quickstart
+Authors for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -768,7 +1205,14 @@ Authors for the quickstart
[Nr1CatalogCategory!]!
-The list of categories for filtering, searching, and grouping associated with the quickstart
+The list of categories for filtering, searching, and grouping associated with the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -777,7 +1221,14 @@ The list of categories for filtering, searching, and grouping associated with th
[String!]!
-The list of category terms associated with the quickstart
+The list of category terms associated with the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -786,7 +1237,14 @@ The list of category terms associated with the quickstart
[Nr1CatalogDataSource!]!
-The list of data sources associated with the quickstart
+The list of data sources associated with the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -795,7 +1253,14 @@ The list of data sources associated with the quickstart
String
-A short form description for the quickstart. Used throughout the platform when displaying the quickstart.
+A short form description for the quickstart. Used throughout the platform when displaying the quickstart. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -804,7 +1269,14 @@ A short form description for the quickstart. Used throughout the platform when d
String
-The human-readable name for the quickstart. Used throughout the New Relic One platform when displaying the quickstart.
+The human-readable name for the quickstart. Used throughout the New Relic One platform when displaying the quickstart. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -813,17 +1285,37 @@ The human-readable name for the quickstart. Used throughout the New Relic One pl
Nr1CatalogIcon
-The corresponding icon for the quickstart
+The corresponding icon for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
-Information about how a quickstart is installed
+Information about how a quickstart is installed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
⚠️ DEPRECATED
+
+
+This field is in a deprecation period. Please refer to `dataSources` for how a quickstart is installed.
+
+
@@ -831,7 +1323,14 @@ Information about how a quickstart is installed
[String!]!
-A list of keywords for filtering and searching
+A list of keywords for filtering and searching * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -840,7 +1339,14 @@ A list of keywords for filtering and searching
-List of components in a quickstart
+List of components in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -849,7 +1355,14 @@ List of components in a quickstart
String!
-The URL friendly name of the quickstart
+The URL friendly name of the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -858,7 +1371,14 @@ The URL friendly name of the quickstart
String
-A short summary detailing the functionality of the quickstart
+A short summary detailing the functionality of the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -867,7 +1387,15 @@ A short summary detailing the functionality of the quickstart
### Nr1CatalogQuickstartsListing
-Paginated information about Quickstarts
+Paginated information about Quickstarts * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -884,7 +1412,14 @@ Paginated information about Quickstarts
String
-Cursor used to fetch the next set of results
+Cursor used to fetch the next set of results * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -893,7 +1428,14 @@ Cursor used to fetch the next set of results
-The list of quickstart results
+The list of quickstart results * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -902,7 +1444,14 @@ The list of quickstart results
Int!
-The total number of quickstart results
+The total number of quickstart results * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -913,7 +1462,15 @@ The total number of quickstart results
### Nr1CatalogInstallDirectiveInput
-Set of attributes which represent how an install takes place
+Set of attributes which represent how an install takes place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -929,7 +1486,14 @@ Set of attributes which represent how an install takes place
Nr1CatalogLinkInstallDirectiveInput
-Link information for this directive. Cannot be used with a nerdlet directive.
+Link information for this directive. Cannot be used with a nerdlet directive. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -938,7 +1502,14 @@ Link information for this directive. Cannot be used with a nerdlet directive.
Nr1CatalogNerdletInstallDirectiveInput
-Nerdlet information for this directive. Cannot be used with a link directive.
+Nerdlet information for this directive. Cannot be used with a link directive. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -947,7 +1518,15 @@ Nerdlet information for this directive. Cannot be used with a link directive.
### Nr1CatalogInstallPlanDirectiveInput
-Set of attributes which represent how an install takes place
+Set of attributes which represent how an install takes place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -963,7 +1542,14 @@ Set of attributes which represent how an install takes place
String
-Value that pairs with the mode to enable the installation step. Supported values are a recipe_name, nerdlet_id, or a link
+Value that pairs with the mode to enable the installation step. Supported values are a recipe_name, nerdlet_id, or a link * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -972,7 +1558,14 @@ Value that pairs with the mode to enable the installation step. Supported values
Nr1CatalogLinkDirectiveInput
-Link information for this directive. Cannot be used with nerdlet or targeted directives.
+Link information for this directive. Cannot be used with nerdlet or targeted directives. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -981,7 +1574,14 @@ Link information for this directive. Cannot be used with nerdlet or targeted dir
-The type of installation that will take place
+The type of installation that will take place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -990,7 +1590,14 @@ The type of installation that will take place
Nr1CatalogNerdletDirectiveInput
-Nerdlet information for this directive. Cannot be used with link or targeted directives.
+Nerdlet information for this directive. Cannot be used with link or targeted directives. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -999,7 +1606,14 @@ Nerdlet information for this directive. Cannot be used with link or targeted dir
Nr1CatalogTargetedDirectiveInput
-Targeted information for this directive. Cannot be used with link or nerdlet directives.
+Targeted information for this directive. Cannot be used with link or nerdlet directives. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1008,7 +1622,15 @@ Targeted information for this directive. Cannot be used with link or nerdlet dir
### Nr1CatalogInstallPlanStepInput
-Metadata associated with a specific step in the install plan
+Metadata associated with a specific step in the install plan * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1024,7 +1646,14 @@ Metadata associated with a specific step in the install plan
String!
-A short form description for the install plan step
+A short form description for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1033,7 +1662,14 @@ A short form description for the install plan step
String!
-The human-readable name for the install plan step
+The human-readable name for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1042,7 +1678,14 @@ The human-readable name for the install plan step
-Provides context about how the fallback install plan step should proceed
+Provides context about how the fallback install plan step should proceed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1051,7 +1694,14 @@ Provides context about how the fallback install plan step should proceed
String!
-Used as a heading for the install plan step
+Used as a heading for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1060,7 +1710,14 @@ Used as a heading for the install plan step
ID!
-The unique identifier for the install plan step
+The unique identifier for the install plan step * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1069,7 +1726,14 @@ The unique identifier for the install plan step
-Provides context about how the primary install plan step should proceed
+Provides context about how the primary install plan step should proceed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1078,7 +1742,14 @@ Provides context about how the primary install plan step should proceed
-Provides context about where the install will occur
+Provides context about where the install will occur * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1087,7 +1758,15 @@ Provides context about where the install will occur
### Nr1CatalogInstallPlanTargetInput
-Represents the location of an install
+Represents the location of an install * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1103,7 +1782,14 @@ Represents the location of an install
-Provides context on the location the install will take place
+Provides context on the location the install will take place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1112,7 +1798,14 @@ Provides context on the location the install will take place
-Operating system for the install
+Operating system for the install * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1121,7 +1814,14 @@ Operating system for the install
-Provides context for the type of installation that will take place
+Provides context for the type of installation that will take place * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1130,7 +1830,15 @@ Provides context for the type of installation that will take place
### Nr1CatalogQuickstartMetadataAlertConditionInput
-Metadata associated with the alert condition in this quickstart
+Metadata associated with the alert condition in this quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1146,7 +1854,14 @@ Metadata associated with the alert condition in this quickstart
String
-A short form description for the alert condition.
+A short form description for the alert condition. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1155,7 +1870,14 @@ A short form description for the alert condition.
String!
-The human-readable name for the alert condition. Used throughout the New Relic One platform when displaying the alert condition.
+The human-readable name for the alert condition. Used throughout the New Relic One platform when displaying the alert condition. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1164,7 +1886,14 @@ The human-readable name for the alert condition. Used throughout the New Relic O
Nr1CatalogRawConfiguration!
-The raw JSON configuration for the alert condition
+The raw JSON configuration for the alert condition * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1173,7 +1902,14 @@ The raw JSON configuration for the alert condition
String
-The source of the alert configuration
+The source of the alert configuration * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1182,7 +1918,14 @@ The source of the alert configuration
-Determines the type of alert condition that will be created
+Determines the type of alert condition that will be created * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1191,7 +1934,15 @@ Determines the type of alert condition that will be created
### Nr1CatalogQuickstartMetadataDashboardInput
-Metadata associated with the dashboard in this quickstart
+Metadata associated with the dashboard in this quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1207,7 +1958,14 @@ Metadata associated with the dashboard in this quickstart
String
-A short form description for the dashboard.
+A short form description for the dashboard. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1216,7 +1974,14 @@ A short form description for the dashboard.
String!
-The human-readable name for the dashboard. Used throughout the New Relic One platform when displaying the dashboard.
+The human-readable name for the dashboard. Used throughout the New Relic One platform when displaying the dashboard. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1225,7 +1990,14 @@ The human-readable name for the dashboard. Used throughout the New Relic One pla
Nr1CatalogRawConfiguration!
-The raw JSON configuration for the dashboard
+The raw JSON configuration for the dashboard * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1234,7 +2006,14 @@ The raw JSON configuration for the dashboard
[Nr1CatalogScreenshotInput!]
-A list of previews for the dashboard, such as screenshots.
+A list of previews for the dashboard, such as screenshots. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1243,7 +2022,14 @@ A list of previews for the dashboard, such as screenshots.
String
-The source of the dashboard configuration
+The source of the dashboard configuration * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1252,7 +2038,15 @@ The source of the dashboard configuration
### Nr1CatalogQuickstartMetadataDocumentationInput
-Metadata associated with the documentation in this quickstart
+Metadata associated with the documentation in this quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1268,7 +2062,14 @@ Metadata associated with the documentation in this quickstart
String!
-A short form description for the documentation component.
+A short form description for the documentation component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1277,7 +2078,14 @@ A short form description for the documentation component.
String!
-The human-readable name for the documentation component. Used throughout the New Relic One platform when displaying the documentation component.
+The human-readable name for the documentation component. Used throughout the New Relic One platform when displaying the documentation component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1286,7 +2094,14 @@ The human-readable name for the documentation component. Used throughout the New
String!
-The documentation URL
+The documentation URL * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1295,7 +2110,15 @@ The documentation URL
### Nr1CatalogQuickstartMetadataInput
-Metadata associated with the quickstart that will be available in New Relic Instant Observability
+Metadata associated with the quickstart that will be available in New Relic Instant Observability * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
+
@@ -1311,7 +2134,14 @@ Metadata associated with the quickstart that will be available in New Relic Inst
-A list of alert condition components that are included in the quickstart
+A list of alert condition components that are included in the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1320,7 +2150,14 @@ A list of alert condition components that are included in the quickstart
[Nr1CatalogAuthorInput!]!
-Authors for the quickstart
+Authors for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1329,7 +2166,14 @@ Authors for the quickstart
[String!]
-The list of category terms associated with the quickstart
+The list of category terms associated with the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1338,7 +2182,14 @@ The list of category terms associated with the quickstart
-A list of dashboard components that are included in the quickstart
+A list of dashboard components that are included in the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1347,7 +2198,14 @@ A list of dashboard components that are included in the quickstart
[ID!]
-A list of data source ids corresponding to the data sources associated with this quickstart
+A list of data source ids corresponding to the data sources associated with this quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1356,7 +2214,14 @@ A list of data source ids corresponding to the data sources associated with this
String!
-A short form description for the quickstart. Used throughout the platform when displaying the quickstart.
+A short form description for the quickstart. Used throughout the platform when displaying the quickstart. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1365,7 +2230,14 @@ A short form description for the quickstart. Used throughout the platform when d
String!
-The human-readable name for the quickstart. Used throughout the New Relic One platform when displaying the quickstart.
+The human-readable name for the quickstart. Used throughout the New Relic One platform when displaying the quickstart. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1374,7 +2246,14 @@ The human-readable name for the quickstart. Used throughout the New Relic One pl
-A list of documentation components that are included in the quickstart
+A list of documentation components that are included in the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1383,7 +2262,14 @@ A list of documentation components that are included in the quickstart
String!
-The public url of an icon for the quickstart
+The public url of an icon for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1392,7 +2278,14 @@ The public url of an icon for the quickstart
[ID!]
-A list of install plan step ids corresponding to the steps of the installation plan
+A list of install plan step ids corresponding to the steps of the installation plan * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1401,7 +2294,14 @@ A list of install plan step ids corresponding to the steps of the installation p
[String!]
-A list of keywords for filtering and searching
+A list of keywords for filtering and searching * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1410,7 +2310,14 @@ A list of keywords for filtering and searching
String
-The URL friendly name for the quickstart
+The URL friendly name for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1419,7 +2326,14 @@ The URL friendly name for the quickstart
String
-Specifies the URL where the source definition for the quickstart can be found
+Specifies the URL where the source definition for the quickstart can be found * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1428,7 +2342,14 @@ Specifies the URL where the source definition for the quickstart can be found
String!
-A short summary detailing the functionality of the quickstart
+A short summary detailing the functionality of the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1437,7 +2358,14 @@ A short summary detailing the functionality of the quickstart
Nr1CatalogSupportLevel
-Level of support for the quickstart
+Level of support for the quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(flag:`DevEx/nrio_mutations`)
+
+
@@ -1448,7 +2376,15 @@ Level of support for the quickstart
### Nr1CatalogInstallPlanDestination
-Possible destinations for the install plan target
+Possible destinations for the install plan target * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1501,7 +2437,15 @@ Unknown install - special case when the target where the install takes place is
### Nr1CatalogInstallPlanDirectiveMode
-Possible modes for an install plan directive
+Possible modes for an install plan directive * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1538,7 +2482,15 @@ Directs the installation toward a specific target
### Nr1CatalogInstallPlanOperatingSystem
-Possible types for the install plan operating system
+Possible types for the install plan operating system * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1575,7 +2527,15 @@ Windows operating system
### Nr1CatalogInstallPlanTargetType
-Possible types for the install plan target
+Possible types for the install plan target * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1620,7 +2580,15 @@ Unknown install - special case when the target where the install takes place is
### Nr1CatalogInstallerType
-Type of installer
+Type of installer * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1641,7 +2609,15 @@ Install plan
### Nr1CatalogQuickstartAlertConditionType
-Possible types of configured alert conditions
+Possible types of configured alert conditions * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1687,7 +2663,15 @@ A static alert condition
### Nr1CatalogInstallPlanDirective
-Information about an install plan directive
+Information about an install plan directive * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1704,7 +2688,14 @@ Information about an install plan directive
-The mode of the install plan directive
+The mode of the install plan directive * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -1713,7 +2704,15 @@ The mode of the install plan directive
### Nr1CatalogInstaller
-Information about how a quickstart is installed
+Information about how a quickstart is installed * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1730,7 +2729,14 @@ Information about how a quickstart is installed
-The type of installer
+The type of installer * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -1739,7 +2745,15 @@ The type of installer
### Nr1CatalogQuickstartComponent
-Information about a component in a quickstart
+Information about a component in a quickstart * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1756,7 +2770,14 @@ Information about a component in a quickstart
-Metadata associated with the quickstart component
+Metadata associated with the quickstart component * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -1765,7 +2786,15 @@ Metadata associated with the quickstart component
### Nr1CatalogQuickstartComponentMetadata
-Information related to the metadata attached to a quickstart component
+Information related to the metadata attached to a quickstart component * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
+
@@ -1782,7 +2811,14 @@ Information related to the metadata attached to a quickstart component
String
-A short form description for the quickstart component.
+A short form description for the quickstart component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
@@ -1791,7 +2827,14 @@ A short form description for the quickstart component.
String
-The human-readable name for the quickstart component.
+The human-readable name for the quickstart component. * [#help-nr1-dev-experience](https://newrelic.slack.com/archives/CPE597DNY)
+ * Team ID: No team ID provided
+
+* [catalog-service-elixir repo](https://source.datanerd.us/nr1-dev-experience/catalog-service-elixir)
+
+ * visibility(customer)
+
+
diff --git a/install/activemq/install.yml b/install/activemq/install.yml
deleted file mode 100644
index ab874f4bbe..0000000000
--- a/install/activemq/install.yml
+++ /dev/null
@@ -1,17 +0,0 @@
-id: activemq-integration
-name: ActiveMQ
-title: ActiveMQ monitoring
-description: |
- Monitor the performance metrics of your Apache ActiveMQ instances in real-time with New Relic APM. New Relic detects your ActiveMQ metrics like queues, brokers, producers, consumers, garbage collection rate, heap memory usage and more.
-
-target:
- type: integration
- destination: host
- os:
- - linux
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/jmx-monitoring-activemq
-
\ No newline at end of file
diff --git a/install/ansible-automation-controller/install.yml b/install/ansible-automation-controller/install.yml
deleted file mode 100644
index 3e6c0a425f..0000000000
--- a/install/ansible-automation-controller/install.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-id: ansible-automation-controller
-name: Ansible Automation Controller
-title: Ansible Automation Controller monitoring
-description: |
- The Ansible Automation Controller integration will enable you to monitor and analyze your Ansible Automation Controller infrastructure.
-
-target:
- type: integration
- destination: host
- os:
- - linux
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/ansible-controller-integration/
diff --git a/install/apache-flink/install.yml b/install/apache-flink/install.yml
deleted file mode 100644
index e85e552810..0000000000
--- a/install/apache-flink/install.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-id: apache-flink
-name: Apache Flink
-title: Apache Flink monitoring
-description: |
- New Relic’s instant observability quickstart with Apache Flink monitoring helps to detect client, jobmanager and taskmanager logs and parses them into a JSON payload.
-
-target:
- type: integration
- destination: host
- os:
- - linux
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/install-configure-openmetrics/install-apache-flink/
diff --git a/install/aws/aws-security-lake/install.yml b/install/aws/aws-security-lake/install.yml
new file mode 100644
index 0000000000..0993650acf
--- /dev/null
+++ b/install/aws/aws-security-lake/install.yml
@@ -0,0 +1,13 @@
+id: aws-security-lake
+name: Amazon-Security-Lake
+title: Amazon Security Lake
+description: |
+ Amazon Security Lake monitoring helps you reduce the friction of sending Security Lake logs to New Relic. With Security Lake logs, you can easily monitor your various security features accross multiple AWS accounts.
+target:
+ type: integration
+ destination: cloud
+install:
+ mode: link
+ destination:
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration/
diff --git a/install/aws/aws-verified-access/install.yml b/install/aws/aws-verified-access/install.yml
new file mode 100644
index 0000000000..89c5ee0479
--- /dev/null
+++ b/install/aws/aws-verified-access/install.yml
@@ -0,0 +1,14 @@
+id: aws-verified-access
+name: AWS-Verified-Access
+title: Amazon Verified Access Flow Logs via Kinesis Data Firehose
+description: |
+ Amazon Verified Access Log monitoring via Kinesis Data Firehose helps you reduce the friction of sending logs to New Relic.
+
+target:
+ type: integration
+ destination: cloud
+
+install:
+ mode: link
+ destination:
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-verified-access-monitoring-integration/
diff --git a/install/dojo/install.yml b/install/dojo/install.yml
deleted file mode 100644
index a09d4c7774..0000000000
--- a/install/dojo/install.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-id: dojo
-name: Dojo
-title: Dojo monitoring
-description: |
- With New Relic, monitor your Dojo solution to get full visibility into the core web vitals performance of your application or website.
-target:
- type: agent
- destination: application
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/dojo-io-integration/
\ No newline at end of file
diff --git a/install/mobile-network-performance/install.yml b/install/mobile-network-performance/install.yml
new file mode 100644
index 0000000000..e9b6dc91d3
--- /dev/null
+++ b/install/mobile-network-performance/install.yml
@@ -0,0 +1,17 @@
+id: mobile-network-performance-install
+name: Mobile Network Performance Install Plan
+title: Mobile Network Performance Install Plan
+description: |
+ Installs the Mobile Network Performance Dashboard.
+
+target:
+ type: unknown
+ destination: unknown
+ os:
+ - linux
+ - windows
+
+install:
+ mode: link
+ destination:
+ url: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/
\ No newline at end of file
diff --git a/install/nuxt-js/install.yml b/install/nuxt-js/install.yml
deleted file mode 100644
index b5c9db1c0f..0000000000
--- a/install/nuxt-js/install.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-id: nuxtjs
-name: NuxtJS
-title: NuxtJs
-description: |
- Instrument and monitor your NuxtJS build apps with New Relic’s Vue browser monitoring agent. Analyze performance data right out of the box.
-target:
- type: agent
- destination: application
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/browser-monitoring-integrations/nuxt-js-integration/
diff --git a/install/on-host-integration/hivemq/install.yml b/install/on-host-integration/hivemq/install.yml
new file mode 100644
index 0000000000..19d8876dc2
--- /dev/null
+++ b/install/on-host-integration/hivemq/install.yml
@@ -0,0 +1,16 @@
+id: hivemq-integration-docs
+name: HiveMQ
+title: HiveMQ monitoring integration
+description: |
+ Our HiveMQ integration collects and metrics from your HiveMQ to our platform, where you can aggregate and visualize key metrics. We collect all the data from the HiveMQ metrics subsystem.
+
+level: New Relic
+
+target:
+ type: agent
+ destination: host
+
+install:
+ mode: link
+ destination:
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-hivemq/
diff --git a/install/on-host-integration/mongodb-prometheus/install.yml b/install/on-host-integration/mongodb-prometheus/install.yml
deleted file mode 100644
index b441380a07..0000000000
--- a/install/on-host-integration/mongodb-prometheus/install.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-id: mongodb-prometheus-integration-docs
-name: MongoDB (Prometheus)
-title: MongoDB monitoring integration
-description: |
- Our MongoDB integration collects and sends inventory and metrics from your MongoDB cluster to our platform, where you can aggregate and visualize key performance metrics. We collect data on mongos, mongod, and config servers, as well as on databases and collections to help pinpoint performance bottlenecks.
-
-level: New Relic
-
-target:
- type: agent
- destination: host
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/windows-services-integration-new/
diff --git a/install/on-host-integration/squid/install.yml b/install/on-host-integration/squid/install.yml
new file mode 100644
index 0000000000..dff7cf7535
--- /dev/null
+++ b/install/on-host-integration/squid/install.yml
@@ -0,0 +1,16 @@
+id: squid-prometheus-integration-docs
+name: Squid
+title: Squid prometheus monitoring integration
+description: |
+ Our Squid prometheus integration collects metrics from your Squid cache manager to our platform, where you can aggregate and visualize key metrics. All the data is collected using the [Prometheus squid-exporter](https://github.com/boynux/squid-exporter).
+
+level: New Relic
+
+target:
+ type: agent
+ destination: host
+
+install:
+ mode: link
+ destination:
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-squid/
diff --git a/install/on-host-integration/vsphere/install.yml b/install/on-host-integration/vsphere/install.yml
new file mode 100644
index 0000000000..a3031985c7
--- /dev/null
+++ b/install/on-host-integration/vsphere/install.yml
@@ -0,0 +1,14 @@
+id: vsphere-integration
+name: VMware vSphere
+title: VMware vSphere integration
+description: |
+ The VMware vSphere on-host integration collects and sends inventory and metrics from your VMware vSphere environment to New Relic so you can monitor its health. We collect metrics at the datacenter, cluster, host, datastore, and virtual machine levels.
+ As part of this integration we will install the New Relic Infrastructure agent.
+target:
+ type: on_host_integration
+ destination: host
+
+install:
+ mode: link
+ destination:
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/vmware-vsphere-monitoring-integration/#install
diff --git a/install/openai/install.yaml b/install/openai/install.yaml
deleted file mode 100644
index c2270551a3..0000000000
--- a/install/openai/install.yaml
+++ /dev/null
@@ -1,13 +0,0 @@
-id: setup-openai
-name: OpenAI integration
-title: OpenAI integration
-description: A lightweight tool to monitor your OpenAI workload.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://github.com/newrelic/openai-api-monitoring
diff --git a/install/public-api-performance/install.yml b/install/public-api-performance/install.yml
deleted file mode 100644
index 8f04c26590..0000000000
--- a/install/public-api-performance/install.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-id: public-api-performance
-name: New Relic Public API Performance
-title: New Relic Public API Performance
-description: The Public API Performance dashboard is a dashboard supported by New Relic’s Global Performance data sets. It’s an out-of-the-box dashboard included as part of your New Relic account.
-
-target:
- type: unknown
- destination: unknown
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/explore-public-api-performance-dashboard/
diff --git a/install/redmine/install.yml b/install/redmine/install.yml
deleted file mode 100644
index 9bda1a14d4..0000000000
--- a/install/redmine/install.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-id: redmine
-name: Redmine
-title: Redmine monitoring
-description: |
- New Relic’s instant observability Redmine quickstart helps you get full visibility into the into the performance of your Redmine app.
-
-target:
- type: integration
- destination: host
- os:
- - linux
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/redmine-integration/
\ No newline at end of file
diff --git a/install/redpanda/install.yml b/install/redpanda/install.yml
deleted file mode 100644
index ca654c696d..0000000000
--- a/install/redpanda/install.yml
+++ /dev/null
@@ -1,14 +0,0 @@
-id: redpanda
-name: Redpanda
-title: Redpanda
-description: |
- Using New Relic’s instant observability quickstart with Redpanda monitoring, you can detect metrics for debugging and monitoring your system’s health.
-
-target:
- type: integration
- destination: host
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/redpanda-integration/
diff --git a/install/snowflake/install.yml b/install/snowflake/install.yml
deleted file mode 100644
index c39f909693..0000000000
--- a/install/snowflake/install.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-id: snowflake
-name: Snowflake
-title: Snowflake monitoring
-description: |
- Quickly monitor your Snowflake application by tracking performance issues with a full end-to-end view of distributed traces.
-target:
- type: integration
- destination: host
- os:
- - linux
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/snowflake-integration/
-
\ No newline at end of file
diff --git a/install/third-party/cloudfoundry/install.yml b/install/third-party/cloudfoundry/install.yml
deleted file mode 100644
index 647bb964a5..0000000000
--- a/install/third-party/cloudfoundry/install.yml
+++ /dev/null
@@ -1,14 +0,0 @@
-id: third-party-cloudfoundry
-name: CloudFoundry
-title: CloudFoundry
-description: |
- Create, deploy, and manage microservice applications in Kubernetes containers.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/vmware-tanzu-pcf-integration
\ No newline at end of file
diff --git a/install/third-party/codestream/github-cs/install.yml b/install/third-party/codestream/github-cs/install.yml
deleted file mode 100644
index 3c0a459eca..0000000000
--- a/install/third-party/codestream/github-cs/install.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-id: third-party-github-for-codestream
-name: GitHub for CodeStream
-title: GitHub for CodeStream
-description: |
- GitHub is a code hosting platform for version control and collaboration. It lets developers and others work together on projects from anywhere.
-
- With CodeStream you can create, review, and merge GitHub PRs without ever leaving your IDE. All with full source-tree and full file access, your favorite keybindings, and all the code intelligence embedded in your development environment.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/codestream/start-here/install-codestream/#connect-tools
diff --git a/install/third-party/codestream/slack-cs/install.yml b/install/third-party/codestream/slack-cs/install.yml
deleted file mode 100644
index 2d7522eb30..0000000000
--- a/install/third-party/codestream/slack-cs/install.yml
+++ /dev/null
@@ -1,14 +0,0 @@
-id: third-party-slack-for-codestream
-name: Slack for CodeStream
-title: Slack for CodeStream
-description: |
- Connect New Relic CodeStream to your team's Slack channel.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/codestream/codestream-integrations/slack-integration/
diff --git a/install/third-party/dapr/install.yml b/install/third-party/dapr/install.yml
new file mode 100644
index 0000000000..3f9601cdb3
--- /dev/null
+++ b/install/third-party/dapr/install.yml
@@ -0,0 +1,13 @@
+id: third-party-dapr
+name: Dapr
+title: Dapr
+description: |
+ Dapr is a portable, event-driven runtime that makes it easy for any developer to build resilient, stateless and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
+target:
+ type: integration
+ destination: cloud
+
+install:
+ mode: link
+ destination:
+ url: https://docs.dapr.io/operations/monitoring/tracing/newrelic/
diff --git a/install/third-party/gigamon-appinsights/install.yml b/install/third-party/gigamon-appinsights/install.yml
new file mode 100644
index 0000000000..e9a157ebeb
--- /dev/null
+++ b/install/third-party/gigamon-appinsights/install.yml
@@ -0,0 +1,18 @@
+id: third-party-gigamon-appinsights
+
+name: Gigamon Application Insights
+
+title: Gigamon Application Insights
+
+description: |
+ Application intelligence is the power to identify, filter, and enrich application data coming from your hybrid cloud.
+ It directs precise application and metadata flows to security and observability tools for insight into New Relic.
+
+target:
+ type: integration
+ destination: cloud
+
+install:
+ mode: link
+ destination:
+ url: https://www.gigamon.com/partners/technology-partners.html#new-relic
diff --git a/install/third-party/github/install.yml b/install/third-party/github/install.yml
index 3784646dc0..260f622aa4 100644
--- a/install/third-party/github/install.yml
+++ b/install/third-party/github/install.yml
@@ -2,10 +2,7 @@ id: github-dependabot-install
name: GitHub Dependabot
title: Automatically Import GitHub Dependabot Events
description: |
- Set up automatic ingestion of your GitHub Dependabot events using two steps:
- - Webhook for ongoing ingestion
- - Historical import for past data
-
+ Set up automatic ingestion of your GitHub Dependabot events by using webhook for ongoing ingestion and historical import for past data.
target:
type: integration
destination: cloud
diff --git a/install/third-party/jfrog-platform/install.yml b/install/third-party/jfrog-platform/install.yml
index 7a108195e6..44bda59007 100644
--- a/install/third-party/jfrog-platform/install.yml
+++ b/install/third-party/jfrog-platform/install.yml
@@ -11,4 +11,4 @@ target:
install:
mode: link
destination:
- url: https://github.com/jfrog/log-analytics-newrelic
\ No newline at end of file
+ url: https://jfrog.com/help/r/jfrog-platform-administration-documentation/new-relic
\ No newline at end of file
diff --git a/install/third-party/lacework/install.yml b/install/third-party/lacework/install.yml
index f4a6888b9d..ee94e5561e 100644
--- a/install/third-party/lacework/install.yml
+++ b/install/third-party/lacework/install.yml
@@ -11,4 +11,4 @@ target:
install:
mode: link
destination:
- url: https://support.lacework.com/hc/en-us/articles/360005842354-New-Relic
\ No newline at end of file
+ url: https://docs.lacework.net/onboarding/new-relic
\ No newline at end of file
diff --git a/install/third-party/newrelic-ingest-metric/install.yml b/install/third-party/newrelic-ingest-metric/install.yml
deleted file mode 100644
index bcf532e2fa..0000000000
--- a/install/third-party/newrelic-ingest-metric/install.yml
+++ /dev/null
@@ -1,18 +0,0 @@
-id: newrelic-ingest-metric
-name: New Relic Ingest Metric
-title: New Relic Ingest Metric
-description: |
- Use this quickstart to set up a synthetic monitor that:
- 1. Queries ingestion by data source, faceted by the attribute of your choice (e.g., APM Events by appName)
- 2. Transforms the output into a metric that is pushed to the Metric API
- 3. Can be queried for consumption analysis / dashboards for 13 months
-
-
-target:
- type: unknown
- destination: unknown
-
-install:
- mode: link
- destination:
- url: https://github.com/newrelic-experimental/nr1-ingest-metric-script
diff --git a/install/third-party/sagemaker/install.yml b/install/third-party/sagemaker/install.yml
deleted file mode 100644
index e772502a38..0000000000
--- a/install/third-party/sagemaker/install.yml
+++ /dev/null
@@ -1,14 +0,0 @@
-id: third-party-amazon-sagemaker
-name: Amazon SageMaker
-title: Amazon SageMaker
-description: |
- Use this integration to quickly monitor your Amazon SageMaker metrics and objects (sent to AWS CloudWatch) and view them as entities and dashboards in New Relic One.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/mlops/integrations/aws-sagemaker-mlops-integration/
\ No newline at end of file
diff --git a/install/third-party/teams-cs/install.yml b/install/third-party/teams-cs/install.yml
deleted file mode 100644
index 61a338f184..0000000000
--- a/install/third-party/teams-cs/install.yml
+++ /dev/null
@@ -1,14 +0,0 @@
-id: third-party-microsoft-teams-for-codestream
-name: Microsoft Teams for CodeStream
-title: Microsoft Teams for CodeStream
-description: |
- Guide to help you get set up using New Relic's Microsoft Teams for CodeStream.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/codestream/codestream-integrations/msteams-integration/
diff --git a/install/third-party/victorops/install.yml b/install/third-party/victorops/install.yml
deleted file mode 100644
index 7a821db41e..0000000000
--- a/install/third-party/victorops/install.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-id: third-party-victorops
-name: VictorOps
-title: VictorOps
-description: |
- Get notified via VictorOps when incidents are opened, acknowledged, or closed.
- Notifications can include charts about the incident.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts
\ No newline at end of file
diff --git a/install/third-party/vmware-esxi/install.yml b/install/third-party/vmware-esxi/install.yml
deleted file mode 100644
index bdd4ef1c75..0000000000
--- a/install/third-party/vmware-esxi/install.yml
+++ /dev/null
@@ -1,13 +0,0 @@
-id: third-party-vmware-esxi
-name: VMware ESXi
-title: VMware ESXi
-description: Hypervisor built for direct interaction with server hardware and resources.
-
-target:
- type: integration
- destination: cloud
-
-install:
- mode: link
- destination:
- url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/vmware-vsphere-monitoring-integration/
\ No newline at end of file
diff --git a/quickstarts/active-directory/config.yml b/quickstarts/active-directory/config.yml
new file mode 100644
index 0000000000..e659842900
--- /dev/null
+++ b/quickstarts/active-directory/config.yml
@@ -0,0 +1,28 @@
+id: 85639904-b7cd-492f-854b-863e35b0f8cc
+slug: active-directory
+title: Active Directory
+description: |
+ This quickstart provides you with the integration, dashboard, and alert policies necessary to proactively monitor the health and availability of your Active Directory domain controllers.
+summary: |
+ Active Directory integration for the health and availability of domain controllers.
+level: Verified
+authors:
+ - Zack Mutchler
+keywords:
+ - active directory
+ - microsoft
+ - domain controller
+ - ldap
+ - kerberos
+ - featured
+dataSourceIds:
+ - active-directory
+alertPolicies:
+ - active-directory
+dashboards:
+ - active-directory
+documentation:
+ - name: Active Directory integration documentation
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/active-directory-integration/
+ description: Quickly monitor your Active Directory domain controllers.
+icon: logo.svg
diff --git a/quickstarts/active-directory/logo.svg b/quickstarts/active-directory/logo.svg
new file mode 100644
index 0000000000..31de7185d7
--- /dev/null
+++ b/quickstarts/active-directory/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/activemq/config.yml b/quickstarts/activemq/config.yml
index 5cddce6da9..d0ba21dbd9 100644
--- a/quickstarts/activemq/config.yml
+++ b/quickstarts/activemq/config.yml
@@ -40,8 +40,6 @@ keywords:
- activemq
- jmx monitoring
- apache
-installPlans:
- - activemq-integration
dataSourceIds:
- activemq
dashboards:
diff --git a/quickstarts/adobe-commerce-business-insights/config.yml b/quickstarts/adobe-commerce-business-insights/config.yml
new file mode 100644
index 0000000000..53fe5cfc31
--- /dev/null
+++ b/quickstarts/adobe-commerce-business-insights/config.yml
@@ -0,0 +1,79 @@
+id: 5b6f36ca-ce68-448a-94e4-a0e4a2be5d29
+slug: adobe-commerce-business-insights
+description: |
+ ## Why monitor your Adobe Commerce website?
+ Monitoring your Adobe Commerce powered website is essential for ensuring that the system is running smoothly and providing accurate data insights. Here are some of the reasons why:
+ - Improved performance: Monitoring can help you identify and fix performance bottlenecks, which can lead to a faster and more responsive shopping experience for your customers.
+ - Increased uptime: By monitoring your application, you can detect and resolve issues before they cause downtime. This can help you avoid lost sales and damage to your brand reputation.
+ - Enhanced security: Monitoring can help you identify and mitigate security threats, such as hacking attempts and data breaches. This can help protect your customers' data and your business's reputation.
+ - Better decision-making: Monitoring data can help you make better decisions about your business, such as how to allocate resources, optimize marketing campaigns, and improve the customer experience.
+ - Compliance with regulations: In some industries, such as healthcare and finance, there are strict regulations that businesses must comply with. Monitoring can help you ensure that your application is meeting these regulations.
+
+ Overall, monitoring your Adobe Commerce application can help you improve its performance, uptime, security, and decision-making capabilities. This can lead to a better shopping experience for your customers, increased sales, and a more secure and compliant business.
+
+ ## Comprehensive monitoring quickstart for Adobe Commerce
+ The New Relic Adobe Commerce monitoring quickstart will help businesses and system users track key performance indicators (KPIs) and other metrics in real time. This ensures that the system is performing optimally and helps identify potential issues before they become major problems.
+
+ Below are a few of the key features:
+
+ ### Revenue monitoring:
+ Monitoring revenue performance in real time can help ensure the accuracy and timeliness of sales data. Tracking revenue over time can identify trends and patterns, providing valuable insights for making informed decisions about marketing strategies and inventory management.
+
+ ### Downtime impact:
+ A business's revenue can be directly affected by downtime if customers are unable to purchase. Keeping track of downtime and lost revenue can help businesses quantify the impact of these issues.
+
+ ### Order tracking:
+ Keep a close watch on order specifics, including total orders, average order value, and most recent orders, to gain valuable insights into your customers' purchasing patterns.
+
+ ### Customer details:
+ Analyzing customer details, such as new vs. returning customers and assessing cart abandonment rates, can provide businesses with a deeper understanding of their specific target audience.
+
+ ### Funnel monitoring:
+ By analyzing the bottom of the funnel, businesses can identify the points in the customer journey where they are losing potential customers and make changes to improve the user experience and drive conversions.
+
+ ## What's included?
+ You'll have full-stack observability of your Adobe Commerce app out-of-the-box:
+ - Alerts (Downtime (%), HTTP Errors and Largest Contentful Paint (LCP))
+ - Dashboards (Executive summary, Customers, Orders, Funnel and more)
+ - Keep an eye on the performance and reliability of your Adobe Commerce site
+ - Keep track of your transactions and bottom of the funnel on a desktop or mobile device
+
+
+summary: |
+ Adobe Commerce quickstart offers a tailored business insights platform for Adobe Commerce store owners and ecommerce managers. It facilitates real-time data extraction for informed decision-making.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: Adobe Commerce Business Insights
+documentation:
+ - name: Adobe Commerce Business Insights documentation
+ description: |
+ Adobe Commerce Quickstart provides pre-configured packages for businesses to gain real-time insights.
+ url: https://docs.newrelic.com/docs/apm/agents/php-agent/other-integrations/magento-business-insights/
+keywords:
+ - adobe commerce
+ - adobe commerce business insights
+ - adobe
+ - nri-flex
+ - adobe magento
+ - magento adobe
+ - adobe commerce magento
+ - adobe magento commerce
+ - adobe commerce monitoring
+ - adobe commerce business insights
+ - ecommerce
+ - magento ecommerce
+ - adobe ecommerce
+ - adobe commerce monitoring
+dataSourceIds:
+ - new-relic-infrastructure-agent
+ - php
+ - mysql
+ - apache
+ - elasticsearch
+ - new-relic-synthetics
+dashboards:
+ - adobe-commerce-business-insights
+alertPolicies:
+ - adobe-commerce-business-insights
diff --git a/quickstarts/adobe-commerce-business-insights/logo.svg b/quickstarts/adobe-commerce-business-insights/logo.svg
new file mode 100644
index 0000000000..bc4e0a1019
--- /dev/null
+++ b/quickstarts/adobe-commerce-business-insights/logo.svg
@@ -0,0 +1,17 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/aerospike/config.yml b/quickstarts/aerospike/config.yml
new file mode 100644
index 0000000000..724b8eebfe
--- /dev/null
+++ b/quickstarts/aerospike/config.yml
@@ -0,0 +1,36 @@
+id: c676d398-14d3-4d32-a00d-56aab474f1f7
+
+slug: aerospike
+description: |
+ ## Comprehensive monitoring quickstart for Aerospike
+ New Relic detects your Aerospike metrics like uptime, info stats, memory, client connections, etc. Monitor the performance metrics of your Aerospike instances in real-time with New Relic APM.
+
+ ## Why monitor Aerospike?
+ Using Aerospike database instrumentation, you can monitor cluster health, database performance, and alerts based on instantaneous and cumulative metrics.
+
+ ## What’s included in this quickstart?
+ New Relic Aerospike monitoring quickstart boasts instant full-stack observability out-of-the-box:
+ - Alerts for Aerospike (failed generation, unavailable partitions, uptime and heap efficiency %)
+ - Dashboards (uptime, info stats, memory, client connections, etc)
+summary: |
+ Instrument and monitor your Aerospike with the New Relic infrastructure agent. Analyze your performance data using our pre-built dashboards and alert conditions.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Ramana reddy
+title: Aerospike
+documentation:
+ - name: Aerospike integration documentation
+ description: |
+ Monitor the performance metrics of your Aerospike instances in real-time with New Relic APM.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/aerospike-integration/
+dataSourceIds:
+ - aerospike
+keywords:
+ - aerospike
+ - real-time data platform
+dashboards:
+ - aerospike
+alertPolicies:
+ - aerospike
diff --git a/quickstarts/aerospike/logo.png b/quickstarts/aerospike/logo.png
new file mode 100644
index 0000000000..a34619094a
Binary files /dev/null and b/quickstarts/aerospike/logo.png differ
diff --git a/quickstarts/ajax/config.yml b/quickstarts/ajax/config.yml
index 37c0675f87..fd0d6c04c6 100644
--- a/quickstarts/ajax/config.yml
+++ b/quickstarts/ajax/config.yml
@@ -53,6 +53,10 @@ keywords:
dashboards:
- ajax
+alertPolicies:
+ - browser
+
# Authors of the quickstart (required)
authors:
- Darren Doyle
+ - Kinsey
diff --git a/quickstarts/amazon-bedrock/config.yml b/quickstarts/amazon-bedrock/config.yml
new file mode 100644
index 0000000000..69d7b2b6d8
--- /dev/null
+++ b/quickstarts/amazon-bedrock/config.yml
@@ -0,0 +1,49 @@
+id: d9996bfb-4ec6-4d59-bf1c-2721d8adb49d
+slug: amazon-bedrock
+description: |
+ ## Why should you monitor your usage of Amazon Bedrock?
+ Monitor your application powered by Amazon Bedrock language models to ensure, get visibility to what you send to Amazon Bedrock, responses received from Amazon Bedrock , latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive Amazon Bedrock monitoring quickstart
+ Our Amazon Bedrock quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the Amazon Bedrock quickstart?
+ New Relic Amazon Bedrock monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Amazon Bedrock usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your Amazon Bedrock usage with New Relic Amazon Bedrock quickstart.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Amazon Bedrock
+documentation:
+ - name: Amazon Bedrock integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Amazon Bedrock app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - amazon bedrock
+ - mlops
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - ai
+ - generative ai
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/amazon-bedrock/logo.png b/quickstarts/amazon-bedrock/logo.png
new file mode 100644
index 0000000000..84a3179916
Binary files /dev/null and b/quickstarts/amazon-bedrock/logo.png differ
diff --git a/quickstarts/annoy/config.yml b/quickstarts/annoy/config.yml
new file mode 100644
index 0000000000..f705887961
--- /dev/null
+++ b/quickstarts/annoy/config.yml
@@ -0,0 +1,49 @@
+id: dfb19b44-2b0b-406d-9f17-7ec27af4a70f
+slug: annoy
+description: |
+ ## Why should you monitor your usage of Annoy?
+
+ Monitor your vector searches on Annoy to get visibility on what you send to Annoy, responses retrieved from Annoy, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Annoy quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Annoy
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - annoy
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/annoy/logo.png b/quickstarts/annoy/logo.png
new file mode 100644
index 0000000000..e80f575621
Binary files /dev/null and b/quickstarts/annoy/logo.png differ
diff --git a/quickstarts/ansible-automation-controller/config.yml b/quickstarts/ansible-automation-controller/config.yml
index 0422852bfd..b7d0c61e93 100644
--- a/quickstarts/ansible-automation-controller/config.yml
+++ b/quickstarts/ansible-automation-controller/config.yml
@@ -31,8 +31,6 @@ keywords:
- ansible automation platform
- ansible tower
- ansiblr automation controller
-installPlans:
- - ansible-automation-controller
dataSourceIds:
- ansible-automation-controller
dashboards:
diff --git a/quickstarts/anyscale/config.yml b/quickstarts/anyscale/config.yml
new file mode 100644
index 0000000000..91ceac9e9c
--- /dev/null
+++ b/quickstarts/anyscale/config.yml
@@ -0,0 +1,56 @@
+id: cde180da-3f5d-4d90-a896-e5841cc2b356
+slug: anyscale
+description: |
+ ## Why should you monitor your usage of Anyscale?
+ Monitor your application powered by Anyscale language models to ensure, get visibility to what you send to Anyscale, responses received from Anyscale, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive Anyscale monitoring quickstart
+ Our Anyscale quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the Anyscale quickstart?
+ New Relic Anyscale monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Anyscale usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your Anyscale usage with New Relic Anyscale quickstart.
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+title: Anyscale
+documentation:
+ - name: Anyscale integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Anyscale app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - anyscale
+ - large language model
+ - natural language processing
+ - nlp
+ - machine learning
+ - artificial intelligence
+ - ai
+ - anyscale ai
+ - cloud native
+ - llm
+ - llm chains
+ - deep learning
+ - distributed computing
+ - kubernetes
+ - generative ai
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/anyscale/logo.svg b/quickstarts/anyscale/logo.svg
new file mode 100644
index 0000000000..2dc2553cfe
--- /dev/null
+++ b/quickstarts/anyscale/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/apache-flink/config.yml b/quickstarts/apache-flink/config.yml
index 904c014bd5..ff5fe58bab 100644
--- a/quickstarts/apache-flink/config.yml
+++ b/quickstarts/apache-flink/config.yml
@@ -42,8 +42,6 @@ keywords:
- flink
- apache flink
- data stream
-installPlans:
- - apache-flink
dataSourceIds:
- apache-flink
dashboards:
diff --git a/quickstarts/apache-hadoop/config.yml b/quickstarts/apache-hadoop/config.yml
new file mode 100644
index 0000000000..b1c941b2dc
--- /dev/null
+++ b/quickstarts/apache-hadoop/config.yml
@@ -0,0 +1,44 @@
+id: d4cf59f5-d1b8-4b02-9261-60f955844e57
+
+slug: apache-hadoop
+description: |
+ ## Comprehensive monitoring quickstart for Apache Hadoop
+ Apache Hadoop metrics are statistical data that Hadoop daemons offer and are used for performance adjustment, debugging, and monitoring. By integrating Apache Hadoop with New Relic, you can get comprehensive information about the workflow by visualizing and gathering metrics and logs.
+
+ ## Why monitor Apache Hadoop?
+ Apache Hadoop is an open-source software package which enables distributed storage and processing of massive data by leveraging a network of computers. It utilizes the MapReduce programming model-based distributed storage and processing of massive data.
+
+ By leveraging New Relic, you can gain a more in-depth understanding of Apache Hadoop performance and health. Monitoring Apache Hadoop with New Relic will help you better understand the HDFS (Hadoop Distributed File System), blocks, system load, data nodes, NodeManager, and jobs.
+
+ ## What’s included in this quickstart?
+ New Relic Apache Hadoop monitoring quickstart provides quality out-of-the-box reporting:
+ - JVM metrics
+ - NameNode metrics
+ - DataNode metrics
+ - Cluster metrics
+ - Queue metrics
+ - Node manager metrics
+ - Infrastructure metrics
+
+summary: |
+ Optimize your Apache Hadoop performance using New Relic Apache Hadoop monitoring.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Apache Hadoop
+documentation:
+ - name: Apache Hadoop integration documentation
+ description: |
+ Monitor the performance metrics of your Apache Hadoop instances in real-time with New Relic Apache Hadoop.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/apache-hadoop-monitoring-integration/
+keywords:
+ - apache-hadoop
+ - apache
+dashboards:
+ - apache-hadoop
+alertPolicies:
+ - apache-hadoop
+dataSourceIds:
+ - apache-hadoop
diff --git a/quickstarts/apache-hadoop/logo.png b/quickstarts/apache-hadoop/logo.png
new file mode 100644
index 0000000000..9e260fbf53
Binary files /dev/null and b/quickstarts/apache-hadoop/logo.png differ
diff --git a/quickstarts/apache-traffic-server/config.yml b/quickstarts/apache-traffic-server/config.yml
new file mode 100644
index 0000000000..192093e882
--- /dev/null
+++ b/quickstarts/apache-traffic-server/config.yml
@@ -0,0 +1,57 @@
+id: 711821c8-fc66-4c25-9527-17407b805cc5
+
+
+slug: apache-traffic-server
+description: |
+ ## Comprehensive monitoring quickstart for Apache Traffic Server
+ By integrating Apache Traffic Server (ATS) with New Relic, you can efficiently set up a monitoring infrastructure that captures, visualizes, and alerts you to important ATS metrics. Monitoring ATS performance and health ensures smooth operation, rapid issue identification, and proactive problem resolution, ultimately enhancing the reliability and efficiency of your web infrastructure.
+
+ ## Why is it important to monitor Apache Traffic Server?
+ Monitor Apache Traffic Server to understand the functionality, performance, and general health of this potent web caching and proxying solution. You will obtain a thorough insight of ATS's behavior, spot any problems before they become serious, and make sure that your web infrastructure is working as efficiently as possible by closely monitoring it.
+
+ By leveraging New Relic, you can gain a more in-depth understanding of Monitoring Apache Traffic Server is an essential procedure that provides priceless information about the functionality, performance, and general health of this potent web caching and proxying solution. You will get a comprehensive understanding of ATS behavior, spot any problems before they become serious, and make sure that your web infrastructure is working as efficiently as possible by closely monitoring it.
+
+ Install this quickstart as part of your proactive observability strategy to guarantee outstanding web performance, exceptional user experiences, and dependable functioning of your web infrastructure. You can efficiently manage ATS and keep up a solid, high-performance web infrastructure.
+
+
+ ## What’s included in this quickstart?
+ The Apache Traffic Server quickstart provides out-of-the-box reporting that covers the following areas:
+
+ - Real-time visibility: Get insights into the performance of your ATS deployment in real time.
+ - Optimized performance: Identify performance bottlenecks and optimize your ATS configuration to improve performance.
+ - Early issue detection: Get alerts when there are potential problems with your ATS deployment so you can take action quickly.
+ - Capacity planning: Plan for future growth by understanding how your ATS deployment is currently being used.
+ - Efficient troubleshooting: Troubleshoot problems with your ATS deployment quickly and easily by using New Relic's tools.
+ - User experience enhancement: Improve the user experience of your applications by understanding how they are being used and making changes to improve performance.
+ - Security insights: Get insights into the security of your ATS deployment and identify potential threats.
+ - Continuous improvement: Use New Relic's data to continuously improve the performance and security of your ATS deployment.
+
+ Monitoring Apache Traffic Server (ATS) with New Relic can help you improve the performance of your online services, which can lead to increased user engagement, longer site visits, and higher revenue.
+
+summary: |
+ Optimize your Apache Traffic Server performance using New Relic Apache Traffic Server monitoring.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Apache Traffic Server
+documentation:
+ - name: Documentation on how to integrate Apache Traffic Server
+ description: |
+ Monitor the performance metrics of your Apache Traffic Server instances in real-time with New Relic Apache Traffic Server.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/apache-traffic-server-monitoring-integration/
+keywords:
+ - ats
+ - apache traffic server
+ - web proxy
+ - web proxy cache
+ - HTTP caching
+ - reverse proxy
+ - content filtering
+dashboards:
+ - apache-traffic-server
+alertPolicies:
+ - apache-traffic-server
+dataSourceIds:
+ - apache-traffic-server
diff --git a/quickstarts/apache-traffic-server/logo.png b/quickstarts/apache-traffic-server/logo.png
new file mode 100644
index 0000000000..3699d4a467
Binary files /dev/null and b/quickstarts/apache-traffic-server/logo.png differ
diff --git a/quickstarts/apache-zooKeeper/config.yml b/quickstarts/apache-zooKeeper/config.yml
new file mode 100644
index 0000000000..3e2bf6c728
--- /dev/null
+++ b/quickstarts/apache-zooKeeper/config.yml
@@ -0,0 +1,38 @@
+id: fe60d07b-4f1d-41d5-b6cc-2a6605baad20
+
+slug: apache-zookeeper
+description: |
+ ## Comprehensive monitoring quickstart for Apache ZooKeeper
+ New Relic detects your Apache ZooKeeper metrics like znode count, watch count, client connections, etc. Monitor your Apache ZooKeeper ensemble, ensuring optimal performance and troubleshooting issues in a timely manner.
+
+ ## Why monitor Apache ZooKeeper?
+ By leveraging Apache ZooKeeper monitoring by New Relic, you gain invaluable visibility into the overall health and performance of your distributed system. This empowers you to swiftly identify and address any potential issues, ensuring optimal operational efficiency.
+
+ ## What’s included in this quickstart?
+ New Relic Apache ZooKeeper monitoring quickstart provides quality out-of-the-box reporting:
+ - Dashboards (znode count, watch count, max latency, client connections, etc)
+ - Alerts for ZooKeeper (rejected connections, watch counts on ZooKeeper nodes)
+
+summary: |
+ Unlock the power of Apache ZooKeeper monitoring with the seamless integration of New Relic infrastructure.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: Apache ZooKeeper
+documentation:
+ - name: Apache ZooKeeper integration documentation
+ description: |
+ Unlock the power of ZooKeeper monitoring with the seamless integration of New Relic infrastructure.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/zookeeper-monitoring-integration/
+keywords:
+ - apache-zooKeeper
+ - ZooKeeper
+ - apache zookeeper
+dataSourceIds:
+ - apache-zookeeper
+dashboards:
+ - apache-zooKeeper
+alertPolicies:
+ - apache-zooKeeper
diff --git a/quickstarts/apache-zooKeeper/logo.png b/quickstarts/apache-zooKeeper/logo.png
new file mode 100644
index 0000000000..f335e23333
Binary files /dev/null and b/quickstarts/apache-zooKeeper/logo.png differ
diff --git a/quickstarts/apache/config.yml b/quickstarts/apache/config.yml
index 555cad6b1f..a4b1da0257 100644
--- a/quickstarts/apache/config.yml
+++ b/quickstarts/apache/config.yml
@@ -1,8 +1,8 @@
id: ad5affab-545a-4355-ad48-cfd66e2fbf00
slug: apache
-title: Apache httpd
+title: Apache HTTPD
description: |+
- ## Understanding Apache httpd
+ ## Understanding Apache HTTPD
The Apache HTTP Server is a free and open-source, secure, efficient, and extensible HTTP web server for the Windows and UNIX operating systems.
@@ -45,3 +45,5 @@ keywords:
- server
dashboards:
- apache
+alertPolicies:
+ - apache
diff --git a/quickstarts/apdex-optimizer/config.yml b/quickstarts/apdex-optimizer/config.yml
new file mode 100644
index 0000000000..6eb550b66c
--- /dev/null
+++ b/quickstarts/apdex-optimizer/config.yml
@@ -0,0 +1,79 @@
+id: e6d3f91e-8a83-4943-94ad-40b5a6281389
+# Sets the URL name of the quickstart on public I/O (required)
+slug: apdex-optimizer
+
+# Displayed in the UI (required)
+title: Apdex Optimizer
+
+# Long-form description of the quickstart (required)
+description: |
+ **Summary of Apdex Optimizer Dashboard**
+
+ ## 1. Apdex Score Overview:
+ - Timeseries chart displaying Apdex scores for each APM application.
+ - Highlights performance trends over time.
+
+ ## 2. Apdex Breakdown:
+ - Detailed breakdown table showcasing Apdex scores for different aspects of your application.
+ - Identifies areas of improvement and potential bottlenecks.
+
+ ## 3. Transaction-level Insights:
+ - In-depth Apdex information on individual transactions.
+ - Pinpoints specific transaction performance for focused optimization.
+
+ ## 4. Threshold Recommendations:
+ - Application Apdex T Value Recommendation table guides optimal threshold settings.
+ - Helps fine-tune Apdex parameters for enhanced performance monitoring.
+
+ ## 5. Transaction Apdex Values:
+ - Transaction Apdex Values table provides granular insights into transaction-level performance.
+ - Enables precise adjustments for optimal user satisfaction.
+
+ ### Actionable Takeaways:
+ - Identify and address performance trends through Apdex score patterns.
+ - Optimize specific transactions based on detailed Apdex insights.
+ - Fine-tune Apdex thresholds for applications to improve overall monitoring effectiveness.
+
+ ### Benefits:
+ - Enhanced visibility into application performance.
+ - Proactive identification of potential issues.
+ - Improved user satisfaction through targeted optimizations.
+
+ This comprehensive Apdex Optimizer dashboard empowers you with actionable data to make informed decisions, ensuring your applications perform at their best.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ Comprehensive APM dashboard providing actionable insights, including Apdex scores over time, detailed breakdowns, transaction-level data, and threshold recommendations, empowering users to optimize application performance effectively
+
+# Support level: New Relic | Verified | Community (required)
+level: New Relic
+
+# Authors of the quickstart (required)
+authors:
+ - Darren Doyle
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - apm
+ - transactions
+ - apdex
+ - errors
+
+
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - apdex-optimizer
+
+# Documentation references
+documentation:
+ - name: Apdex
+ url: https://docs.newrelic.com/docs/apm/new-relic-apm/apdex/apdex-measure-user-satisfaction/#change-apdex-settings
+ description: Apdex is an industry standard to measure users' satisfaction with the response time of web applications and services.
+
+# Content / Design
+icon: logo.svg
+website: https://www.newrelic.com
+
+dataSourceIds:
+ - apdex-optimizer
diff --git a/data-sources/newrelic-ingest-metric/logo.svg b/quickstarts/apdex-optimizer/logo.svg
similarity index 100%
rename from data-sources/newrelic-ingest-metric/logo.svg
rename to quickstarts/apdex-optimizer/logo.svg
diff --git a/quickstarts/apm-change-tracking/config.yml b/quickstarts/apm-change-tracking/config.yml
index 602196714c..65f1e6ecf7 100644
--- a/quickstarts/apm-change-tracking/config.yml
+++ b/quickstarts/apm-change-tracking/config.yml
@@ -25,3 +25,5 @@ documentation:
icon: logo.svg
dashboards:
- change-tracking-apm
+
+
\ No newline at end of file
diff --git a/quickstarts/apm-transaction-analysis/config.yaml b/quickstarts/apm-transaction-analysis/config.yaml
new file mode 100644
index 0000000000..e7ae61a8cd
--- /dev/null
+++ b/quickstarts/apm-transaction-analysis/config.yaml
@@ -0,0 +1,25 @@
+id: 5337037a-7822-438e-a89f-395b8920bad0
+slug: apm-transaction-analysis
+title: APM Transaction Analysis
+description: |
+ ## Why use this dashboard?
+ Normally in the curated APM view you will see one application at a time. When you have hundreds of applications and wish to analyze the relative performance accross apps, this view excels.
+ Using the power of NRQL we present a unified drill down of performance that is very useful when setting up alert conditions and service levels. It is very good at helping explore performance outliers.
+summary: |
+ A unified filterable view of transaction performance across an account.
+level: New Relic
+authors:
+ - Jim Hagan
+keywords:
+ - APM
+ - Transaction
+dataSourceIds:
+ - solutions-hub-dashboards
+documentation:
+ - name: APM Transactions
+ url: https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm/
+ description: Transactions in New Relic's APM
+icon: logo.svg
+website: https://www.newrelic.com
+dashboards:
+ - apm-transaction-analysis
diff --git a/quickstarts/audit/newrelic-ingest-metric/logo.svg b/quickstarts/apm-transaction-analysis/logo.svg
similarity index 100%
rename from quickstarts/audit/newrelic-ingest-metric/logo.svg
rename to quickstarts/apm-transaction-analysis/logo.svg
diff --git a/quickstarts/apollo/apollo-server/config.yml b/quickstarts/apollo/apollo-server/config.yml
index ba13e2235b..b5ec351c28 100644
--- a/quickstarts/apollo/apollo-server/config.yml
+++ b/quickstarts/apollo/apollo-server/config.yml
@@ -21,12 +21,24 @@ level: Community
authors:
- New Relic
- John Vajda
+ - Dave Miyamasu
keywords:
- apollo server
- apollo
- graphql
+ - nodejs
+ - npm
+ - plugin
+ - typescript
+ - express
+ - hapi
+ - koa
+ - fastify
+ - lambda
installPlans:
- node-agent
+dashboards:
+ - apollo-server
dataSourceIds:
- node-js
documentation:
diff --git a/quickstarts/argocd/config.yml b/quickstarts/argocd/config.yml
index 30393b7f5f..c81ab04f03 100644
--- a/quickstarts/argocd/config.yml
+++ b/quickstarts/argocd/config.yml
@@ -50,6 +50,7 @@ keywords:
- remote_write
- promql
- grafana
+ - featured
installPlans:
- setup-prometheus
- setup-prometheus-agent-mode
diff --git a/quickstarts/atlassian/atlassian-jira/config.yml b/quickstarts/atlassian/atlassian-jira/config.yml
index c3eb023d93..70369e60f3 100644
--- a/quickstarts/atlassian/atlassian-jira/config.yml
+++ b/quickstarts/atlassian/atlassian-jira/config.yml
@@ -41,4 +41,5 @@ keywords:
# Content / Design
icon: logo.png
website: https://www.atlassian.com/
-
+dataSourceIds:
+ - atlassian-jira
diff --git a/quickstarts/audit/account-data-ingestion-analysis/config.yml b/quickstarts/audit/account-data-ingestion-analysis/config.yml
index 4849f268a7..a593f0ac4b 100644
--- a/quickstarts/audit/account-data-ingestion-analysis/config.yml
+++ b/quickstarts/audit/account-data-ingestion-analysis/config.yml
@@ -23,3 +23,4 @@ documentation:
description: Manage data coming into New Relic
dashboards:
- data-ingestion-breakdown
+
diff --git a/quickstarts/audit/infrastructure-integrations-data-analysis/config.yml b/quickstarts/audit/infrastructure-integrations-data-analysis/config.yml
index 24f45f2ad8..004d57f91b 100644
--- a/quickstarts/audit/infrastructure-integrations-data-analysis/config.yml
+++ b/quickstarts/audit/infrastructure-integrations-data-analysis/config.yml
@@ -38,3 +38,4 @@ dashboards:
- gcp-integrations-data-ingest-analysis
- kubernetes-data-ingest-analysis
- on-host-integrations-data-analysis
+
diff --git a/quickstarts/audit/k8s-log-ingestion-analysis/config.yaml b/quickstarts/audit/k8s-log-ingestion-analysis/config.yaml
index f22f76019d..bf5fec2edd 100644
--- a/quickstarts/audit/k8s-log-ingestion-analysis/config.yaml
+++ b/quickstarts/audit/k8s-log-ingestion-analysis/config.yaml
@@ -43,5 +43,7 @@ documentation:
installPlans:
- kubernetes-install
+dataSourceIds:
+ - kubernetes
dashboards:
- - k8s-log-ingest-breakdown
\ No newline at end of file
+ - k8s-log-ingest-breakdown
diff --git a/quickstarts/audit/log-ingestion-analysis/config.yml b/quickstarts/audit/log-ingestion-analysis/config.yml
index bdc83ee3eb..2693ee729b 100644
--- a/quickstarts/audit/log-ingestion-analysis/config.yml
+++ b/quickstarts/audit/log-ingestion-analysis/config.yml
@@ -26,3 +26,4 @@ icon: logo.svg
website: https://www.newrelic.com
dashboards:
- log-analysis
+
diff --git a/quickstarts/audit/newrelic-ingest-metric/config.yml b/quickstarts/audit/newrelic-ingest-metric/config.yml
deleted file mode 100644
index eb19fef985..0000000000
--- a/quickstarts/audit/newrelic-ingest-metric/config.yml
+++ /dev/null
@@ -1,37 +0,0 @@
-id: c57f4c0b-824c-4b80-ac93-555763ee9549
-name: newrelic-ingest-metric
-title: New Relic Ingest Metric
-description: |
- This quickstart provides a synthetic monitor (and associated dashboard) that will regularly query ingest for each data type (APM Events, Infrastructure Processes, etc.) and post it to the Metric API as a custom metric `newrelic-ingest-metric`. This means that you can query and analyze ingest across your account for 13 months by default, instead of 8 days for events, 30 days for Logs, etc. The custom metric also includes a facet for each data type, so that you can see, for example, ingest for Mobile Events by appName or Logging by labels.app. The following parameters have default values but are all configurable:
- - ingest interval (hourly, daily, weekly)
- - facet for each data type
- - name of custom metric
- - addition of custom events
-summary: |
- Use this script to set up a synthetic monitor that:
- 1. Queries ingestion by data source, faceted by the attribute of your choice (e.g., APM Events by appName)
- 2. Transforms the output into a metric that is pushed to the Metric API
- 3. Can be queried for consumption analysis / dashboards for 13 months
-level: Community
-authors:
- - Nora Shannon Johnson
-keywords:
- - ingest
- - ingestion
- - custom metric
- - synthetic monitor
- - consumption
- - billing
- - facet
-installPlans:
- - newrelic-ingest-metric
-dataSourceIds:
- - newrelic-ingest-metric
-documentation:
- - name: nr1-ingest-metric-script (github)
- url: https://github.com/newrelic-experimental/nr1-ingest-metric-script
- description: Instructions for updating and activating the synthetic monitor that generates the newrelic.ingest custom metric
-icon: logo.svg
-website: https://www.newrelic.com
-dashboards:
- - newrelic-ingest-metric
diff --git a/quickstarts/audit/newrelic-ingest-metric/images/ingest-infrahosts.png b/quickstarts/audit/newrelic-ingest-metric/images/ingest-infrahosts.png
deleted file mode 100644
index 20b8dee3f0..0000000000
Binary files a/quickstarts/audit/newrelic-ingest-metric/images/ingest-infrahosts.png and /dev/null differ
diff --git a/quickstarts/audit/newrelic-ingest-metric/images/ingest-metrics.png b/quickstarts/audit/newrelic-ingest-metric/images/ingest-metrics.png
deleted file mode 100644
index be99b35183..0000000000
Binary files a/quickstarts/audit/newrelic-ingest-metric/images/ingest-metrics.png and /dev/null differ
diff --git a/quickstarts/audit/newrelic-ingest-metric/images/ingest-overview.png b/quickstarts/audit/newrelic-ingest-metric/images/ingest-overview.png
deleted file mode 100644
index 803a61389b..0000000000
Binary files a/quickstarts/audit/newrelic-ingest-metric/images/ingest-overview.png and /dev/null differ
diff --git a/quickstarts/awadb/config.yml b/quickstarts/awadb/config.yml
new file mode 100644
index 0000000000..402c4e7715
--- /dev/null
+++ b/quickstarts/awadb/config.yml
@@ -0,0 +1,46 @@
+id: 3902c751-1d30-44ac-af9a-00969bd19f5a
+slug: awadb
+description: |
+ ## Why should you monitor your usage of AwaDB?
+ Monitor your vector searches on AwaDB to get visibility on what you send to AwaDB, responses retrieved from AwaDB, latency, usage and errors.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+ ## Comprehensive monitoring quickstart for your AwaDB app
+ Our AwaDB quickstart provides insights like identifying popular queries, sources, and content.
+ ## What’s included in this quickstart?
+ New Relic AwaDB monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your AwaDB app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic AwaDB quickstart
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: AwaDB
+documentation:
+ - name: AwaDB integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - AwaDB
+ - vector search
+ - machine learning
+ - artificial intelligence
+ - AI
+ - ML
+ - data science
+ - big data
+ - NR1_addData
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/awadb/logo.png b/quickstarts/awadb/logo.png
new file mode 100644
index 0000000000..3a912f2ea0
Binary files /dev/null and b/quickstarts/awadb/logo.png differ
diff --git a/quickstarts/aws/amazon-appstream/config.yml b/quickstarts/aws/amazon-appstream/config.yml
new file mode 100644
index 0000000000..3aa0089cde
--- /dev/null
+++ b/quickstarts/aws/amazon-appstream/config.yml
@@ -0,0 +1,35 @@
+id: 40ec6df0-73d5-41f0-a83e-35a2d92dcdd5
+slug: amazon-appstream
+description: |-
+ ## What is Amazon AppStream?
+ Amazon AppStream 2.0 is a fully managed application streaming service that provides users with instant access to their desktop applications from anywhere.
+ ### Get started!
+ Start monitoring Amazon AppStream by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-appstream-monitoring-integration/) to learn more about New Relic monitoring for Amazon AppStream.
+summary: |-
+ Monitor Amazon AppStream by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon AppStream
+documentation:
+ - name: Amazon AppStream installation docs
+ description: |
+ Monitor Amazon AppStream by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-appstream-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - AppStream
+ - amazon appstream
+ - app stream
+ - amazon app stream
+alertPolicies:
+ - amazon-appstream
+dashboards:
+ - amazon-appstream
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-appstream/logo.png b/quickstarts/aws/amazon-appstream/logo.png
new file mode 100644
index 0000000000..2d9c5dc81d
Binary files /dev/null and b/quickstarts/aws/amazon-appstream/logo.png differ
diff --git a/quickstarts/aws/amazon-cloudsearch/config.yml b/quickstarts/aws/amazon-cloudsearch/config.yml
new file mode 100644
index 0000000000..d182309fd2
--- /dev/null
+++ b/quickstarts/aws/amazon-cloudsearch/config.yml
@@ -0,0 +1,35 @@
+id: f7f88b90-ed4a-453e-a1ac-433292393905
+slug: amazon-cloudsearch
+description: |-
+ ## What is Amazon CloudSearch?
+ Amazon CloudSearch is a managed service in the AWS Cloud that makes it simple and cost-effective to set up, manage, and scale a search solution for your website or application.
+ ### Get started!
+ Start monitoring Amazon CloudSearch by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-cloudsearch-monitoring-integration/) to learn more about New Relic monitoring for Amazon CloudSearch.
+summary: |-
+ Monitor Amazon CloudSearch by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon CloudSearch
+documentation:
+ - name: Amazon CloudSearch installation docs
+ description: |
+ Monitor Amazon CloudSearch by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-cloudsearch-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - CloudSearch
+ - amazon cloudsearch
+ - cloud search
+ - amazon cloud search
+alertPolicies:
+ - amazon-cloudsearch
+dashboards:
+ - amazon-cloudsearch
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
diff --git a/quickstarts/aws/amazon-cloudsearch/logo.png b/quickstarts/aws/amazon-cloudsearch/logo.png
new file mode 100644
index 0000000000..edda2ba90d
Binary files /dev/null and b/quickstarts/aws/amazon-cloudsearch/logo.png differ
diff --git a/quickstarts/aws/amazon-cloudwatch-internet-monitor/config.yml b/quickstarts/aws/amazon-cloudwatch-internet-monitor/config.yml
new file mode 100644
index 0000000000..d3e7faa769
--- /dev/null
+++ b/quickstarts/aws/amazon-cloudwatch-internet-monitor/config.yml
@@ -0,0 +1,39 @@
+id: b6ae27cb-1cff-4447-ac3f-c570b80ec4b6
+slug: amazon-cloudwatch-internet-monitor
+description: |-
+ ## What is Amazon CloudWatch Internet Monitor?
+
+ Amazon CloudWatch Internet Monitor provides visibility into how internet issues impact the performance and availability between your applications hosted on AWS and your end users.
+
+ ### Get started!
+
+ Start monitoring Amazon CloudWatch Internet Monitor by sending your Amazon CloudWatch Internet Monitor Logs to New Relic.
+
+ Check out our Amazon CloudWatch Internet Monitor documentation to instrument your cloud service and manage the stability, scalability, and reliability of your systems with New Relic's Log monitoring capabilities.
+
+ ### More info
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-internet-monitor-integration/) to learn more about New Relic monitoring for Amazon CloudWatch Internet Monitor.
+summary: Monitor Amazon CloudWatch Internet Monitor in New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Aarushi Jain
+title: Amazon CloudWatch Internet Monitor
+documentation:
+ - name: Amazon CloudWatch Internet Monitor installation docs
+ description: Monitor Amazon CloudWatch Internet Monitor in New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-internet-monitor-integration/
+keywords:
+ - aws
+ - amazon web services
+ - cloudwatch
+ - monitor
+ - internet
+dashboards:
+ - amazon-cloudwatch-internet-monitor
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-cloudwatch-internet-monitor
diff --git a/quickstarts/aws/amazon-cloudwatch-internet-monitor/logo.png b/quickstarts/aws/amazon-cloudwatch-internet-monitor/logo.png
new file mode 100644
index 0000000000..2bac187c8a
Binary files /dev/null and b/quickstarts/aws/amazon-cloudwatch-internet-monitor/logo.png differ
diff --git a/quickstarts/aws/amazon-codebuild/config.yml b/quickstarts/aws/amazon-codebuild/config.yml
new file mode 100644
index 0000000000..a4867ac56a
--- /dev/null
+++ b/quickstarts/aws/amazon-codebuild/config.yml
@@ -0,0 +1,32 @@
+id: e1dd597a-2768-4096-8fbd-b6f53874a16a
+slug: amazon-codebuild
+description: |-
+ ## What is Amazon CodeBuild?
+ AWS CodeBuild is a fully managed build service that compiles your source code, runs unit tests, and produces artifacts that are ready to deploy. CodeBuild eliminates the need to provision, manage, and scale your own build servers.
+ ### Get started!
+ Start monitoring Amazon CodeBuild by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-codebuild-monitoring-integration/) to learn more about New Relic monitoring for Amazon Codebuild.
+summary: |-
+ Monitor Amazon CodeBuild by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon CodeBuild
+documentation:
+ - name: Amazon CodeBuild installation docs
+ description: |
+ Monitor Amazon CodeBuild by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-codebuild-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - CodeBuild
+alertPolicies:
+ - amazon-codebuild
+dashboards:
+ - amazon-codebuild
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-codebuild/logo.png b/quickstarts/aws/amazon-codebuild/logo.png
new file mode 100644
index 0000000000..ee541b7785
Binary files /dev/null and b/quickstarts/aws/amazon-codebuild/logo.png differ
diff --git a/quickstarts/aws/amazon-database-migration-service/config.yml b/quickstarts/aws/amazon-database-migration-service/config.yml
new file mode 100644
index 0000000000..2230e137a7
--- /dev/null
+++ b/quickstarts/aws/amazon-database-migration-service/config.yml
@@ -0,0 +1,33 @@
+id: c93fbfb6-5dd7-47e8-a4e3-011356721998
+slug: amazon-database-migration-service
+description: |-
+ ## What is Amazon Database Migration Service?
+ AWS Database Migration Service (AWS DMS) is a web service you can use to migrate data from your database that is on-premises, on an Amazon Relational Database Service (Amazon RDS) DB instance, or in a database on an Amazon Elastic Compute Cloud (Amazon EC2) instance to a database on an AWS service.
+ ### Get started!
+ Start monitoring Amazon Database Migration Service by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-database-migration-service-monitoring-integration/) to learn more about New Relic monitoring for Amazon Database Migration Service.
+summary: |-
+ Monitor Amazon Database Migration Service by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Database Migration Service
+documentation:
+ - name: Amazon Database Migration Service installation docs
+ description: |
+ Monitor Amazon Database Migration Service by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-database-migration-service-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - dms
+ - database migration service
+alertPolicies:
+ - amazon-database-migration-service
+dashboards:
+ - amazon-database-migration-service
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-database-migration-service/logo.png b/quickstarts/aws/amazon-database-migration-service/logo.png
new file mode 100644
index 0000000000..5cb1e87a7c
Binary files /dev/null and b/quickstarts/aws/amazon-database-migration-service/logo.png differ
diff --git a/quickstarts/aws/amazon-datasync/config.yml b/quickstarts/aws/amazon-datasync/config.yml
new file mode 100644
index 0000000000..8491f5e5f4
--- /dev/null
+++ b/quickstarts/aws/amazon-datasync/config.yml
@@ -0,0 +1,30 @@
+id: 1d1342c3-bec7-4cb2-b600-1e768d976e43
+slug: amazon-datasync
+description: |-
+ ## What is Amazon DataSync?
+ AWS DataSync is a secure, online service that automates and accelerates moving data between on premises and AWS Storage services. DataSync can copy data between Network File System (NFS) shares, Server Message Block (SMB) shares, Hadoop Distributed File Systems (HDFS), self-managed object storage, AWS Snowcone, Amazon Simple Storage Service (Amazon S3) buckets, Amazon Elastic File System (Amazon EFS) file systems, Amazon FSx for Windows File Server file systems, Amazon FSx for Lustre file systems, Amazon FSz for OpenZFS file systems, and Amazon FSx for NetApp ONTAP file systems.
+ ### Get started!
+ Start monitoring Amazon DataSync by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-datasync-monitoring-integration/) to learn more about New Relic monitoring for Amazon DataSync.
+summary: |-
+ Monitor Amazon DataSync by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon DataSync
+documentation:
+ - name: Amazon DataSync installation docs
+ description: |
+ Monitor Amazon DataSync by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-datasync-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - DataSync
+dashboards:
+ - amazon-datasync
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-datasync/logo.png b/quickstarts/aws/amazon-datasync/logo.png
new file mode 100644
index 0000000000..a4c9660d8a
Binary files /dev/null and b/quickstarts/aws/amazon-datasync/logo.png differ
diff --git a/quickstarts/aws/amazon-elastictranscoder/config.yml b/quickstarts/aws/amazon-elastictranscoder/config.yml
new file mode 100644
index 0000000000..4ab2bedbc6
--- /dev/null
+++ b/quickstarts/aws/amazon-elastictranscoder/config.yml
@@ -0,0 +1,32 @@
+id: 6753d1a3-c1d7-4b71-abc9-45e7e55df1a1
+slug: amazon-elastictranscoder
+description: |-
+ ## What is Amazon Elastic Transcoder?
+ Amazon Elastic Transcoder is media transcoding in the cloud. It is designed to be a highly scalable, easy to use and a cost effective way for developers and businesses to convert (or “transcode”) media files from their source format into versions that will playback on devices like smartphones, tablets and PCs.
+ ### Get started!
+ Start monitoring Amazon Elastic Transcoder by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-elastictranscoder-monitoring-integration/) to learn more about New Relic monitoring for Amazon elastictranscoder.
+summary: |-
+ Monitor Amazon Elastic Transcoder by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Elastic Transcoder
+documentation:
+ - name: Amazon Elastic Transcoder installation docs
+ description: |
+ Monitor Amazon Elastic Transcoder by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-elastictranscoder-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - elastictranscoder
+alertPolicies:
+ - amazon-elastictranscoder
+dashboards:
+ - amazon-elastictranscoder
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-elastictranscoder/logo.png b/quickstarts/aws/amazon-elastictranscoder/logo.png
new file mode 100644
index 0000000000..13bd8180bf
Binary files /dev/null and b/quickstarts/aws/amazon-elastictranscoder/logo.png differ
diff --git a/quickstarts/aws/amazon-gamelift/config.yml b/quickstarts/aws/amazon-gamelift/config.yml
new file mode 100644
index 0000000000..2e17c0d726
--- /dev/null
+++ b/quickstarts/aws/amazon-gamelift/config.yml
@@ -0,0 +1,30 @@
+id: cf8d67fe-fd29-4d75-bd62-415d704306b8
+slug: amazon-gamelift
+description: |-
+ ## What is Amazon GameLift?
+ Amazon GameLift can deploy, operate, and scale dedicated, low-cost servers in the cloud for session-based multiplayer games. Built on AWS global computing infrastructure, Amazon GameLift helps deliver high-performance, high-reliability game servers while dynamically scaling your resource usage to meet worldwide player demand.
+ ### Get started!
+ Start monitoring Amazon GameLift by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-gamelift-monitoring-integration/) to learn more about New Relic monitoring for Amazon GameLift.
+summary: |-
+ Monitor Amazon GameLift by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon GameLift
+documentation:
+ - name: Amazon GameLift installation docs
+ description: |
+ Monitor Amazon GameLift by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-gamelift-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - GameLift
+dashboards:
+ - amazon-gamelift
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-gamelift/logo.png b/quickstarts/aws/amazon-gamelift/logo.png
new file mode 100644
index 0000000000..a9631f7bf6
Binary files /dev/null and b/quickstarts/aws/amazon-gamelift/logo.png differ
diff --git a/quickstarts/aws/amazon-inspector/config.yml b/quickstarts/aws/amazon-inspector/config.yml
new file mode 100644
index 0000000000..4c6a47a5d7
--- /dev/null
+++ b/quickstarts/aws/amazon-inspector/config.yml
@@ -0,0 +1,32 @@
+id: 41e17e73-73b8-4351-a3fb-07314bddca48
+slug: amazon-inspector
+description: |-
+ ## What is Amazon Inspector?
+ Amazon Inspector is a vulnerability management service that continuously scans your AWS workloads for software vulnerabilities and unintended network exposure. Amazon Inspector automatically discovers and scans running Amazon EC2 instances, container images in Amazon Elastic Container Registry (Amazon ECR), and AWS Lambda functions for known software vulnerabilities and unintended network exposure.
+ ### Get started!
+ Start monitoring Amazon Inspector by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-inspector-monitoring-integration/) to learn more about New Relic monitoring for Amazon Inspector.
+summary: |-
+ Monitor Amazon Inspector by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Inspector
+documentation:
+ - name: Amazon Inspector installation docs
+ description: |
+ Monitor Amazon Inspector by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-inspector-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - inspector
+dashboards:
+ - amazon-inspector
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-inspector
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-inspector/logo.png b/quickstarts/aws/amazon-inspector/logo.png
new file mode 100644
index 0000000000..7c78744188
Binary files /dev/null and b/quickstarts/aws/amazon-inspector/logo.png differ
diff --git a/quickstarts/aws/amazon-keyspaces/config.yml b/quickstarts/aws/amazon-keyspaces/config.yml
new file mode 100644
index 0000000000..3227c1d62e
--- /dev/null
+++ b/quickstarts/aws/amazon-keyspaces/config.yml
@@ -0,0 +1,34 @@
+id: c42677b7-42b0-445a-9e25-5b684bc8652e
+slug: amazon-keyspaces
+description: |-
+ ## What is Amazon Keyspaces?
+ Amazon Keyspaces (for Apache Cassandra) is a scalable, highly available, and managed Apache Cassandra–compatible database service. With Amazon Keyspaces, you can run your Cassandra workloads on AWS using the same Cassandra application code and developer tools that you use today.
+ ### Get started!
+ Start monitoring Amazon Keyspaces by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-keyspaces-monitoring-integration/) to learn more about New Relic monitoring for Amazon Keyspaces.
+summary: |-
+ Monitor Amazon Keyspaces by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Keyspaces
+documentation:
+ - name: Amazon Keyspaces installation docs
+ description: |
+ Monitor Amazon Keyspaces by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-keyspaces-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - Keyspaces
+ - amazon keyspaces
+ - cassandra
+alertPolicies:
+ - amazon-keyspaces
+dashboards:
+ - amazon-keyspaces
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
diff --git a/quickstarts/aws/amazon-keyspaces/logo.png b/quickstarts/aws/amazon-keyspaces/logo.png
new file mode 100644
index 0000000000..816569da1a
Binary files /dev/null and b/quickstarts/aws/amazon-keyspaces/logo.png differ
diff --git a/quickstarts/aws/amazon-sagemaker/config.yml b/quickstarts/aws/amazon-sagemaker/config.yml
new file mode 100644
index 0000000000..7e8c7fb2f7
--- /dev/null
+++ b/quickstarts/aws/amazon-sagemaker/config.yml
@@ -0,0 +1,32 @@
+id: 7ed6c23d-b8ee-4d2e-b983-f552c7820960
+slug: amazon-sagemaker
+description: |-
+ ## What is Amazon Sagemaker?
+ Amazon SageMaker is a fully managed machine learning service. With SageMaker, data scientists and developers can quickly and easily build and train machine learning models, and then directly deploy them into a production-ready hosted environment.
+ ### Get started!
+ Start monitoring Amazon Sagemaker by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-sagemaker-monitoring-integration/) to learn more about New Relic monitoring for Amazon Sagemaker.
+summary: |-
+ Monitor Amazon Sagemaker by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Sagemaker
+documentation:
+ - name: Amazon Sagemaker installation docs
+ description: |
+ Monitor Amazon Sagemaker by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-sagemaker-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - Sagemaker
+alertPolicies:
+ - amazon-sagemaker
+dashboards:
+ - amazon-sagemaker
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-sagemaker/logo.png b/quickstarts/aws/amazon-sagemaker/logo.png
new file mode 100644
index 0000000000..9eacf9ab4e
Binary files /dev/null and b/quickstarts/aws/amazon-sagemaker/logo.png differ
diff --git a/quickstarts/aws/amazon-security-lake/config.yml b/quickstarts/aws/amazon-security-lake/config.yml
new file mode 100644
index 0000000000..70b92ab21b
--- /dev/null
+++ b/quickstarts/aws/amazon-security-lake/config.yml
@@ -0,0 +1,48 @@
+id: a9e632bf-9467-4e0d-92cd-e4b16eebef03
+slug: aws-security-lake
+description: |-
+ ## What is Amazon Security Lake?
+
+ Amazon Security Lake allow you to automatically centralize your security data in just a few steps.
+
+
+ ### Get started!
+
+ Start monitoring Amazon Security Lake by forwarding logs to New Relic using a Lambda function.
+
+ Check out our Amazon Security Lake documentation to instrument your cloud service and manage the stability, scalability, and reliability of your systems with New Relic's infrastructure monitoring capabilities.
+
+ ### More info
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration/) to learn more about New Relic monitoring for Amazon Security Lake.
+summary: |-
+ Monitor Amazon Security Lake by sending logs to New Relic
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Security Lake
+documentation:
+ - name: Amazon Security Lake integration guide
+ description: |
+ Monitor Amazon Security Lake by sending logs to New Relic via Lambda function
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-security-lake-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - networking
+ - security lake
+ - vpc flow logs
+ - security hub
+ - route 53 query resolver
+ - cloudtrail
+dashboards:
+ - amazon-security-lake-vpc-flowlogs
+ - amazon-security-lake-security-hub
+ - amazon-security-lake-route53-resolver-query-logs
+ - amazon-security-lake-cloudtrail-logs
+installPlans:
+ - aws-security-lake
+dataSourceIds:
+ - amazon-security-lake
diff --git a/quickstarts/aws/amazon-security-lake/logo.svg b/quickstarts/aws/amazon-security-lake/logo.svg
new file mode 100644
index 0000000000..94db88def4
--- /dev/null
+++ b/quickstarts/aws/amazon-security-lake/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-simpleworkflow/config.yml b/quickstarts/aws/amazon-simpleworkflow/config.yml
new file mode 100644
index 0000000000..2a990d8cbb
--- /dev/null
+++ b/quickstarts/aws/amazon-simpleworkflow/config.yml
@@ -0,0 +1,32 @@
+id: becf8b30-f2a9-4f0e-ab72-3f62fe1b80d9
+slug: amazon-simpleworkflow
+description: |-
+ ## What is Amazon SimpleWorkFlow?
+ The Amazon Simple Workflow Service (Amazon SWF) makes it easy to build applications that coordinate work across distributed components. In Amazon SWF, a task represents a logical unit of work that is performed by a component of your application. Coordinating tasks across the application involves managing intertask dependencies, scheduling, and concurrency in accordance with the logical flow of the application.
+ ### Get started!
+ Start monitoring Amazon SimpleWorkFlow by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-simpleworkflow-monitoring-integration/) to learn more about New Relic monitoring for Amazon SimpleWorkFlow.
+summary: |-
+ Monitor Amazon SimpleWorkFlow by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon SimpleWorkFlow
+documentation:
+ - name: Amazon SimpleWorkFlow installation docs
+ description: |
+ Monitor Amazon SimpleWorkFlow by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-simpleworkflow-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - SimpleWorkFlow
+alertPolicies:
+ - amazon-simpleworkflow
+dashboards:
+ - amazon-simpleworkflow
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-simpleworkflow/logo.png b/quickstarts/aws/amazon-simpleworkflow/logo.png
new file mode 100644
index 0000000000..52fce622e2
Binary files /dev/null and b/quickstarts/aws/amazon-simpleworkflow/logo.png differ
diff --git a/quickstarts/aws/amazon-timestream/config.yml b/quickstarts/aws/amazon-timestream/config.yml
new file mode 100644
index 0000000000..3b9717e2d4
--- /dev/null
+++ b/quickstarts/aws/amazon-timestream/config.yml
@@ -0,0 +1,32 @@
+id: 2e7a2e20-71b6-43e2-bfa7-a2d09780e558
+slug: amazon-timestream
+description: |-
+ ## What is Amazon Timestream?
+ Amazon Timestream is a serverless scalable time-series database service to store and analyze up to trillions of events per day. It automatically scales up or down to adjust capacity and performance.
+ ### Get started!
+ Start monitoring Amazon Timestream by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-timestream-monitoring-integration/) to learn more about New Relic monitoring for Amazon Timestream.
+summary: |-
+ Monitor Amazon Timestream by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Timestream
+documentation:
+ - name: Amazon Timestream installation docs
+ description: |
+ Monitor Amazon Timestream by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-timestream-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - timestream
+dashboards:
+ - amazon-timestream
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-timestream
diff --git a/quickstarts/aws/amazon-timestream/logo.png b/quickstarts/aws/amazon-timestream/logo.png
new file mode 100644
index 0000000000..5e2f9bee40
Binary files /dev/null and b/quickstarts/aws/amazon-timestream/logo.png differ
diff --git a/quickstarts/aws/amazon-transfer-family/config.yml b/quickstarts/aws/amazon-transfer-family/config.yml
new file mode 100644
index 0000000000..509c79f7ae
--- /dev/null
+++ b/quickstarts/aws/amazon-transfer-family/config.yml
@@ -0,0 +1,34 @@
+id: 932165c7-b93a-42e7-8058-1b847cea522a
+slug: amazon-transfer-family
+description: |-
+ ## What is Amazon Transfer Family?
+ Amazon Transfer Family securely scales your recurring business-to-business file transfers to AWS Storage services using SFTP, FTPS, FTP, and AS2 protocols.
+ ### Get started!
+ Start monitoring Amazon Transfer Family by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-transfer-family-monitoring-integration/) to learn more about New Relic monitoring for Amazon Transfer Family.
+summary: |-
+ Monitor Amazon Transfer Family by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Transfer Family
+documentation:
+ - name: Amazon Transfer Family installation docs
+ description: |
+ Monitor Amazon Transfer Family by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-transfer-family-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - amazon transfer Family
+ - amazon transfer
+ - transfer
+dashboards:
+ - amazon-transfer-family
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-transfer-family
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-transfer-family/logo.png b/quickstarts/aws/amazon-transfer-family/logo.png
new file mode 100644
index 0000000000..742673e19c
Binary files /dev/null and b/quickstarts/aws/amazon-transfer-family/logo.png differ
diff --git a/quickstarts/aws/amazon-vpc-lattice/config.yml b/quickstarts/aws/amazon-vpc-lattice/config.yml
new file mode 100644
index 0000000000..dd5ec92759
--- /dev/null
+++ b/quickstarts/aws/amazon-vpc-lattice/config.yml
@@ -0,0 +1,39 @@
+id: 47e7ef3d-d2e4-4556-bd06-8e93633f301e
+slug: amazon-vpc-lattice
+description: |
+ ## Monitor your VPC Lattice service in New Relic's observability platform
+ Our lattice integration reports data from your NAT Gateway service to your New Relic account using AWS CloudWatch Metric Streams and Amazon Firehose.
+ ## Get started!
+ This integration uses [AWS CloudWatch Metric streams](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) to get VPC Lattice data into New Relic.
+ ## About this integration
+ With this integration you can monitor key information about your VPC Lattice service.
+ - Request count
+ - Byte traffic
+ - Success rate
+ - Request time
+summary: |
+ Use the New Relic - Amazon VPC Lattice Integration to monitor your AWS service traffic.
+icon: logo.jpeg
+level: New Relic
+authors:
+ - New Relic
+ - Joseph Counts
+title: Amazon VPC Lattice
+documentation:
+ - name: Amazon VPC Lattice integration docs
+ description: |
+ Monitor your NAT Gateway traffic using AWS CloudWatch Metric Streams
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-vpc-lattice-monitoring-integration/
+keywords:
+ - aws
+ - amazon
+ - lattice
+ - metrics
+ - vpc
+ - network
+dataSourceIds:
+ - amazon-vpc-lattice
+ - amazon-cloudwatch-metric-streams
+dashboards:
+ - amazon-vpc-lattice-access-logs
+ - amazon-vpc-lattice-metrics
diff --git a/quickstarts/aws/amazon-vpc-lattice/logo.jpeg b/quickstarts/aws/amazon-vpc-lattice/logo.jpeg
new file mode 100644
index 0000000000..3ef360ee2f
Binary files /dev/null and b/quickstarts/aws/amazon-vpc-lattice/logo.jpeg differ
diff --git a/quickstarts/aws/amazon-vpc-nat-gateway/config.yml b/quickstarts/aws/amazon-vpc-nat-gateway/config.yml
new file mode 100644
index 0000000000..a35a0601f4
--- /dev/null
+++ b/quickstarts/aws/amazon-vpc-nat-gateway/config.yml
@@ -0,0 +1,38 @@
+id: 16e409db-33be-4cf2-9f21-363f09c43898
+slug: amazon-vpc-natgateway
+description: |
+ ## Monitor your NAT Gateway in New Relic's observability platform
+ Our NAT Gateway integration reports data from your NAT Gateway service to your New Relic account using AWS CloudWatch Metric Streams.
+ ## Get started!
+ This integration uses [AWS CloudWatch Metric streams](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/connect/aws-metric-stream/) to get NAT Gateway traffic data into New Relic.
+ ## About this integration
+ With this integration you can monitor key traffic information about your NAT Gateway.
+ - Track your connection established rate
+ - View idle connection timeouts
+ - Track Byte traffic
+ - Monitor your active connections over time
+ - Check for packet drops or port allocation errors over time
+summary: |
+ Use the New Relic - Amazon VPC NAT Gateway Integration to monitor traffic to and from your NAT Gateway.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+ - Joseph Counts
+title: Amazon VPC NAT Gateway
+documentation:
+ - name: Amazon VPC NAT Gateway integration docs
+ description: |
+ Monitor your NAT Gateway traffic using AWS CloudWatch Metric Streams
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-nat-gateway-monitoring-integration/
+keywords:
+ - aws
+ - amazon
+ - nat gateway
+ - metrics
+ - vpc
+ - network
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+dashboards:
+ - amazon-vpc-natgateway
diff --git a/quickstarts/aws/amazon-vpc-nat-gateway/logo.svg b/quickstarts/aws/amazon-vpc-nat-gateway/logo.svg
new file mode 100644
index 0000000000..0568d19aba
--- /dev/null
+++ b/quickstarts/aws/amazon-vpc-nat-gateway/logo.svg
@@ -0,0 +1,18 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-workmail/config.yml b/quickstarts/aws/amazon-workmail/config.yml
new file mode 100644
index 0000000000..5626638919
--- /dev/null
+++ b/quickstarts/aws/amazon-workmail/config.yml
@@ -0,0 +1,32 @@
+id: 9426b0ae-8888-4dac-af07-de931af992a0
+slug: amazon-workmail
+description: |-
+ ## What is Amazon WorkMail?
+ Amazon WorkMail is a secure, managed business email and calendar service with support for existing desktop and mobile email client applications. Amazon WorkMail gives users the ability to seamlessly access their email, contacts, and calendars using the client application of their choice, including Microsoft Outlook, native iOS and Android email applications, any client application supporting the IMAP protocol, or directly through a web browser.
+ ### Get started!
+ Start monitoring Amazon WorkMail by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-workmail-monitoring-integration/) to learn more about New Relic monitoring for Amazon WorkMail.
+summary: |-
+ Monitor Amazon WorkMail by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon WorkMail
+documentation:
+ - name: Amazon WorkMail installation docs
+ description: |
+ Monitor Amazon WorkMail by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-workmail-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - WorkMail
+dashboards:
+ - amazon-workmail
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-workmail
diff --git a/quickstarts/aws/amazon-workmail/logo.png b/quickstarts/aws/amazon-workmail/logo.png
new file mode 100644
index 0000000000..c09ddb0302
Binary files /dev/null and b/quickstarts/aws/amazon-workmail/logo.png differ
diff --git a/quickstarts/aws/amazon-workspaces/config.yml b/quickstarts/aws/amazon-workspaces/config.yml
new file mode 100644
index 0000000000..db77ba4438
--- /dev/null
+++ b/quickstarts/aws/amazon-workspaces/config.yml
@@ -0,0 +1,32 @@
+id: 440596f8-d11f-4656-b21a-0b0bb02bc29d
+slug: amazon-workspaces
+description: |-
+ ## What is Amazon WorkSpaces?
+ Amazon WorkSpaces is a fully managed desktop virtualization service for Windows and Linux that enables you to access resources from any supported device.
+ ### Get started!
+ Start monitoring Amazon WorkSpaces by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-workspaces-monitoring-integration/) to learn more about New Relic monitoring for Amazon WorkSpaces.
+summary: |-
+ Monitor Amazon WorkSpaces by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon WorkSpaces
+documentation:
+ - name: Amazon WorkSpaces installation docs
+ description: |
+ Monitor Amazon WorkSpaces by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/amazon-workspaces-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - WorkSpaces
+dashboards:
+ - amazon-workspaces
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - amazon-workspaces
\ No newline at end of file
diff --git a/quickstarts/aws/amazon-workspaces/logo.png b/quickstarts/aws/amazon-workspaces/logo.png
new file mode 100644
index 0000000000..867ba24f54
Binary files /dev/null and b/quickstarts/aws/amazon-workspaces/logo.png differ
diff --git a/quickstarts/aws/aws-chatbot/config.yml b/quickstarts/aws/aws-chatbot/config.yml
new file mode 100644
index 0000000000..4c3ab16d5b
--- /dev/null
+++ b/quickstarts/aws/aws-chatbot/config.yml
@@ -0,0 +1,32 @@
+id: 94a5c325-ad12-4419-8c6b-9aee101a76d1
+slug: aws-chatbot
+description: |-
+ ## What is AWS Chatbot?
+ AWS Chatbot is an AWS service that enables DevOps and software development teams to use messaging program chat rooms to monitor and respond to operational events in their AWS Cloud. AWS Chatbot processes AWS service notifications from Amazon Simple Notification Service (Amazon SNS), and forwards them to chat rooms so teams can analyze and act on them immediately, regardless of location.
+ ### Get started!
+ Start monitoring AWS Chatbot by using AWS Kinesis Firehose to send logs to New Relic! Take a look at our documentation for information on how to set this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration/) to learn more about New Relic monitoring for AWS Chatbot.
+summary: |-
+ Monitor AWS Chatbot by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: AWS Chatbot
+documentation:
+ - name: AWS Chatbot installation docs
+ description: |
+ Monitor AWS Chatbot by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-chatbot-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - networking
+dashboards:
+ - aws-chatbot
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - aws-chatbot
\ No newline at end of file
diff --git a/quickstarts/aws/aws-chatbot/logo.png b/quickstarts/aws/aws-chatbot/logo.png
new file mode 100644
index 0000000000..22731fe7e5
Binary files /dev/null and b/quickstarts/aws/aws-chatbot/logo.png differ
diff --git a/quickstarts/aws/aws-elemental-mediatailor/config.yml b/quickstarts/aws/aws-elemental-mediatailor/config.yml
new file mode 100644
index 0000000000..d35f588a50
--- /dev/null
+++ b/quickstarts/aws/aws-elemental-mediatailor/config.yml
@@ -0,0 +1,35 @@
+id: 483a4d68-5838-4b7a-83b1-0abc7bc454c7
+slug: aws-elemental-mediatailor
+description: |-
+ ## What is AWS Elemental MediaTailor?
+ AWS Elemental MediaTailor is a channel assembly and personalized ad-insertion service for video providers to create linear over-the-top (OTT) channels using existing video content. The service then lets you monetize those channels or other live streams with personalized advertising.
+ ### Get started!
+ Start monitoring AWS Elemental MediaTailor by connecting Amazon Web Services (AWS) to New Relic! Take a look at our documentation for information on how to set up this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration/) to learn more about New Relic monitoring for Amazon MediaTailor.
+summary: |-
+ Monitor AWS Elemental MediaTailor by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: AWS Elemental MediaTailor
+documentation:
+ - name: AWS Elemental MediaTailor installation docs
+ description: |
+ Monitor AWS Elemental MediaTailor by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-elemental-mediatailor-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - Elemental MediaTailor
+ - aws elemental media tailor
+ - elemental media tailor
+ - aws elemental mediatailor
+alertPolicies:
+ - aws-elemental-mediatailor
+dashboards:
+ - aws-elemental-mediatailor
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
\ No newline at end of file
diff --git a/quickstarts/aws/aws-elemental-mediatailor/logo.png b/quickstarts/aws/aws-elemental-mediatailor/logo.png
new file mode 100644
index 0000000000..94a7ac1abc
Binary files /dev/null and b/quickstarts/aws/aws-elemental-mediatailor/logo.png differ
diff --git a/quickstarts/aws/aws-lex/config.yml b/quickstarts/aws/aws-lex/config.yml
new file mode 100644
index 0000000000..e79668b0ed
--- /dev/null
+++ b/quickstarts/aws/aws-lex/config.yml
@@ -0,0 +1,31 @@
+id: 62698640-266d-4f4b-9894-f42f13de6b16
+slug: aws-lex
+description: |-
+ ## Monitor your Amazon Lex Metrics
+
+ With New Relic's Amazon Lex integration, you now can see all your Lex data on New Relic Instant Observability Platform.
+
+ ### Get started!
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration/) to learn more about New
+ Relic monitoring and integration with Amazon Lex.
+
+summary: Use New Relic - Amazon Lex Integration to monitor your bots with New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Lex
+documentation:
+ - name: Amazon Lex installation docs
+ description: |
+ Monitor Amazon Lex by connecting AWS to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-lex-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - lex
+dataSourceIds:
+ - aws-lex
+dashboards:
+ - aws-lex
\ No newline at end of file
diff --git a/quickstarts/aws/aws-lex/logo.png b/quickstarts/aws/aws-lex/logo.png
new file mode 100644
index 0000000000..68ba7e3646
Binary files /dev/null and b/quickstarts/aws/aws-lex/logo.png differ
diff --git a/quickstarts/aws/aws-polly/config.yml b/quickstarts/aws/aws-polly/config.yml
new file mode 100644
index 0000000000..03a6f6b5d7
--- /dev/null
+++ b/quickstarts/aws/aws-polly/config.yml
@@ -0,0 +1,31 @@
+id: a92448c6-19ab-4c6e-946d-22e4171e594f
+slug: aws-polly
+description: |-
+ ## Monitor your AWS PollyOperation and PollyLexicon Metrics
+
+ With New Relic's Amazon Polly integration, you now can see all your Polly data on New Relic Instant Observability Platform.
+
+ ### Get started!
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration/) to learn more about New
+ Relic monitoring and integration with Amazon Polly.
+
+summary: Use New Relic - Amazon Polly Integration to monitor your Polly utilizing Apps and Services with New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Polly
+documentation:
+ - name: Amazon Polly installation docs
+ description: |
+ Monitor Amazon Polly by connecting AWS to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-polly-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - polly
+dataSourceIds:
+ - aws-polly
+dashboards:
+ - aws-polly
diff --git a/quickstarts/aws/aws-polly/logo.png b/quickstarts/aws/aws-polly/logo.png
new file mode 100644
index 0000000000..c6c41a44e4
Binary files /dev/null and b/quickstarts/aws/aws-polly/logo.png differ
diff --git a/quickstarts/aws/aws-rekognition/config.yml b/quickstarts/aws/aws-rekognition/config.yml
new file mode 100644
index 0000000000..792e2e7536
--- /dev/null
+++ b/quickstarts/aws/aws-rekognition/config.yml
@@ -0,0 +1,31 @@
+id: b8259c45-0324-4cde-86a0-7c7df8dab9a3
+slug: aws-rekognition
+description: |-
+ ## Monitor your AWS Rekognition and AWS Rekognition Operation Metrics
+
+ With New Relic's Amazon Rekognition integration, you now can see all your Rekognition data on New Relic Instant Observability Platform.
+
+ ### Get started!
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration/) to learn more about New
+ Relic monitoring and integration with Amazon Rekognition.
+
+summary: Use New Relic - Amazon Rekognition Integration to analyze your rekognition data with New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Rekognition
+documentation:
+ - name: Amazon Rekognition installation docs
+ description: |
+ Monitor AWS Rekognition by connecting AWS to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-rekognition-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - rekognition
+dataSourceIds:
+ - aws-rekognition
+dashboards:
+ - aws-rekognition
diff --git a/quickstarts/aws/aws-rekognition/logo.png b/quickstarts/aws/aws-rekognition/logo.png
new file mode 100644
index 0000000000..7b238651ed
Binary files /dev/null and b/quickstarts/aws/aws-rekognition/logo.png differ
diff --git a/quickstarts/aws/aws-textract/config.yml b/quickstarts/aws/aws-textract/config.yml
new file mode 100644
index 0000000000..1668a7ee3e
--- /dev/null
+++ b/quickstarts/aws/aws-textract/config.yml
@@ -0,0 +1,31 @@
+id: e519bc93-31fa-4375-9fa0-ac3e2620acc2
+slug: aws-textract
+description: |-
+ ## Monitor your AWS Textract Metrics
+
+ With New Relic's Amazon Textract integration, you now can see all your Textract data on New Relic Instant Observability Platform.
+
+ ### Get started!
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration/) to learn more about New
+ Relic monitoring and integration with Amazon Textract.
+
+summary: Use New Relic - Amazon Textract Integration to monitor your Textract utilizing Apps and Services with New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Textract
+documentation:
+ - name: Amazon Textract installation docs
+ description: |
+ Monitor Amazon Textract by connecting AWS to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-textract-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - textract
+dataSourceIds:
+ - aws-textract
+dashboards:
+ - aws-textract
diff --git a/quickstarts/aws/aws-textract/logo.png b/quickstarts/aws/aws-textract/logo.png
new file mode 100644
index 0000000000..c4d7bccafb
Binary files /dev/null and b/quickstarts/aws/aws-textract/logo.png differ
diff --git a/quickstarts/aws/aws-transcribe/config.yml b/quickstarts/aws/aws-transcribe/config.yml
new file mode 100644
index 0000000000..fafafd988b
--- /dev/null
+++ b/quickstarts/aws/aws-transcribe/config.yml
@@ -0,0 +1,32 @@
+id: 101d9711-2c67-493a-86cb-e672a8ba43ef
+slug: aws-transcribe
+description: |-
+ ## What is AWS Transcribe?
+ Amazon Transcribe is an automatic speech recognition service that uses machine learning models to convert audio to text. You can use Amazon Transcribe as a standalone transcription service or to add speech-to-text capabilities to any application.
+ ### Get started!
+ Start monitoring AWS Transcribe by using AWS Kinesis Firehose to send logs to New Relic! Take a look at our documentation for information on how to set this integration.
+ ### More info
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration/) to learn more about New Relic monitoring for AWS Transcribe.
+summary: |-
+ Monitor Amazon Transcribe by connecting AWS to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: AWS Transcribe
+documentation:
+ - name: AWS Transcribe installation docs
+ description: |
+ Monitor AWS Transcribe by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-transcribe-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - networking
+dashboards:
+ - aws-transcribe
+dataSourceIds:
+ - amazon-cloudwatch-metric-streams
+alertPolicies:
+ - aws-transcribe
\ No newline at end of file
diff --git a/quickstarts/aws/aws-transcribe/logo.png b/quickstarts/aws/aws-transcribe/logo.png
new file mode 100644
index 0000000000..2afb751ff3
Binary files /dev/null and b/quickstarts/aws/aws-transcribe/logo.png differ
diff --git a/quickstarts/aws/aws-translate/config.yml b/quickstarts/aws/aws-translate/config.yml
new file mode 100644
index 0000000000..2b074dd281
--- /dev/null
+++ b/quickstarts/aws/aws-translate/config.yml
@@ -0,0 +1,31 @@
+id: 97208883-0a4a-4c5b-9fc6-a06dee240c34
+slug: aws-translate
+description: |-
+ ## Monitor your AWS Translate Metrics
+
+ With New Relic's Amazon Translate integration, you now can see all your Transate data on New Relic Instant Observability Platform.
+
+ ### Get started!
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration/) to learn more about New
+ Relic monitoring and integration with Amazon Translate.
+
+summary: Use New Relic - Amazon Translate Integration to monitor your Translate utilizing Apps and Services with New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Translate
+documentation:
+ - name: Amazon Translate installation docs
+ description: |
+ Monitor Amazon Translate by connecting AWS to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-translate-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - translate
+dataSourceIds:
+ - aws-translate
+dashboards:
+ - aws-translate
diff --git a/quickstarts/aws/aws-translate/logo.png b/quickstarts/aws/aws-translate/logo.png
new file mode 100644
index 0000000000..3b2074af3d
Binary files /dev/null and b/quickstarts/aws/aws-translate/logo.png differ
diff --git a/quickstarts/aws/aws-verified-access/config.yml b/quickstarts/aws/aws-verified-access/config.yml
new file mode 100644
index 0000000000..7910ee0182
--- /dev/null
+++ b/quickstarts/aws/aws-verified-access/config.yml
@@ -0,0 +1,48 @@
+id: a474d202-84a7-4ca0-829c-e93b52027318
+slug: aws-verified-access
+description: |-
+ ## What is Amazon Verified Access?
+
+ AWS Verified Access allows you to provide secure network access without a VPN to corporate applications. Verified Access verifies each access request in real time and only connects users to the applications they are allowed to access, removing broad access to corporate applications, and reducing the associated risks.
+
+
+ ### Get started!
+
+ Start monitoring Amazon Veried Access by using AWS Kenesis Firehose to send logs to New Relic! Take a look at our documentation for information on how to set this integration.
+
+ ### About this integration
+
+ With this integration, you can keep up with important information about your Verified Access logo.svg
+
+ - Access attempt traffic
+ - Top denied attempts by IP Address
+ - Users attempting access from multiple IP Addresses
+ - Top accessed applications
+ - Real time logs on denied access attempts
+
+ ### More info
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-verified-access-monitoring-integration/) to learn more about New Relic monitoring for Amazon Verified Access.
+summary: |-
+ Monitor Amazon Verified Access by streaming Firehose logs into New Relic
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: Amazon Verified Access
+documentation:
+ - name: Amazon Verified Access installation docs
+ description: |
+ Monitor Amazon Verified by connecting AWS to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-verified-access-monitoring-integration/
+keywords:
+ - aws
+ - amazon web services
+ - networking
+dashboards:
+ - aws-verified-access
+installPlans:
+ - aws-verified-access
+dataSourceIds:
+ - amazon-verified-access
diff --git a/quickstarts/aws/aws-verified-access/logo.svg b/quickstarts/aws/aws-verified-access/logo.svg
new file mode 100644
index 0000000000..0568d19aba
--- /dev/null
+++ b/quickstarts/aws/aws-verified-access/logo.svg
@@ -0,0 +1,18 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/azure-openai/config.yml b/quickstarts/azure-openai/config.yml
new file mode 100644
index 0000000000..47c6d541b8
--- /dev/null
+++ b/quickstarts/azure-openai/config.yml
@@ -0,0 +1,46 @@
+id: 8c8be34e-2f80-4666-b599-29965477e9da
+slug: azure-openai
+title: Azure OpenAI
+
+description: |
+ ## Monitor your Azure OpenAI LLM Usage in New Relic
+
+ With the GPT integration, you'll have the ability to seamlessly monitor Azure OpenAI completion queries and simultaneously log useful statistics in a New Relic customizable dashboard about your requests.
+
+ By adding just two lines of code, users can gain access to key performance metrics such as cost, response time, and sample inputs/outputs. The dashboard also allows users to track total requests, average token/requests, and model names.
+
+ With New Relic fully customizable dashboard, users can add additional metrics based on their specific business requirements and needs.
+
+ Overall, New Relic Azure OpenAI integration provides real-time metrics around GPT applications to help businesses optimize usage, reduce costs, and achieve better results.
+
+summary: |
+ Seamlessly monitor your usage of Azure OpenAI’s GPT Series APIs using New Relic’s dashboard. You'll get access to real-time metrics that can help you optimize usage, reduce costs, and achieve better results.
+
+icon: logo.svg
+
+level: New Relic
+
+authors:
+ - New Relic
+ - Yogev Kriger
+
+documentation:
+ - name: Monitor Azure OpenAI
+ description: |
+ A lightweight tool to monitor your Azure OpenAI workload.
+ url: >-
+ https://github.com/newrelic/openai-api-monitoring
+
+keywords:
+ - featured
+ - azure openai
+ - openai
+ - ai
+ - gpt
+ - mlops
+ - llm
+
+dataSourceIds:
+ - llm-application
+alertPolicies:
+ - llm-application
diff --git a/data-sources/openai/openai-logo.svg b/quickstarts/azure-openai/logo.svg
similarity index 100%
rename from data-sources/openai/openai-logo.svg
rename to quickstarts/azure-openai/logo.svg
diff --git a/quickstarts/azure/azure-anomaly-detector/config.yml b/quickstarts/azure/azure-anomaly-detector/config.yml
new file mode 100644
index 0000000000..e0862f4182
--- /dev/null
+++ b/quickstarts/azure/azure-anomaly-detector/config.yml
@@ -0,0 +1,41 @@
+id: 5e73aab7-1186-4aa9-a321-089690d47f1f
+slug: azure-anomaly-detector
+description: |-
+ ## What is Azure Anomaly Detector?
+
+ Azure Anomaly Detector is an AI service with a set of APIs, which enables you to monitor and detect anomalies in your time series data with little machine learning (ML) knowledge, either batch validation or real-time inference.
+
+ ### New Relic Azure Anomaly Detector quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, successful calls, success rate and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Anomaly Detector with New Relic?
+
+ [New Relic Azure Anomaly Detector](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Anomaly Detector via different metrics including total calls, successful calls, success rate and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Anomaly Detector is critical to track the performance through key metrics. Download New Relic Azure Anomaly Detector monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Anomaly Detector.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Anomaly Detector
+documentation:
+ - name: Azure Anomaly Detector installation docs.
+ description: |
+ Monitor Azure Anomaly Detector by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - anomaly detector
+ - product partnerships
+dashboards:
+ - azure-anomaly-detector
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-anomaly-detector/logo.png b/quickstarts/azure/azure-anomaly-detector/logo.png
new file mode 100644
index 0000000000..b7c0ca1498
Binary files /dev/null and b/quickstarts/azure/azure-anomaly-detector/logo.png differ
diff --git a/quickstarts/azure/azure-app-configuration/config.yml b/quickstarts/azure/azure-app-configuration/config.yml
new file mode 100644
index 0000000000..ff10d09177
--- /dev/null
+++ b/quickstarts/azure/azure-app-configuration/config.yml
@@ -0,0 +1,40 @@
+id: 936ad19f-b447-4d17-a7f6-9fee6df5d94a
+slug: azure-app-configuration
+description: |-
+ ## What is Azure App Configuration?
+
+ Azure App Configuration provides a service to centrally manage application settings and feature flags.
+
+ ### New Relic Azure AppConfiguration quickstart features
+
+ A standard dashboard that tracks key indicators like daily storage usage, http incoming request count, http incoming request duration and throttled http request count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure AppConfiguration with New Relic?
+
+ [New Relic Azure App Configuration](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure App Configuration via different metrics including daily storage usage, http incoming request count, http incoming request duration and throttled http request count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure App Configuration is critical to track the performance through key metrics. Download New Relic Azure App Configuration monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure App Configuration Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure App Configuration
+documentation:
+ - name: Azure App Configuration installation docs.
+ description: |
+ Monitor Azure App Configuration by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-configuration-monitoring-integration/
+keywords:
+ - azure
+ - app configuration
+ - product partnerships
+dashboards:
+ - azure-app-configuration
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-app-configuration/logo.png b/quickstarts/azure/azure-app-configuration/logo.png
new file mode 100644
index 0000000000..9e3e40996e
Binary files /dev/null and b/quickstarts/azure/azure-app-configuration/logo.png differ
diff --git a/quickstarts/azure/azure-app-service-environment/config.yml b/quickstarts/azure/azure-app-service-environment/config.yml
new file mode 100644
index 0000000000..721a404c36
--- /dev/null
+++ b/quickstarts/azure/azure-app-service-environment/config.yml
@@ -0,0 +1,40 @@
+id: 35b73600-922b-49f9-9702-836771340372
+slug: azure-app-service-environment
+title: Azure App Service Environment
+description: |-
+ ## What is Azure App Service Environment?
+
+ App Service Environment represents the collection of physical resources for the App service. An App Service Environment can have multiple web apps. In other words, we can have multiple web apps in an App Service Environment.
+
+ ### New Relic Azure App Service Environment quickstart features
+
+ A standard dashboard that tracks key indicators like bytes received, bytes sent, cpu percentage, disk queue length, memory percentage. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure App Service Environment with New Relic?
+
+ [New Relic Azure App Service Environment](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure App Service Environment via different metrics including account bytes received, bytes sent, cpu percentage, disk queue length, memory percentage.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure App Service Environment is critical to tracking the performance through key metrics. Install the New Relic Azure App Service Environment monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure App Service Environment.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure App Service Environment installation docs
+ description: |
+ Monitor Azure App Service Environment by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-environment-monitoring-integration/
+keywords:
+ - azure
+ - app service environment
+ - product partnerships
+dashboards:
+ - azure-app-service-environment
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-app-service-environment/logo.png b/quickstarts/azure/azure-app-service-environment/logo.png
new file mode 100644
index 0000000000..3413fa5208
Binary files /dev/null and b/quickstarts/azure/azure-app-service-environment/logo.png differ
diff --git a/quickstarts/azure/azure-app-service-plan/config.yml b/quickstarts/azure/azure-app-service-plan/config.yml
new file mode 100644
index 0000000000..e6bc13dff4
--- /dev/null
+++ b/quickstarts/azure/azure-app-service-plan/config.yml
@@ -0,0 +1,40 @@
+id: 9dc69e3b-c6c6-4b3e-b832-0f1ceab6c17b
+slug: azure-app-service-plan
+title: Azure App Service Plan
+description: |-
+ ## What is Azure App Service Plan?
+
+ Azure App Service Plan represents the collection of physical resources for the App Service. An App Service Plan can have multiple web apps. In other words, we can have multiple web apps in an app service plan.
+
+ ### New Relic Azure App Service Plan quickstart features
+
+ A standard dashboard that tracks key indicators like bytes received, bytes sent, CPU percentage, disk queue length, memory percentage. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure App Service Plan with New Relic?
+
+ [New Relic Azure App Service Plan](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan/) monitoring quickstart empowers you to track the performance of Azure App Service Plan via different metrics including bytes received, bytes sent, CPU percentage, disk queue length, memory percentage.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure App Service Plan is critical to track the performance through via key metrics. Download New Relic Azure App Service Plan monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure App Service Plan Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure App Service Plan installation docs
+ description: |
+ Monitor Azure App Service Plan by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-app-service-plan/
+keywords:
+ - azure
+ - app service plan
+ - product partnerships
+dashboards:
+ - azure-app-service-plan
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-app-service-plan/logo.png b/quickstarts/azure/azure-app-service-plan/logo.png
new file mode 100644
index 0000000000..79e4169adb
Binary files /dev/null and b/quickstarts/azure/azure-app-service-plan/logo.png differ
diff --git a/quickstarts/azure/azure-application-insights/config.yml b/quickstarts/azure/azure-application-insights/config.yml
new file mode 100644
index 0000000000..8f332fc46b
--- /dev/null
+++ b/quickstarts/azure/azure-application-insights/config.yml
@@ -0,0 +1,41 @@
+id: 53d48c5a-1f30-4793-b742-a04929bf1d4b
+slug: azure-application-insights
+title: Azure Application Insights
+description: |-
+ ## What is Azure Application Insights?
+
+ Azure Application Insights is a service that monitors the performance of live web applications and detects anomalies. It is an extension of Azure Monitor and supports multiple platforms, such as .NET, Java, Python, and Node.js. It helps developers to understand how their applications are used and user interaction.
+
+ ### New Relic Azure Application Insights quickstart features
+
+ A standard dashboard that tracks key indicators like receiving response time, availability, dependency call failures and browser exceptions. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Application Insights with New Relic?
+
+ [New Relic Azure Application Insights](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Application Insights via different metrics including receiving response time, availability, dependency call failures and browser exceptions.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Application Insights is critical to tracking the performance through key metrics. Install the New Relic Azure Application Insights monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Application Insights service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Application Insights installation docs.
+ description: |
+ Monitor Azure Application Insights by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-application-insights-monitoring-integration/
+keywords:
+ - azure
+ - application insight
+ - application insights
+ - product partnerships
+dashboards:
+ - azure-application-insights
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-application-insights/logo.png b/quickstarts/azure/azure-application-insights/logo.png
new file mode 100644
index 0000000000..6807838aa1
Binary files /dev/null and b/quickstarts/azure/azure-application-insights/logo.png differ
diff --git a/quickstarts/azure/azure-automation-account/config.yml b/quickstarts/azure/azure-automation-account/config.yml
new file mode 100644
index 0000000000..89daefe58d
--- /dev/null
+++ b/quickstarts/azure/azure-automation-account/config.yml
@@ -0,0 +1,40 @@
+id: b299cfaa-f5a4-4aea-9f0f-a7f3289b3d13
+slug: azure-automation-account
+title: Azure Automation Account
+description: |-
+ ## What is Azure Automation Account?
+
+ Azure Automation delivers cloud-based automation, operating system updates, and a configuration service that supports consistent management across your Azure and non-Azure environments.
+
+ ### New Relic Azure Automation Account quickstart features
+
+ A standard dashboard that tracks key indicators like hybrid worker ping, total jobs, total update deployment machine runs and total update deployment runs. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Automation Account with New Relic?
+
+ [New Relic Azure Automation Account](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Automation Account via different metrics including hybrid worker ping, total jobs, total update deployment machine runs and total update deployment runs.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Automation Account is critical to tracking the performance through key metrics. Install the New Relic Azure Automation Account monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Automation Account Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Automation Account installation docs
+ description: |
+ Monitor Azure Automation Account by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-automation-account-monitoring-integration/
+keywords:
+ - azure
+ - automation account
+ - product partnerships
+dashboards:
+ - azure-automation-account
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-automation-account/logo.png b/quickstarts/azure/azure-automation-account/logo.png
new file mode 100644
index 0000000000..782208efef
Binary files /dev/null and b/quickstarts/azure/azure-automation-account/logo.png differ
diff --git a/quickstarts/azure/azure-batch/config.yml b/quickstarts/azure/azure-batch/config.yml
new file mode 100644
index 0000000000..46eed3ffa3
--- /dev/null
+++ b/quickstarts/azure/azure-batch/config.yml
@@ -0,0 +1,40 @@
+id: e31643a4-a7a8-4fb9-b4fc-e8b15f93dabf
+slug: azure-batch
+description: |-
+ ## What is Azure Batch?
+
+ Azure Batch is a managed service that enables you to run high-performance parallel computing jobs in the cloud. You can run compute-intensive work in a collection of virtual machines.
+
+ ### New Relic Azure Batch quickstart features
+
+ A standard dashboard that tracks key indicators like vCPU minutes, node states, job status and task status. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Batch with New Relic?
+
+ [New Relic Azure Batch](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batch-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Batch via different metrics including vCPU minutes, node states, task states and job states.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Batch is critical to track the performance of the jobs via key metrics. Download New Relic Azure Batch monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Batch Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Batch
+documentation:
+ - name: Azure Batch installation docs
+ description: |
+ Monitor Azure Batch by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-batchaccount-monitoring-integration/
+keywords:
+ - azure
+ - batch
+ - product partnerships
+dashboards:
+ - azure-batch
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-batch/logo.png b/quickstarts/azure/azure-batch/logo.png
new file mode 100644
index 0000000000..7b21c6a40a
Binary files /dev/null and b/quickstarts/azure/azure-batch/logo.png differ
diff --git a/quickstarts/azure/azure-bing-autosuggest/config.yml b/quickstarts/azure/azure-bing-autosuggest/config.yml
new file mode 100644
index 0000000000..f48c7cd8d1
--- /dev/null
+++ b/quickstarts/azure/azure-bing-autosuggest/config.yml
@@ -0,0 +1,41 @@
+id: 6082a44b-888c-4524-b282-78c61fdf8432
+slug: azure-bing-autosuggest
+description: |-
+ ## What is Azure Bing Autosuggest?
+
+ The Bing Autosuggest enables developers to incorporate intelligent search suggestions into their applications. It leverages the power of Bing's search engine to provide real-time query suggestions as users type in a search box or interact with an application.
+
+ ### New Relic Azure Bing Autosuggest quickstart features
+
+ A standard dashboard that tracks key indicators like successful calls, data out, latency and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Bing Autosuggest with New Relic?
+
+ [New Relic Azure Bing Autosuggest](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Bing Autosuggest via different metrics including successful calls, data out, latency and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Bing Autosuggest is critical to track the performance through key metrics. Download New Relic Azure Bing Autosuggest monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Bing Autosuggest service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Bing Autosuggest
+documentation:
+ - name: Azure Bing Autosuggest installation docs
+ description: |
+ Monitor Azure Bing Autosuggest by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/
+keywords:
+ - azure
+ - bing search
+ - bing autosuggest
+ - product partnerships
+dashboards:
+ - azure-bing-autosuggest
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-bing-autosuggest/logo.png b/quickstarts/azure/azure-bing-autosuggest/logo.png
new file mode 100644
index 0000000000..233f3c0d0c
Binary files /dev/null and b/quickstarts/azure/azure-bing-autosuggest/logo.png differ
diff --git a/quickstarts/azure/azure-bing-custom-search/config.yml b/quickstarts/azure/azure-bing-custom-search/config.yml
new file mode 100644
index 0000000000..c3aafdc277
--- /dev/null
+++ b/quickstarts/azure/azure-bing-custom-search/config.yml
@@ -0,0 +1,41 @@
+id: b123f385-7c01-4a5e-af21-3746ee571cb3
+slug: azure-bing-custom-search
+description: |-
+ ## What is Azure Bing Custom Search?
+
+ Azure Bing Custom Search lets you create a tailored, ad-free search experiences for topics that your users care about. You specify the domains and webpages that Bing searches. You can also pin, boost, and demote specific content to create a custom view of the web that helps your users quickly find relevant content.
+
+ ### New Relic Azure Bing Custom Search quickstart features
+
+ A standard dashboard that tracks key indicators like successful calls, data out, latency and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Bing Custom Search with New Relic?
+
+ [New Relic Azure Bing Custom Search](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Bing Custom Search via different metrics including successful calls, data out, latency and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Bing Custom Search is critical to track the performance through key metrics. Download New Relic Azure Bing Custom Search monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Bing Custom Search service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Bing Custom Search
+documentation:
+ - name: Azure Bing Custom Search installation docs
+ description: |
+ Monitor Azure Custom Search by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/
+keywords:
+ - azure
+ - bing search
+ - bing custom search
+ - product partnerships
+dashboards:
+ - azure-bing-custom-search
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-bing-custom-search/logo.png b/quickstarts/azure/azure-bing-custom-search/logo.png
new file mode 100644
index 0000000000..05a1db3f42
Binary files /dev/null and b/quickstarts/azure/azure-bing-custom-search/logo.png differ
diff --git a/quickstarts/azure/azure-bing-search/config.yml b/quickstarts/azure/azure-bing-search/config.yml
new file mode 100644
index 0000000000..4c055c21a6
--- /dev/null
+++ b/quickstarts/azure/azure-bing-search/config.yml
@@ -0,0 +1,41 @@
+id: 86fff965-b8b5-41a0-874c-7bfb713c4e3f
+slug: azure-bing-search
+description: |-
+ ## What is Azure Bing Search?
+
+ The Bing Search let you build web-connected apps and services that find webpages, images, news, locations and more without advertisements.
+
+ ### New Relic Azure Bing Search quickstart features
+
+ A standard dashboard that tracks key indicators like successful calls, total calls by api, data in, data out, latency and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Bing Search with New Relic?
+
+ [New Relic Azure Bing Search](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Bing Search via different metrics including successful calls, total calls by api, data in, data out, latency and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Bing Search is critical to track the performance through key metrics. Download New Relic Azure Bing Search monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Bing Search service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Bing Search
+documentation:
+ - name: Azure Bing Search installation docs
+ description: |
+ Monitor Azure Bing Search by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/
+keywords:
+ - azure
+ - bing
+ - bing search
+ - product partnerships
+dashboards:
+ - azure-bing-search
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-bing-search/logo.png b/quickstarts/azure/azure-bing-search/logo.png
new file mode 100644
index 0000000000..6b04ff80eb
Binary files /dev/null and b/quickstarts/azure/azure-bing-search/logo.png differ
diff --git a/quickstarts/azure/azure-bing-spell-check/config.yml b/quickstarts/azure/azure-bing-spell-check/config.yml
new file mode 100644
index 0000000000..15e108438f
--- /dev/null
+++ b/quickstarts/azure/azure-bing-spell-check/config.yml
@@ -0,0 +1,41 @@
+id: 1f8eedad-bdf6-44d1-b776-c10a4de9d071
+slug: azure-bing-spell-check
+description: |-
+ ## What is Azure Bing Spell Check?
+
+ The Bing Spell Check enables you to perform contextual grammar and spell checking on text. While most spell-checkers rely on dictionary-based rule sets, the Bing spell-checker leverages machine learning and statistical machine translation to provide accurate and contextual corrections.
+
+ ### New Relic Azure Bing Spell Check quickstart features
+
+ A standard dashboard that tracks key indicators like successful calls, data out, latency and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Bing Spell Check with New Relic?
+
+ [New Relic Azure Bing Spell Check](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Bing Spell Check via different metrics including successful calls, data out, latency and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Bing Spell Check is critical to track the performance through key metrics. Download New Relic Azure Bing Spell Check monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Bing Spell Check service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Bing Spell Check
+documentation:
+ - name: Azure Bing Spell Check installation docs
+ description: |
+ Monitor Azure Bing Spell Check by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/
+keywords:
+ - azure
+ - bing search
+ - bing spell check
+ - product partnerships
+dashboards:
+ - azure-bing-spell-check
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-bing-spell-check/logo.png b/quickstarts/azure/azure-bing-spell-check/logo.png
new file mode 100644
index 0000000000..2bab537ce6
Binary files /dev/null and b/quickstarts/azure/azure-bing-spell-check/logo.png differ
diff --git a/quickstarts/azure/azure-bing-web-search/config.yml b/quickstarts/azure/azure-bing-web-search/config.yml
new file mode 100644
index 0000000000..2469695887
--- /dev/null
+++ b/quickstarts/azure/azure-bing-web-search/config.yml
@@ -0,0 +1,41 @@
+id: 1c1b42bf-6e69-4467-8375-8ed91dac960f
+slug: azure-bing-web-search
+description: |-
+ ## What is Azure Bing Web Search?
+
+ Azure Bing Web Search enables safe, ad-free, location-aware search results, surfacing relevant information from billions of web documents. Help your users find what they're looking for from the world-wide-web by harnessing Bing's ability to comb billions of webpages, images, videos, and news with a single API call.
+
+ ### New Relic Azure Bing Web Search quickstart features
+
+ A standard dashboard that tracks key indicators like successful calls, data out, latency and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Bing Web Search with New Relic?
+
+ [New Relic Azure Bing Web Search](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Bing Web Search via different metrics including successful calls, data out, latency and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Bing Web Search is critical to track the performance through key metrics. Download New Relic Azure Bing Web Search monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Bing Web Search service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Bing Web Search
+documentation:
+ - name: Azure Bing Web Search installation docs
+ description: |
+ Monitor Azure Bing Web Search by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-bing-search-monitoring-integration/
+keywords:
+ - azure
+ - bing search
+ - bing web search
+ - product partnerships
+dashboards:
+ - azure-bing-web-search
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-bing-web-search/logo.png b/quickstarts/azure/azure-bing-web-search/logo.png
new file mode 100644
index 0000000000..d547e37dc7
Binary files /dev/null and b/quickstarts/azure/azure-bing-web-search/logo.png differ
diff --git a/quickstarts/azure/azure-cdn-profile/config.yml b/quickstarts/azure/azure-cdn-profile/config.yml
new file mode 100644
index 0000000000..33a7ced2be
--- /dev/null
+++ b/quickstarts/azure/azure-cdn-profile/config.yml
@@ -0,0 +1,41 @@
+id: 1eddac86-3ee3-42b9-aae3-ceebb4b42401
+slug: azure-cdn-profile
+title: Azure CDN profile
+description: |-
+ ## What is Azure CDN profile?
+
+ Azure Content Delivery Network is a globally distributed network of servers that can efficiently deliver web content to consumers. A CDN minimizes latency by storing cached content on edge servers in point-of-presence (POP) locations that are close to end users.
+
+ ### New Relic Azure CDN profile quickstart features
+
+ A standard dashboard that tracks key indicators like total latency, request count, byte hit ratio and response size. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure CDN profile with New Relic?
+
+ [New Relic Azure CDN profile](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure CDN profile via different metrics including total latency, request count, byte hit ratio and response size.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure CDN profile is critical to tracking the performance of the content via key metrics. Install the New Relic Azure CDN profile monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure CDN profile service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure CDN profile installation docs
+ description: |
+ Monitor Azure CDN profile by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cdn-profile-monitoring-integration/
+keywords:
+ - azure
+ - cdn profile
+ - cdn profiles
+dashboards:
+ - azure-cdn-profile
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-cdn-profile/logo.png b/quickstarts/azure/azure-cdn-profile/logo.png
new file mode 100644
index 0000000000..184f0151c8
Binary files /dev/null and b/quickstarts/azure/azure-cdn-profile/logo.png differ
diff --git a/quickstarts/azure/azure-cloud-services/config.yml b/quickstarts/azure/azure-cloud-services/config.yml
new file mode 100644
index 0000000000..f9038a5aa9
--- /dev/null
+++ b/quickstarts/azure/azure-cloud-services/config.yml
@@ -0,0 +1,41 @@
+id: 9c966ae6-12e8-4147-9350-5b95efae8e30
+slug: azure-cloud-services
+title: Azure Cloud Services
+description: |-
+ ## What is Azure Cloud Services?
+
+ Azure Cloud Services is an example of a platform as a service (PaaS). Like Azure App Service, this technology is designed to support applications that are scalable, reliable and inexpensive to operate.
+
+ ### New Relic Azure Cloud Services quickstart features
+
+ A standard dashboard that tracks key indicators like available memory bytes, disk read bytes, disk write bytes and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Cloud Services with New Relic?
+
+ [New Relic Azure Cloud Services](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Cloud Services via different metrics including available memory bytes, disk read bytes, disk write bytes and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Cloud Services is critical to tracking the performance through key metrics. Install the New Relic Azure Cloud Services monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Cloud Services.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Cloud Services installation docs
+ description: |
+ Monitor Azure Cloud Services by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cloud-services-monitoring-integration/
+keywords:
+ - azure
+ - cloud service
+ - cloud services
+ - product partnerships
+dashboards:
+ - azure-cloud-services
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-cloud-services/logo.png b/quickstarts/azure/azure-cloud-services/logo.png
new file mode 100644
index 0000000000..f9bffabbda
Binary files /dev/null and b/quickstarts/azure/azure-cloud-services/logo.png differ
diff --git a/quickstarts/azure/azure-cognitive-search/config.yml b/quickstarts/azure/azure-cognitive-search/config.yml
new file mode 100644
index 0000000000..5ae1324ade
--- /dev/null
+++ b/quickstarts/azure/azure-cognitive-search/config.yml
@@ -0,0 +1,41 @@
+id: 535361fa-6fe6-4283-a0fc-d7522bcb3d06
+slug: azure-cognitive-search
+title: Azure Cognitive Search
+description: |-
+ ## What is Azure Cognitive Search?
+
+ Azure Cognitive Search (formerly known as "Azure Search") is a cloud search service that gives developers infrastructure, APIs, and tools for building a rich search experience over private, heterogeneous content in web, mobile, and enterprise applications.
+
+ ### New Relic Azure Cognitive Search quickstart features
+
+ A standard dashboard that tracks key indicators like search latency, search queries per second, documents processed count, skill execution count and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Cognitive Search with New Relic?
+
+ [New Relic Azure Cognitive Search](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Cognitive Search via different metrics including search latency, search queries per second, documents processed count, skill execution count and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Cognitive Search is critical to tracking the performance through key metrics. Install the New Relic Azure Cognitive Search monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Cognitive Search service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Cognitive Search installation docs
+ description: |
+ Monitor Azure Cognitive Search by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-search-monitoring-integration/
+keywords:
+ - azure
+ - search
+ - cognitive search
+ - product partnerships
+dashboards:
+ - azure-cognitive-search
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-cognitive-search/logo.png b/quickstarts/azure/azure-cognitive-search/logo.png
new file mode 100644
index 0000000000..599f375baf
Binary files /dev/null and b/quickstarts/azure/azure-cognitive-search/logo.png differ
diff --git a/quickstarts/azure/azure-cognitive-service/config.yml b/quickstarts/azure/azure-cognitive-service/config.yml
new file mode 100644
index 0000000000..b1666d72d1
--- /dev/null
+++ b/quickstarts/azure/azure-cognitive-service/config.yml
@@ -0,0 +1,41 @@
+id: 96f44c71-4827-4e69-b56a-efb9195f35b3
+slug: azure-cognitive-service
+description: |-
+ ## What is Azure Cognitive Services?
+
+ Azure Cognitive Services are cloud-based artificial intelligence (AI) services that help developers build cognitive intelligence into applications without having direct AI or data science skills or knowledge.
+
+ ### New Relic Azure Cognitive Services quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, successful calls, success rate, latency, ratelimit and total errors. It indicates total calls by api and operations, ratelimit by ratelimitkey and total data by operations. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Cognitive Services with New Relic?
+
+ [New Relic Azure Cognitive Services](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Cognitive Services via different metrics including total calls, successful calls, success rate, latency, ratelimit and total errors. It indicates total calls by api and operations, ratelimit by ratelimitkey and total data by operations.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Cognitive Services is critical to track the performance through key metrics. Download New Relic Azure Cognitive Services monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Cognitive Services.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Cognitive Service
+documentation:
+ - name: Azure Cognitive Service installation docs.
+ description: |
+ Monitor Azure Cognitive Services by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive service
+ - cognitive services
+ - product partnerships
+dashboards:
+ - azure-cognitive-service
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-cognitive-service/logo.png b/quickstarts/azure/azure-cognitive-service/logo.png
new file mode 100644
index 0000000000..baf43911f2
Binary files /dev/null and b/quickstarts/azure/azure-cognitive-service/logo.png differ
diff --git a/quickstarts/azure/azure-computer-vision/config.yml b/quickstarts/azure/azure-computer-vision/config.yml
new file mode 100644
index 0000000000..9cc7f3c3e8
--- /dev/null
+++ b/quickstarts/azure/azure-computer-vision/config.yml
@@ -0,0 +1,41 @@
+id: 5583457b-8689-4a7c-892e-8c565312216a
+slug: azure-computer-vision
+description: |-
+ ## What is Azure Computer Vision?
+
+ Azure Computer vision applications use input from sensing devices, artificial intelligence, machine learning and deep learning to replicate the way the human vision system works. Computer vision applications run on algorithms that are trained on massive amounts of visual data or images in the cloud.
+
+ ### New Relic Azure Computer Vision quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, total data, computer vision transactions and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Computer Vision with New Relic?
+
+ [New Relic Azure Computer Vision](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Computer Vision via different metrics including total calls, total data, computer vision transactions and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Computer Vision is critical to track the performance through key metrics. Download New Relic Azure Computer Vision monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Computer Vision.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Computer Vision
+documentation:
+ - name: Azure Computer Vision installation docs.
+ description: |
+ Monitor Azure Computer Vision by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - computer vision
+ - product partnerships
+dashboards:
+ - azure-computer-vision
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-computer-vision/logo.png b/quickstarts/azure/azure-computer-vision/logo.png
new file mode 100644
index 0000000000..bd59b3799a
Binary files /dev/null and b/quickstarts/azure/azure-computer-vision/logo.png differ
diff --git a/quickstarts/azure/azure-container-registry/config.yml b/quickstarts/azure/azure-container-registry/config.yml
new file mode 100644
index 0000000000..1510264684
--- /dev/null
+++ b/quickstarts/azure/azure-container-registry/config.yml
@@ -0,0 +1,40 @@
+id: f0d9ae29-607c-40e1-b471-043cd56c8ec0
+slug: azure-container-registry
+description: |-
+ ## What is Azure Container Registry?
+
+ Azure Container Registry is a private registry service for building, storing and managing container images and related artifacts.
+
+ ### New Relic Azure Container Registry quickstart features
+
+ A standard dashboard that tracks key indicators like agent pool CPU time, run duration, storage used, successful pull count, successful push count, total pull count and total push count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Container Registry with New Relic?
+
+ [New Relic Azure Container Registry](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Container Registry via different metrics including agent pool CPU time, run duration, storage used, successful pull count, successful push count, total pull count and total push count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Container Registry is critical to track the performance through key metrics. Download New Relic Azure Container Registry monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Container Registry service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Container Registry
+documentation:
+ - name: Azure Container Registry installation docs
+ description: |
+ Monitor Azure Container Registry by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-containers-monitoring-integration/
+keywords:
+ - azure
+ - container registry
+ - product partnerships
+dashboards:
+ - azure-container-registry
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-container-registry/logo.png b/quickstarts/azure/azure-container-registry/logo.png
new file mode 100644
index 0000000000..b7c0ff4adc
Binary files /dev/null and b/quickstarts/azure/azure-container-registry/logo.png differ
diff --git a/quickstarts/azure/azure-content-moderator/config.yml b/quickstarts/azure/azure-content-moderator/config.yml
new file mode 100644
index 0000000000..5a5cab8c4b
--- /dev/null
+++ b/quickstarts/azure/azure-content-moderator/config.yml
@@ -0,0 +1,41 @@
+id: 64bb7af0-b5d3-4cfd-8a9a-fe98af2f3aff
+slug: azure-content-moderator
+description: |-
+ ## What is Azure Content Moderator?
+
+ Azure Content Moderator is an AI service that lets you handle content that is potentially offensive, risky, or otherwise undesirable. It includes the AI-powered content moderation service which scans text, image, and videos and applies content flags automatically.
+
+ ### New Relic Azure Content Moderator quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, total data in, success rate and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Content Moderator with New Relic?
+
+ [New Relic Azure Content Moderator](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Content Moderator via different metrics including total calls, total data in, success rate and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Content Moderator is critical to track the performance through key metrics. Download New Relic Azure Content Moderator monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Content Moderator.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Content Moderator
+documentation:
+ - name: Azure Content Moderator installation docs.
+ description: |
+ Monitor Azure Content Moderator by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - content moderator
+ - product partnerships
+dashboards:
+ - azure-content-moderator
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-content-moderator/logo.png b/quickstarts/azure/azure-content-moderator/logo.png
new file mode 100644
index 0000000000..a625e78dcc
Binary files /dev/null and b/quickstarts/azure/azure-content-moderator/logo.png differ
diff --git a/quickstarts/azure/azure-content-safety/config.yml b/quickstarts/azure/azure-content-safety/config.yml
new file mode 100644
index 0000000000..96148f94dd
--- /dev/null
+++ b/quickstarts/azure/azure-content-safety/config.yml
@@ -0,0 +1,41 @@
+id: 5037b361-edec-4516-9b25-2e9ea5ab0bf1
+slug: azure-content-safety
+description: |-
+ ## What is Azure Content Safety?
+
+ Azure AI Content Safety detects harmful user-generated and AI-generated content in applications and services. Content Safety includes text and image APIs that allow you to detect material that is harmful.
+
+ ### New Relic Azure Content Safety quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, data in, success rate, total call count for text moderation and total call count for image moderation. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Content Safety with New Relic?
+
+ [New Relic Azure Content Safety](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Content Safety via different metrics including total calls, data in, success rate, total errors, total call count for text moderation and total call count for image moderation.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Content Safety is critical to track the performance through key metrics. Download New Relic Azure Content Safety monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Content Safety.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Content Safety
+documentation:
+ - name: Azure Content Safety installation docs.
+ description: |
+ Monitor Azure Content Safety by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - content safety
+ - product partnerships
+dashboards:
+ - azure-content-safety
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-content-safety/logo.png b/quickstarts/azure/azure-content-safety/logo.png
new file mode 100644
index 0000000000..ba68d40360
Binary files /dev/null and b/quickstarts/azure/azure-content-safety/logo.png differ
diff --git a/quickstarts/azure/azure-custom-vision-prediction/config.yml b/quickstarts/azure/azure-custom-vision-prediction/config.yml
new file mode 100644
index 0000000000..06e89f56ad
--- /dev/null
+++ b/quickstarts/azure/azure-custom-vision-prediction/config.yml
@@ -0,0 +1,41 @@
+id: fd3f5479-1c35-458c-8b48-ae6fc27e37d5
+slug: azure-custom-vision-prediction
+description: |-
+ ## What is Azure Custom Vision Prediction?
+
+ Azure Custom Vision Prediction is a service offered by Microsoft Azure that allows developers to build and deploy custom image classification and object detection models. It leverages deep learning algorithms to recognize and classify images according to user-defined categories.
+
+ ### New Relic Azure Custom Vision Prediction quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, success rate ,data in, data out and custom vision transactions. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Custom Vision Prediction with New Relic?
+
+ [New Relic Azure Custom Vision Prediction](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Custom Vision Prediction via different metrics including total calls, success rate, data in, data out and custom vision transactions.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Custom Vision Prediction is critical to track the performance through key metrics. Download New Relic Azure Custom Vision Prediction monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Custom Vision Prediction.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Custom Vision Prediction
+documentation:
+ - name: Azure Custom Vision Prediction installation docs.
+ description: |
+ Monitor Azure Custom Vision Prediction by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - custom vision prediction
+ - product partnerships
+dashboards:
+ - azure-custom-vision-prediction
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-custom-vision-prediction/logo.png b/quickstarts/azure/azure-custom-vision-prediction/logo.png
new file mode 100644
index 0000000000..86d1a8bc56
Binary files /dev/null and b/quickstarts/azure/azure-custom-vision-prediction/logo.png differ
diff --git a/quickstarts/azure/azure-custom-vision-training/config.yml b/quickstarts/azure/azure-custom-vision-training/config.yml
new file mode 100644
index 0000000000..fe418b3f51
--- /dev/null
+++ b/quickstarts/azure/azure-custom-vision-training/config.yml
@@ -0,0 +1,41 @@
+id: 03ae9fcb-3de1-40e4-92f0-1b6415fb3f03
+slug: azure-custom-vision-training
+description: |-
+ ## What is Azure Custom Vision Training?
+
+ Azure Custom Vision Training is an image recognition service that lets you build, deploy, and improve your own image identifier models. An image identifier applies labels to images, according to their visual characteristics.
+
+ ### New Relic Azure Custom Vision Training quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, success rate, images stored and custom vision training time. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Custom Vision Training with New Relic?
+
+ [New Relic Azure Custom Vision Training](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Custom Vision Training via different metrics including total calls, success rate, images stored and custom vision training time.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Custom Vision Training is critical to track the performance through key metrics. Download New Relic Azure Custom Vision Training monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Custom Vision Training.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Custom Vision Training
+documentation:
+ - name: Azure Custom Vision Training installation docs.
+ description: |
+ Monitor Azure Custom Vision Training by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - custom vision training
+ - product partnerships
+dashboards:
+ - azure-custom-vision-training
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-custom-vision-training/logo.png b/quickstarts/azure/azure-custom-vision-training/logo.png
new file mode 100644
index 0000000000..86d1a8bc56
Binary files /dev/null and b/quickstarts/azure/azure-custom-vision-training/logo.png differ
diff --git a/quickstarts/azure/azure-data-box-edge/config.yml b/quickstarts/azure/azure-data-box-edge/config.yml
new file mode 100644
index 0000000000..9285e7df12
--- /dev/null
+++ b/quickstarts/azure/azure-data-box-edge/config.yml
@@ -0,0 +1,40 @@
+id: c852cbc9-bb73-4e6c-ac36-07e7b35c266d
+slug: azure-data-box-edge
+title: Azure Data Box Edge
+description: |-
+ ## What is Azure Data Box Edge?
+
+ Azure Data Box Edge is a physical network appliance, shipped by Microsoft, that sends data in and out of Azure. Data Box Edge is additionally equipped with AI-enabled edge computing capabilities that help you analyze, process and transform the on-premises data before uploading it to the cloud.
+
+ ### New Relic Azure Data Box Edge quickstart features
+
+ A standard dashboard that tracks key indicators like total capacity, bytes uploaded to cloud, cloud read throughput, hyperV memory utilization and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Data Box Edge with New Relic?
+
+ [New Relic Azure Data Box Edge](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Data Box Edge via different metrics including total capacity, bytes uploaded to cloud, cloud read throughput, hyperV memory utilization and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Data Box Edge is critical to tracking the performance through key metrics. Install the New Relic Azure Data Box Edge monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Data Box Edge service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Data Box Edge installation docs
+ description: |
+ Monitor Azure Data Box Edge by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-box-edge-monitoring-integration/
+keywords:
+ - azure
+ - data box edge
+ - product partnerships
+dashboards:
+ - azure-data-box-edge
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-data-box-edge/logo.png b/quickstarts/azure/azure-data-box-edge/logo.png
new file mode 100644
index 0000000000..3bb3d57c07
Binary files /dev/null and b/quickstarts/azure/azure-data-box-edge/logo.png differ
diff --git a/quickstarts/azure/azure-data-explorer/config.yml b/quickstarts/azure/azure-data-explorer/config.yml
new file mode 100644
index 0000000000..6e67737c27
--- /dev/null
+++ b/quickstarts/azure/azure-data-explorer/config.yml
@@ -0,0 +1,40 @@
+id: 3953ee6f-6e6c-42f8-8d17-bcda79c08d15
+slug: azure-data-explorer
+title: Azure Data Explorer
+description: |-
+ ## What is Azure Data Explorer?
+
+ Azure Data Explorer is a fast, fully managed data analytics service for real-time analysis on large volumes of data streaming from applications, websites, IoT devices and more.
+
+ ### New Relic Azure Data Explorer quickstart features
+
+ A standard dashboard that tracks key indicators like CPU utilization level, ingestion latency, ingestion result and query duration. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Data Explorer with New Relic?
+
+ [New Relic Azure Data Explorer](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Data Explorer via different metrics including CPU utilization level, ingestion latency, ingestion result and query duration.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Data Explorer toolbox gives you an end-to-end solution for data ingestion, query, visualization and management. Install the New Relic Azure Data Explorer monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Data Explorer service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Data Explorer installation docs
+ description: |
+ Monitor Azure Data Explorer by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-explorer-monitoring-integration/
+keywords:
+ - azure
+ - data explorer
+ - product partnerships
+dashboards:
+ - azure-data-explorer
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-data-explorer/logo.png b/quickstarts/azure/azure-data-explorer/logo.png
new file mode 100644
index 0000000000..18ccf33a5e
Binary files /dev/null and b/quickstarts/azure/azure-data-explorer/logo.png differ
diff --git a/quickstarts/azure/azure-data-lake-analytics/config.yml b/quickstarts/azure/azure-data-lake-analytics/config.yml
new file mode 100644
index 0000000000..ca17131d6f
--- /dev/null
+++ b/quickstarts/azure/azure-data-lake-analytics/config.yml
@@ -0,0 +1,40 @@
+id: 4ed0aedb-2f24-4189-b28f-8d498d89edbf
+slug: azure-data-lake-analytics
+title: Azure Data Lake Analytics
+description: |-
+ ## What is Azure Data Lake Analytics?
+
+ Azure Data Lake Analytics is an on-demand analytics job service that simplifies big data. Instead of deploying, configuring, and tuning hardware, you write queries to transform your data and extract valuable insights. The analytics service can handle jobs of any scale instantly by setting the dial for how much power you need. You only pay for your job when it's running, making it cost-effective.
+
+ ### New Relic Azure Data Lake Analytics quickstart features
+
+ A standard dashboard that tracks key indicators like number of jobs stage, AU time for jobs ended in success, failure and cancelled. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Data Lake Analytics with New Relic?
+
+ [New Relic Azure Data Lake Analytics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Data Lake Analytics via different metrics including A standard dashboard that tracks key indicators like number of jobs stage, AU time for jobs ended in success, failure and cancelled.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Data Lake Analytics is critical to tracking the performance through key metrics. Install the New Relic Azure Data Lake Analytics Service monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Data Lake Analytics service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Data Lake Analytics installation docs
+ description: |
+ Monitor Azure Data Lake Analytics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-analytic-monitoring-integration/
+keywords:
+ - azure
+ - data lake analytics
+ - product partnerships
+dashboards:
+ - azure-data-lake-analytics
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-data-lake-analytics/logo.png b/quickstarts/azure/azure-data-lake-analytics/logo.png
new file mode 100644
index 0000000000..092738e70b
Binary files /dev/null and b/quickstarts/azure/azure-data-lake-analytics/logo.png differ
diff --git a/quickstarts/azure/azure-data-lake-storage/config.yml b/quickstarts/azure/azure-data-lake-storage/config.yml
new file mode 100644
index 0000000000..95f9bf3fe9
--- /dev/null
+++ b/quickstarts/azure/azure-data-lake-storage/config.yml
@@ -0,0 +1,40 @@
+id: 1e1c1ed6-12b5-46a0-89f0-7231edd0aed5
+slug: azure-data-lake-storage
+title: Azure Data Lake Storage
+description: |-
+ ## What is Azure Data Lake Storage?
+
+ Azure Data Lake enables you to capture data of any size, type, and ingestion speed in one single place for operational and exploratory analytics.
+
+ ### New Relic Azure Data Lake Storage quickstart features
+
+ A standard dashboard that tracks key indicators like data read, data written, read requests, total storage and written requests. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Data Lake Storage with New Relic?
+
+ [New Relic Azure Data Lake Storage](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Data Lake Storage via different metrics including data read, data written, read requests, total storage and written requests.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Data Lake Storage is critical to tracking the performance through key metrics. Install the New Relic Azure Data Lake Storage monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Data Lake Storage service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Data Lake Storage installation docs
+ description: |
+ Monitor Azure Data Lake Storage by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-lake-storage-monitoring-integration/
+keywords:
+ - azure
+ - data lake storage
+ - product partnerships
+dashboards:
+ - azure-data-lake-storage
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-data-lake-storage/logo.png b/quickstarts/azure/azure-data-lake-storage/logo.png
new file mode 100644
index 0000000000..d8b0f5798d
Binary files /dev/null and b/quickstarts/azure/azure-data-lake-storage/logo.png differ
diff --git a/quickstarts/azure/azure-data-share/config.yml b/quickstarts/azure/azure-data-share/config.yml
new file mode 100644
index 0000000000..81693691cd
--- /dev/null
+++ b/quickstarts/azure/azure-data-share/config.yml
@@ -0,0 +1,41 @@
+id: f965234e-4904-463b-935b-ff95da841abc
+slug: azure-data-share
+title: Azure Data Share
+description: |-
+ ## What is Azure Data Share?
+
+ Azure Data Share enables organizations to securely share data with multiple customers and partners. Data providers are always in control of the data that they've shared and Azure Data Share makes it simple to manage and monitor what data was shared, when and by whom.
+
+ ### New Relic Azure Data Share quickstart features
+
+ A standard dashboard that tracks key indicators like share count, failed share subscription synchronizations, share subscription count and succeeded share synchronizations.It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Data Share with New Relic?
+
+ [New Relic Azure Data Share](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Data Share via different metrics including share count, failed share subscription synchronizations, share subscription count and succeeded share synchronizations.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Using Data Share a data provider can share data and manage their shares all in one place. They can stay in control of how their data is handled by specifying terms of use for their data share. Azure Data Share helps enhance insights by making it easy to combine data from third parties to enrich analytics and AI scenarios.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Data Share installation docs
+ description: |
+ Monitor Azure Data Share by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-share-monitoring-integration/
+keywords:
+ - azure
+ - data share
+ - product partnerships
+dashboards:
+ - azure-data-share
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-data-share/logo.png b/quickstarts/azure/azure-data-share/logo.png
new file mode 100644
index 0000000000..8d80d69fc8
Binary files /dev/null and b/quickstarts/azure/azure-data-share/logo.png differ
diff --git a/quickstarts/azure/azure-datafactories/config.yml b/quickstarts/azure/azure-datafactories/config.yml
index e353f946b6..f2c2d8a99b 100644
--- a/quickstarts/azure/azure-datafactories/config.yml
+++ b/quickstarts/azure/azure-datafactories/config.yml
@@ -21,6 +21,7 @@ icon: logo.svg
level: New Relic
authors:
- New Relic
+ - Dave Miyamasu
title: Azure DataFactories
documentation:
- name: Azure DataFactories installation docs
@@ -29,6 +30,11 @@ documentation:
url: https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-data-factory-integration/
keywords:
- azure
+ - etl
+ - data factory
+ - pipeline
+dashboards:
+ - azure-datafactories
installPlans:
- azure-infrastructure-monitoring
dataSourceIds:
diff --git a/quickstarts/azure/azure-device-provisioning-service/config.yml b/quickstarts/azure/azure-device-provisioning-service/config.yml
new file mode 100644
index 0000000000..c3a3fb4c37
--- /dev/null
+++ b/quickstarts/azure/azure-device-provisioning-service/config.yml
@@ -0,0 +1,40 @@
+id: 10ecef52-8600-42f4-9587-ac8f5054a015
+slug: azure-device-provisioning-service
+title: Azure Device Provisioning Service
+description: |-
+ ## What is Azure Device Provisioning Service?
+
+ The IoT Hub Device Provisioning Service (DPS) is a helper service for IoT Hub that enables zero-touch, just-in-time provisioning to the right IoT hub without requiring human intervention, allowing customers to provision millions of devices in a secure and scalable manner.
+
+ ### New Relic Azure Device Provisioning Service quickstart features
+
+ A standard dashboard that tracks key indicators like attestation attempts, device assignments and registration attempts. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Device Provisioning Service with New Relic?
+
+ [New Relic Azure Device Provisioning Service](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration/) monitoring quickstart empowers you to track the performance of Azure Device Provisioning Service via different metrics including account attestation attempts, device assignments and registration attempts.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Device Provisioning Service is critical to tracking the performance through key metrics. Install the New Relic Azure Device Provisioning Service monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Device Provisioning Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Device Provisioning Service installation docs
+ description: |
+ Monitor Azure Device Provisioning Service by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-device-provisioning-service-integration/
+keywords:
+ - azure
+ - device provisioning service
+ - product partnerships
+dashboards:
+ - azure-device-provisioning-service
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-device-provisioning-service/logo.png b/quickstarts/azure/azure-device-provisioning-service/logo.png
new file mode 100644
index 0000000000..957a0862b2
Binary files /dev/null and b/quickstarts/azure/azure-device-provisioning-service/logo.png differ
diff --git a/quickstarts/azure/azure-disk-storage/config.yml b/quickstarts/azure/azure-disk-storage/config.yml
new file mode 100644
index 0000000000..9d6b7a4794
--- /dev/null
+++ b/quickstarts/azure/azure-disk-storage/config.yml
@@ -0,0 +1,40 @@
+id: 8a6fd1c3-6022-4533-8c5e-f5f6753372bb
+slug: azure-disk-storage
+description: |-
+ ## What is Azure Disk Storage?
+
+ Azure managed disks are block-level storage volumes that are managed by Azure and used with Azure Virtual Machines.
+
+ ### New Relic Azure Disk Storage quickstart features
+
+ A standard dashboard that tracks key indicators like disk read bytes, disk read operations, disk write bytes, disk write operations and disk on-demand burst operations. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Disk Storage with New Relic?
+
+ [New Relic Azure Disk Storage](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Disk Storage via different metrics including disk read bytes, disk read operations, disk write bytes, disk write operations and disk on-demand burst operations.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Disk Storage is critical to track the performance through key metrics. Download New Relic Azure Disk Storage monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Disk Storage.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Disk Storage
+documentation:
+ - name: Azure Disk Storage installation docs
+ description: |
+ Monitor Azure Disk Storage by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-disk-storage-monitoring-integration/
+keywords:
+ - azure
+ - disk storage
+ - product partnerships
+dashboards:
+ - azure-disk-storage
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-disk-storage/logo.png b/quickstarts/azure/azure-disk-storage/logo.png
new file mode 100644
index 0000000000..9569816f7b
Binary files /dev/null and b/quickstarts/azure/azure-disk-storage/logo.png differ
diff --git a/quickstarts/azure/azure-dns-zones/config.yml b/quickstarts/azure/azure-dns-zones/config.yml
new file mode 100644
index 0000000000..ce9de9abcf
--- /dev/null
+++ b/quickstarts/azure/azure-dns-zones/config.yml
@@ -0,0 +1,40 @@
+id: 98803980-ab2e-4018-8103-ff9a9847dfa8
+slug: azure-dns-zones
+description: |-
+ ## What is Azure DNS zones?
+
+ Azure DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools and billing as your other Azure services.
+
+ ### New Relic Azure DNS Zones quickstart features
+
+ A standard dashboard that tracks key indicators like query volume, record set capacity utilization and record set count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure DNS Zones with New Relic?
+
+ [New Relic Azure DNS Zones](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure DNS Zones via different metrics including query volume, record set capacity utilization and record set count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure DNS Zones is critical to track the performance through key metrics. Download New Relic Azure Dns Zones monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure DNS Zones Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure DNS Zones
+documentation:
+ - name: Azure DNS Zones installation docs
+ description: |
+ Monitor Azure DNS Zones by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-dns-zones-monitoring-integration/
+keywords:
+ - azure
+ - dns zones
+ - product partnerships
+dashboards:
+ - azure-dns-zones
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-dns-zones/logo.png b/quickstarts/azure/azure-dns-zones/logo.png
new file mode 100644
index 0000000000..7182ce07a7
Binary files /dev/null and b/quickstarts/azure/azure-dns-zones/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-domains/config.yml b/quickstarts/azure/azure-event-grid-domains/config.yml
new file mode 100644
index 0000000000..ca53accdb6
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-domains/config.yml
@@ -0,0 +1,40 @@
+id: b7ada61a-95c7-48af-8260-27734c0d72af
+slug: azure-event-grid-domains
+description: |-
+ ## What is Azure Event Grid Domains?
+
+ Event Grid Domains within the Event Grid service is a management capability to manage a large number of events.
+
+ ### New Relic Azure Event Grid Domains quickstart features
+
+ A standard dashboard that tracks key indicators like dead lettered count, delivered events, dropped events and matched events. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Event Grid Domains with New Relic?
+
+ [New Relic Azure Event Grid domains](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Event Grid Domains via different metrics including dead lettered count, delivered events, dropped events and matched events.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid Domains is critical to track the performance through key metrics. Download New Relic Azure Event Grid Domains monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid Domains Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid Domains
+documentation:
+ - name: Azure Event Grid Domains installation docs
+ description: |
+ Monitor Azure Event Grid Domains by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-domains-monitoring-integration/
+keywords:
+ - azure
+ - event grid domains
+ - product partnerships
+dashboards:
+ - azure-event-grid-domains
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-domains/logo.png b/quickstarts/azure/azure-event-grid-domains/logo.png
new file mode 100644
index 0000000000..895ceca5ff
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-domains/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-partner-namespaces/config.yml b/quickstarts/azure/azure-event-grid-partner-namespaces/config.yml
new file mode 100644
index 0000000000..f7dd0f7fc6
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-partner-namespaces/config.yml
@@ -0,0 +1,41 @@
+id: 3f899a50-6bb4-4a2a-9238-f1865636172a
+slug: azure-event-grid-partner-namespaces
+description: |-
+ ## What is Azure Event Grid Partner Namespaces?
+
+ A partner namespace is a regional resource that has an endpoint to publish events to Azure Event Grid. Partner namespaces contain either channels or event channels (legacy resource).
+
+ ### New Relic Azure Event Grid Partner Namespaces quickstart features
+
+ A standard dashboard that tracks key indicators like publish fail count, publish success count, publish success latency and unmatched event count. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Event Grid Partner Namespaces with New Relic?
+
+ [New Relic Azure Event Grid Partner Namespaces](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Event Grid Partner Namespaces via different metrics including publish fail count, publish success count, publish success latency and unmatched event count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid Partner Namespaces is critical to track the performance through key metrics. Download New Relic Azure Event Grid Partner Namespaces monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid Partner Namespaces.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid Partner Namespaces
+documentation:
+ - name: Azure Event Grid Partner Namespaces installation docs
+ description: |
+ Monitor Azure Event Grid Partner Namespaces by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-namespaces-monitoring-integration/
+keywords:
+ - azure
+ - event grid
+ - product partnerships
+dashboards:
+ - azure-event-grid-partner-namespaces
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-partner-namespaces/logo.png b/quickstarts/azure/azure-event-grid-partner-namespaces/logo.png
new file mode 100644
index 0000000000..1a0aa000de
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-partner-namespaces/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-partner-topics/config.yml b/quickstarts/azure/azure-event-grid-partner-topics/config.yml
new file mode 100644
index 0000000000..b7c96d3148
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-partner-topics/config.yml
@@ -0,0 +1,40 @@
+id: de0c7325-e684-4e6e-8156-c02651f64104
+slug: azure-event-grid-partner-topics
+description: |-
+ ## What is Azure Event Grid Partner Topics?
+
+ Event Grid's Partner Events allows customers to subscribe to events that originate in a registered system using the same mechanism they would use for any other event source on Azure, such as an Azure service.
+
+ ### New Relic Azure Event Grid Partner Topics quickstart features
+
+ A standard dashboard that tracks key indicators like delivery success count, matched event count, publish success count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Event Grid Partner Topics with New Relic?
+
+ [New Relic Azure Event Grid Partner Topics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure partner topics via different metrics including delivery success count, matched event count, publish success count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid Partner Topics is critical to track the performance through key metrics. Download New Relic Azure Event Grid Partner Topics monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid Partner Topics Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid Partner Topics
+documentation:
+ - name: Azure Event Grid Partner Topics installation docs
+ description: |
+ Monitor Azure Event Grid Partner Topics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-partner-topics-monitoring-integration/
+keywords:
+ - azure
+ - event grid
+ - product partnerships
+dashboards:
+ - azure-event-grid-partner-topics
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-partner-topics/logo.png b/quickstarts/azure/azure-event-grid-partner-topics/logo.png
new file mode 100644
index 0000000000..907343a55e
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-partner-topics/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-subscriptions/config.yml b/quickstarts/azure/azure-event-grid-subscriptions/config.yml
new file mode 100644
index 0000000000..eecdaad098
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-subscriptions/config.yml
@@ -0,0 +1,42 @@
+id: c5ab28e0-e920-4d36-8c29-2fe7d5ce48f1
+slug: azure-event-grid-subscriptions
+description: |-
+ ## What is Azure Event Grid Subscriptions?
+
+ Azure Event Grid Subscriptions tells Event Grid which events on a topic you're interested in receiving. The endpoint or built-in mechanism to route events, sometimes to more than one handler. Subscriptions are also used by handlers to intelligently filter incoming events.
+
+ ### New Relic Azure Event Grid Subscriptions quickstart features
+
+ A standard dashboard that tracks key indicators like delivery failed events, delivered events, dropped events and matched events. It runs custom queries and visualizes the data immediately
+
+
+ ### Why monitor Azure Event Grid Subscriptions with New Relic?
+
+ [New Relic Azure Event Grid Subscriptions](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure event grid subscriptions via different metrics including delivery failed events, delivered events, dropped events and matched events.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid Subscriptions is critical to track the performance through key metrics. Download New Relic Azure Event Grid Subscriptions monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid Subscriptions Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid Subscriptions
+documentation:
+ - name: Azure Event Grid Subscriptions installation docs
+ description: |
+ Monitor Azure Event Grid Subscriptions by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-subscriptions-monitoring-integration/
+keywords:
+ - azure
+ - event grid
+ - event grid subscriptions
+ - product partnerships
+dashboards:
+ - azure-event-grid-subscriptions
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-subscriptions/logo.png b/quickstarts/azure/azure-event-grid-subscriptions/logo.png
new file mode 100644
index 0000000000..228b1b8dea
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-subscriptions/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-system-topics/config.yml b/quickstarts/azure/azure-event-grid-system-topics/config.yml
new file mode 100644
index 0000000000..09d6b322b1
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-system-topics/config.yml
@@ -0,0 +1,40 @@
+id: d55a0980-e633-4ae0-9ea2-a6025f270c02
+slug: azure-event-grid-system-topics
+description: |-
+ ## What is Azure Event Grid System Topics?
+
+ A system topic in Event Grid represents one or more events published by Azure services such as Azure storage and Azure event hubs. For example, a system topic may represent all blob events or only blob created and blob deleted events published for a specific storage account.
+
+ ### New Relic Azure Event Grid System Topics quickstart features
+
+ A standard dashboard that tracks key indicators like delivery success count, matched event count, publish success count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Event Grid System Topics with New Relic?
+
+ [New Relic Azure Event Grid System Topics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure system topics via different metrics including delivery success count, matched event count, publish success count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid System Topics is critical to track the performance through key metrics. Download New Relic Azure Event Grid System Topics monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid System Topics Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid System Topics
+documentation:
+ - name: Azure Event Grid System Topics installation docs
+ description: |
+ Monitor Azure Event Grid System Topics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-system-topics-monitoring-integration/
+keywords:
+ - azure
+ - event grid
+ - product partnerships
+dashboards:
+ - azure-event-grid-system-topics
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-system-topics/logo.png b/quickstarts/azure/azure-event-grid-system-topics/logo.png
new file mode 100644
index 0000000000..142ee540a9
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-system-topics/logo.png differ
diff --git a/quickstarts/azure/azure-event-grid-topics/config.yml b/quickstarts/azure/azure-event-grid-topics/config.yml
new file mode 100644
index 0000000000..1c413c8b49
--- /dev/null
+++ b/quickstarts/azure/azure-event-grid-topics/config.yml
@@ -0,0 +1,42 @@
+id: 0c301dd2-2eef-458a-9e1f-9d4fd4f9e944
+slug: azure-event-grid-topics
+description: |-
+ ## What is Azure Event Grid Topics?
+
+ Event Grid is a highly scalable, serverless event broker that you can use to integrate applications using events. Event Grid topic provides an endpoint where the source sends events. A topic is used for a collection of related events. To respond to certain types of events, subscribers decide which topics to subscribe to.
+
+ ### New Relic Azure Event Grid Topics quickstart features
+
+ A standard dashboard that tracks key indicators like delivery success count, matched event count, publish success count. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Event Grid Topics with New Relic?
+
+ [New Relic Azure Event Grid Topics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Batch via different metrics including delivery success count, matched event count, publish success count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Event Grid Topics is critical to track the performance through key metrics. Download New Relic Azure Event Grid Topics monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Event Grid Topics Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Event Grid Topics
+documentation:
+ - name: Azure Event Grid Topics installation docs
+ description: |
+ Monitor Azure Event Grid Topics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-event-grid-topics-monitoring-integration/
+keywords:
+ - azure
+ - event grid
+ - event grid topics
+ - product partnerships
+dashboards:
+ - azure-event-grid-topics
+dataSourceIDs:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-event-grid-topics/logo.png b/quickstarts/azure/azure-event-grid-topics/logo.png
new file mode 100644
index 0000000000..3da3634fa4
Binary files /dev/null and b/quickstarts/azure/azure-event-grid-topics/logo.png differ
diff --git a/quickstarts/azure/azure-face-api/config.yml b/quickstarts/azure/azure-face-api/config.yml
new file mode 100644
index 0000000000..2bb39fcb0c
--- /dev/null
+++ b/quickstarts/azure/azure-face-api/config.yml
@@ -0,0 +1,41 @@
+id: 028c9f7f-77e7-4470-b7e2-c7512f8a292b
+slug: azure-face-api
+description: |-
+ ## What is Azure Face API?
+
+ Azure Face service provides AI algorithms that detect, recognize and analyze human faces in images. Facial recognition software is important in many different scenarios, such as identity verification, touchless access control and face blurring for privacy.
+
+ ### New Relic Azure Face API quickstart features
+
+ A standard dashboard that tracks key indicators like face transactions, total calls, face images trained and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Face API with New Relic?
+
+ [New Relic Azure Face API](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Face API via different metrics including face transactions, total calls, face images trained and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Face API is critical to track the performance through key metrics. Download New Relic Azure Face API monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Face API.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Face API
+documentation:
+ - name: Azure Face API installation docs.
+ description: |
+ Monitor Azure Face API by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - face api
+ - product partnerships
+dashboards:
+ - azure-face-api
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-face-api/logo.png b/quickstarts/azure/azure-face-api/logo.png
new file mode 100644
index 0000000000..d94d727f15
Binary files /dev/null and b/quickstarts/azure/azure-face-api/logo.png differ
diff --git a/quickstarts/azure/azure-form-recognizer/config.yml b/quickstarts/azure/azure-form-recognizer/config.yml
new file mode 100644
index 0000000000..514744eebd
--- /dev/null
+++ b/quickstarts/azure/azure-form-recognizer/config.yml
@@ -0,0 +1,41 @@
+id: d3f5e348-55d8-455a-8afd-53c23d4cc00b
+slug: azure-form-recognizer
+description: |-
+ ## What is Azure Form Recognizer?
+
+ Azure Form Recognizer is a cloud-based Azure Applied AI Service that enables you to build intelligent document processing solutions. Massive amounts of data, spanning a wide variety of data types, are stored in forms and documents.
+
+ ### New Relic Azure Form Recognizer quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, successful calls, success rate, Proccessed Pages and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Form Recognizer with New Relic?
+
+ [New Relic Azure Form Recognizer](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Form Recognizer via different metrics including total calls, successful calls, success rate, Proccessed Pages and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Form Recognizer is critical to track the performance through key metrics. Download New Relic Azure Form Recognizer monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Form Recognizer.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Form Recognizer
+documentation:
+ - name: Azure Form Recognizer installation docs.
+ description: |
+ Monitor Azure Form Recognizer by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - form recognizer
+ - product partnerships
+dashboards:
+ - azure-form-recognizer
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-form-recognizer/logo.png b/quickstarts/azure/azure-form-recognizer/logo.png
new file mode 100644
index 0000000000..2aed5573b6
Binary files /dev/null and b/quickstarts/azure/azure-form-recognizer/logo.png differ
diff --git a/quickstarts/azure/azure-functions-workflow/config.yml b/quickstarts/azure/azure-functions-workflow/config.yml
new file mode 100644
index 0000000000..6b5ee062dd
--- /dev/null
+++ b/quickstarts/azure/azure-functions-workflow/config.yml
@@ -0,0 +1,43 @@
+id: 099258cc-d981-40d4-907c-3b2881595735
+slug: azure-functions-workflow
+description: |-
+ ## What is Azure Functions Workflow?
+
+ Azure Functions Workflow refers to Azure Logic Apps under standard plan type. Azure Logic Apps is a cloud platform where you can create and run automated workflows with little to no code. By using the visual designer and selecting from prebuilt operations, you can quickly build a workflow that integrates and manages your apps, data, services and systems.
+
+ ### New Relic Azure Functions Workflow quickstart features
+
+ A standard dashboard that tracks key indicators like app connections, workflow runs, HTTP response time, bytes sent and bytes received. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Functions Workflow with New Relic?
+
+ [New Relic Azure Functions Workflow](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Functions Workflow via different metrics including app connections, workflow runs, HTTP response time, bytes sent and bytes received.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Functions Workflow is critical to track the performance through key metrics. Download New Relic Azure Functions Workflow monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Functions Workflow service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Functions Workflow
+documentation:
+ - name: Azure Functions Workflow installation docs
+ description: |
+ Monitor Azure Functions Workflow by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-functions-workflow-monitoring-integration/
+keywords:
+ - azure
+ - logic apps
+ - workflow apps
+ - functions workflow
+ - product partnerships
+dashboards:
+ - azure-functions-workflow
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-functions-workflow/logo.png b/quickstarts/azure/azure-functions-workflow/logo.png
new file mode 100644
index 0000000000..1bb4e7528c
Binary files /dev/null and b/quickstarts/azure/azure-functions-workflow/logo.png differ
diff --git a/quickstarts/azure/azure-hdinsight/config.yml b/quickstarts/azure/azure-hdinsight/config.yml
new file mode 100644
index 0000000000..0cda18e086
--- /dev/null
+++ b/quickstarts/azure/azure-hdinsight/config.yml
@@ -0,0 +1,40 @@
+id: 035f4083-0e3c-43f0-aca3-cc4b71730457
+slug: azure-hdinsight
+title: Azure HDInsight
+description: |-
+ ## What is Azure HDInsight?
+
+ Azure HDInsight is a managed, full-spectrum, open-source analytics service in the cloud for enterprises. With HDInsight, you can use open-source frameworks such as, Apache Spark, Apache Hive, LLAP, Apache Kafka, Hadoop and more, in your Azure environment.
+
+ ### New Relic Azure HDInsight quickstart features
+
+ A standard dashboard that tracks key indicators like categorized gateway requests, pending memory, pending CPU. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure HDInsight with New Relic?
+
+ [New Relic Azure HDInsight](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure HDInsight via different metrics including categorized gateway requests, pending memory and pending CPU.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure HDInsight is critical to tracking the performance through key metrics. Install the New Relic Azure HDInsight monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure HDInsight service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure HDInsight installation docs
+ description: |
+ Monitor Azure HDInsight by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-hdinsight-monitoring-integration/
+keywords:
+ - azure
+ - hdinsight
+ - product partnerships
+dashboards:
+ - azure-hdinsight
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-hdinsight/logo.png b/quickstarts/azure/azure-hdinsight/logo.png
new file mode 100644
index 0000000000..34c6046436
Binary files /dev/null and b/quickstarts/azure/azure-hdinsight/logo.png differ
diff --git a/quickstarts/azure/azure-immersive-reader/config.yml b/quickstarts/azure/azure-immersive-reader/config.yml
new file mode 100644
index 0000000000..56793e6e30
--- /dev/null
+++ b/quickstarts/azure/azure-immersive-reader/config.yml
@@ -0,0 +1,41 @@
+id: 47ef32ba-fd2c-4ff1-9866-0c5847d5c6ca
+slug: azure-immersive-reader
+description: |-
+ ## What is Azure Immersive Reader?
+
+ Azure Immersive Reader is part of Azure Applied AI Services and is an inclusively designed tool that implements proven techniques to improve reading comprehension for new readers, language learners and people with learning differences such as dyslexia.
+
+ ### New Relic Azure Immersive Reader quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, successful calls, processed characters and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Immersive Reader with New Relic?
+
+ [New Relic Azure Immersive Reader](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Immersive Reader via different metrics including total calls, successful calls, processed characters and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Immersive Reader is critical to track the performance through key metrics. Download New Relic Azure Immersive Reader monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Immersive Reader.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Immersive Reader
+documentation:
+ - name: Azure Immersive Reader installation docs.
+ description: |
+ Monitor Azure Immersive Reader by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - immersive reader
+ - product partnerships
+dashboards:
+ - azure-immersive-reader
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-immersive-reader/logo.png b/quickstarts/azure/azure-immersive-reader/logo.png
new file mode 100644
index 0000000000..66e188b568
Binary files /dev/null and b/quickstarts/azure/azure-immersive-reader/logo.png differ
diff --git a/quickstarts/azure/azure-integration-service-environment/config.yml b/quickstarts/azure/azure-integration-service-environment/config.yml
new file mode 100644
index 0000000000..1d556dcd34
--- /dev/null
+++ b/quickstarts/azure/azure-integration-service-environment/config.yml
@@ -0,0 +1,41 @@
+id: 6d356923-129b-4fbd-89cf-3df5fe75fa62
+slug: azure-integration-service-environment
+title: Azure Integration Service Environment
+description: |-
+ ## What is Azure Integration Service Environment?
+
+ An integration service environment is a fully isolated and dedicated environment for all enterprise-scale integration needs. When you create a new integration service environment, it's injected into your Azure Virtual Network allowing you to deploy Logic Apps as a service in your VNET.
+
+ ### New Relic Azure Integration Service Environment quickstart features
+
+ A standard dashboard that tracks key indicators like actions completed, action latency, actions failed and connector memory usage. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Integration Service Environment with New Relic?
+
+ [New Relic Azure Integration Service Environment](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Integration Service Environment via different metrics including actions completed, action latency, actions failed and connector memory usage.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Integration Service Environment is critical to tracking the performance through key metrics. Install the New Relic Azure Integration Service Environment monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Integration Service Environment.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Integration Service Environment installation docs
+ description: |
+ Monitor Azure Integration Service Environment by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-integration-service-environment-monitoring-integration/
+keywords:
+ - azure
+ - integration service environment
+ - integration service environments
+ - product partnerships
+dashboards:
+ - azure-integration-service-environment
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-integration-service-environment/logo.png b/quickstarts/azure/azure-integration-service-environment/logo.png
new file mode 100644
index 0000000000..16d8f7cd3f
Binary files /dev/null and b/quickstarts/azure/azure-integration-service-environment/logo.png differ
diff --git a/quickstarts/azure/azure-iot-central-applications/config.yml b/quickstarts/azure/azure-iot-central-applications/config.yml
new file mode 100644
index 0000000000..acf187b0ec
--- /dev/null
+++ b/quickstarts/azure/azure-iot-central-applications/config.yml
@@ -0,0 +1,40 @@
+id: 911a0700-8e41-4bc7-b976-e662268792b5
+slug: azure-iot-central-applications
+description: |-
+ ## What is Azure IoT Central Applications?
+
+ IoT Central is an IoT application platform as a service (aPaaS) that reduces the burden and cost of developing, managing and maintaining IoT solutions. IoT Central streamlines the development of a complex and continually evolving IoT infrastructure by letting you to focus your efforts on determining the business impact you can create with the IoT data stream.
+
+ ### New Relic Azure IoT Central Applications quickstart features
+
+ A standard dashboard that tracks key indicators like c2d commands success, connected device count, data export error and device data usage. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure IoT Central Applications with New Relic?
+
+ [New Relic Azure IoT Central Applications](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure IoT Central Applications via different metrics including c2d commands success, connected device count, data export error and device data usage.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure IoT Central Applications is critical to track the performance through key metrics. Download New Relic Azure IoT Central Applications monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure IoT Central Applications Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure IoT Central Applications
+documentation:
+ - name: Azure IoT Central Applications installation docs
+ description: |
+ Monitor Azure IoT Central Applications by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-central-application-monitoring-integration/
+keywords:
+ - azure
+ - iot central applications
+ - product partnerships
+dashboards:
+ - azure-iot-central-applications
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-iot-central-applications/logo.png b/quickstarts/azure/azure-iot-central-applications/logo.png
new file mode 100644
index 0000000000..a49ae3614c
Binary files /dev/null and b/quickstarts/azure/azure-iot-central-applications/logo.png differ
diff --git a/quickstarts/azure/azure-iot-hub/config.yml b/quickstarts/azure/azure-iot-hub/config.yml
new file mode 100644
index 0000000000..6dd7a39c6b
--- /dev/null
+++ b/quickstarts/azure/azure-iot-hub/config.yml
@@ -0,0 +1,40 @@
+id: 258b1e34-bc62-4692-b788-e652a884d916
+slug: azure-iot-hub
+title: Azure IoT Hub
+description: |-
+ ## What is Azure IoT Hub?
+
+ Azure IoT Hub is a managed service hosted in the cloud that acts as a central message hub for communication between an IoT application and its attached devices.
+
+ ### New Relic Azure IoT Hub quickstart features
+
+ A standard dashboard that tracks key indicators like jobs completed, jobs failed, D2C endpoints latency and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure IoT Hub with New Relic?
+
+ [New Relic Azure Iothub](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure IoT Hub via different metrics including jobs completed, jobs failed, D2C endpoints latency and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure IoT Hub is critical to tracking the performance through key metrics. Install the New Relic Azure IoT Hub monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure IoT Hub service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure IoT Hub installation docs
+ description: |
+ Monitor Azure IoT Hub by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-iot-hub-monitoring-integration/
+keywords:
+ - azure
+ - iot hub
+ - product partnerships
+dashboards:
+ - azure-iot-hub
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-iot-hub/logo.png b/quickstarts/azure/azure-iot-hub/logo.png
new file mode 100644
index 0000000000..f16a356f43
Binary files /dev/null and b/quickstarts/azure/azure-iot-hub/logo.png differ
diff --git a/quickstarts/azure/azure-language-service/config.yml b/quickstarts/azure/azure-language-service/config.yml
new file mode 100644
index 0000000000..2f6e1b7ecb
--- /dev/null
+++ b/quickstarts/azure/azure-language-service/config.yml
@@ -0,0 +1,41 @@
+id: 20964ca2-a00c-4f70-9d25-59ce5208f845
+slug: azure-language-service
+description: |-
+ ## What is Azure Language Service?
+
+ Azure Cognitive Service for Language is a cloud-based service that provides Natural Language Processing (NLP) features for understanding and analyzing text. Use this service to help build intelligent applications using the web-based Language Studio, REST APIs and client libraries.
+
+ ### New Relic Azure Language Service quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, successful calls, success rate, processed text records, processed health text records and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Language Service with New Relic?
+
+ [New Relic Azure Language Service](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Language Service via different metrics including total calls, successful calls, processed text records, processed health text records and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Language Service is critical to track the performance through key metrics. Download New Relic Azure Language Service monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Language Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Language Service
+documentation:
+ - name: Azure Language Service installation docs.
+ description: |
+ Monitor Azure Language Service by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - language
+ - product partnerships
+dashboards:
+ - azure-language-service
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-language-service/logo.png b/quickstarts/azure/azure-language-service/logo.png
new file mode 100644
index 0000000000..1973e90168
Binary files /dev/null and b/quickstarts/azure/azure-language-service/logo.png differ
diff --git a/quickstarts/azure/azure-machine-learning/config.yml b/quickstarts/azure/azure-machine-learning/config.yml
new file mode 100644
index 0000000000..ec1eff9ebb
--- /dev/null
+++ b/quickstarts/azure/azure-machine-learning/config.yml
@@ -0,0 +1,43 @@
+id: 7b419a4e-f2e7-4e2d-b0fc-130cd8e942c4
+slug: azure-machine-learning
+title: Azure Machine Learning Through Azure Monitor Integration
+description: |-
+ ## What is Azure Machine Learning?
+
+ Azure Machine Learning empowers data scientists and developers to build, deploy, and manage high-quality models faster and with confidence.
+
+ ### New Relic Azure Machine Learning quickstart features
+
+ A standard dashboard that tracks key indicators like Job Execution, ActiveCores, CpuUtilization, FinalizingRuns, Model Deployment and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Machine Learning with New Relic?
+
+ [New Relic Azure Machine Learning](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration/) monitoring quickstart empowers you to track the performance of Azure Machine Learning via different metrics including Job Execution, ActiveCores, CpuUtilization, FinalizingRuns, Model Deployment and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitor Azure Machine Learning Through Azure Monitor Integration by connecting Azure to New Relic
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Machine Learning installation docs
+ description: |
+ Monitor Azure Machine Learning by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-machine-learning-monitor-integration/
+keywords:
+ - azure
+ - azure machine learning
+ - machine learning
+ - azure ml
+dashboards:
+ - azure-machine-learning
+dataSourceIds:
+ - azure-monitor
+alertPolicies:
+ - azure-machine-learning
\ No newline at end of file
diff --git a/quickstarts/azure/azure-machine-learning/logo.png b/quickstarts/azure/azure-machine-learning/logo.png
new file mode 100644
index 0000000000..020f948ca9
Binary files /dev/null and b/quickstarts/azure/azure-machine-learning/logo.png differ
diff --git a/quickstarts/azure/azure-maps/config.yml b/quickstarts/azure/azure-maps/config.yml
new file mode 100644
index 0000000000..d32cbf700c
--- /dev/null
+++ b/quickstarts/azure/azure-maps/config.yml
@@ -0,0 +1,40 @@
+id: 263cc05f-d01d-4313-a4aa-62df965c33f6
+slug: azure-maps
+description: |-
+ ## What is Azure Maps?
+
+ Azure Maps is a collection of geospatial services and SDKs that use fresh mapping data to provide geographic context to web and mobile applications.
+
+ ### New Relic Azure Maps quickstart features
+
+ A standard dashboard that tracks key indicators like availability, creator usage and usage. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Maps with New Relic?
+
+ [New Relic Azure Maps](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Maps via different metrics including availability, creator usage and usage.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Azure Maps is a collection of geospatial services and SDKs that use fresh mapping data to provide geographic context to web and mobile applications.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Maps
+documentation:
+ - name: Azure Maps installation docs
+ description: |
+ Monitor Azure Maps by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-maps-monitoring-integration/
+keywords:
+ - azure
+ - maps
+ - product partnerships
+dashboards:
+ - azure-maps
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-maps/logo.svg b/quickstarts/azure/azure-maps/logo.svg
new file mode 100644
index 0000000000..cd35afe7a4
--- /dev/null
+++ b/quickstarts/azure/azure-maps/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/azure/azure-media-services-live-events/config.yml b/quickstarts/azure/azure-media-services-live-events/config.yml
new file mode 100644
index 0000000000..5053055a03
--- /dev/null
+++ b/quickstarts/azure/azure-media-services-live-events/config.yml
@@ -0,0 +1,41 @@
+id: 50da112b-302d-4c4c-8672-d347aff1c36a
+slug: azure-media-services-live-events
+description: |-
+ ## What is Azure Media Services Live Events?
+
+ Azure Media Services Live Events is a service provided by Microsoft Azure that enables live video and audio streaming for various events such as conferences, webinars, concerts and sports events. It allows users to capture, encode, package and deliver live video content to audiences worldwide via the internet.
+
+ ### New Relic Azure Media Services Live Events quickstart features
+
+ A standard dashboard that tracks key indicators like ingest bitrate, ingest drift value, ingest last timestamp and live output last timestamp. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Media Services Live Events with New Relic?
+
+ [New Relic Azure Media Services Live Events](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Media Services Live Events via different metrics including ingest bitrate, ingest drift value, ingest last timestamp and live output last timestamp.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Media Services Live Events is critical to track the performance of the live events via key metrics. Download New Relic Azure Media Services Live Events monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure SignalR Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Media Services Live Events
+documentation:
+ - name: Azure Media Services Live Events installation docs
+ description: |
+ Monitor Azure Media Services Live Events by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-live-events-monitoring-integration/
+keywords:
+ - azure
+ - media services
+ - live events
+ - product partnerships
+dashboards:
+ - azure-media-services-live-events
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-media-services-live-events/logo.png b/quickstarts/azure/azure-media-services-live-events/logo.png
new file mode 100644
index 0000000000..338aee6adc
Binary files /dev/null and b/quickstarts/azure/azure-media-services-live-events/logo.png differ
diff --git a/quickstarts/azure/azure-media-services-streaming-endpoints/config.yml b/quickstarts/azure/azure-media-services-streaming-endpoints/config.yml
new file mode 100644
index 0000000000..b163cdbc94
--- /dev/null
+++ b/quickstarts/azure/azure-media-services-streaming-endpoints/config.yml
@@ -0,0 +1,41 @@
+id: 19935340-6dd8-45ae-b5a8-79432e5c4f3a
+slug: azure-media-services-streaming-endpoints
+description: |-
+ ## What is Azure Media Services Streaming Endpoints?
+
+ A Streaming Endpoint represents a dynamic (just-in-time) packaging and origin service that can deliver your live and on-demand content directly to a client player app, using one of the common streaming media protocols (HLS or DASH).
+
+ ### New Relic Azure MediaServices StreamingEndpoints quickstart features
+
+ A standard dashboard that tracks key indicators like CPU usage, egress, egress bandwidth, requests and success E2E latency. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Media Services Streaming Endpoints with New Relic?
+
+ [New Relic Azure Media Services Streaming Endpoints](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Media Services Streaming Endpoints via different metrics including CPU usage, egress, egress bandwidth, requests and success E2E latency.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Media Services Streaming Endpoints is critical to track the performance of the streaming endpoints via key metrics. Download New Relic Azure Media Services Streaming Endpoints monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Media Services Streaming Endpoints Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Media Services Streaming Endpoints
+documentation:
+ - name: Azure Media Services Streaming Endpoints installation docs
+ description: |
+ Monitor Azure Media Services Streaming Endpoints by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-streaming-endpoints-monitoring-integration/
+keywords:
+ - azure
+ - media services streaming endpoints
+ - product partnerships
+dashboards:
+ - azure-media-services-streaming-endpoints
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-media-services-streaming-endpoints/logo.png b/quickstarts/azure/azure-media-services-streaming-endpoints/logo.png
new file mode 100644
index 0000000000..9664106f55
Binary files /dev/null and b/quickstarts/azure/azure-media-services-streaming-endpoints/logo.png differ
diff --git a/quickstarts/azure/azure-media-services-video-analyzer/config.yml b/quickstarts/azure/azure-media-services-video-analyzer/config.yml
new file mode 100644
index 0000000000..68a9807f98
--- /dev/null
+++ b/quickstarts/azure/azure-media-services-video-analyzer/config.yml
@@ -0,0 +1,41 @@
+id: 70512fed-b33b-48d6-95ae-60ad9415baa4
+slug: azure-media-services-video-analyzer
+description: |-
+ ## What is Azure Media Services Video Analyzer?
+
+ Azure Video Analyzer for Media Azure Video Analyzer for Media, previously known as Azure Video Indexer, is available under AMS and also as a separate Azure service.
+
+ ### New Relic Azure Media Services Video Analyzer quickstart features
+
+ A standard dashboard that tracks key indicators like ingress bytes and pipelines. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Media Services Video Analyzer with New Relic?
+
+ [New Relic Azure Media Services Video Analyzer](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Media Services Video Analyzer via different metrics including ingress bytes and pipelines.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Media Services Video Analyzer is critical to track the performance of the video analyzer via key metrics. Download New Relic Azure Media Services Video Analyzer monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Media Services Video Analyzer Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Media Services Video Analyzer
+documentation:
+ - name: Azure Media Services Video Analyzer installation docs
+ description: |
+ Monitor Azure Media Services Video Analyzer by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-video-analyzer-monitoring-integration/
+keywords:
+ - azure
+ - media services video analyzer
+ - product partnerships
+dashboards:
+ - azure-media-services-video-analyzer
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-media-services-video-analyzer/logo.png b/quickstarts/azure/azure-media-services-video-analyzer/logo.png
new file mode 100644
index 0000000000..32b7fb26ba
Binary files /dev/null and b/quickstarts/azure/azure-media-services-video-analyzer/logo.png differ
diff --git a/quickstarts/azure/azure-media-services/config.yml b/quickstarts/azure/azure-media-services/config.yml
new file mode 100644
index 0000000000..6629c0bd32
--- /dev/null
+++ b/quickstarts/azure/azure-media-services/config.yml
@@ -0,0 +1,40 @@
+id: e90a5553-e84c-409c-aef1-5ac05cc90b80
+slug: azure-media-services
+description: |-
+ ## What is Azure Media Services?
+
+ Azure Media Services is a cloud-based platform that enables you to build solutions that achieve broadcast-quality video streaming, enhance accessibility and distribution, analyze content and much more.
+
+ ### New Relic Azure Media Services quickstart features
+
+ A standard dashboard that tracks key indicators like content key policy count, job quota, max running channels and live events count, streaming policy quota used percentage and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Media Services with New Relic?
+
+ [New Relic Azure Media Services](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Media Services via different metrics including content key policy count, job quota, max running channels and live events count, streaming policy quota used percentage and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Media Services is critical to track the performance of media services via key metrics. Download New Relic Azure Media Services monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Media Services.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Media Services
+documentation:
+ - name: Azure Media Services installation docs
+ description: |
+ Monitor Azure Media Services by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-media-services-monitoring-integration/
+keywords:
+ - azure
+ - media services
+ - product partnerships
+dashboards:
+ - azure-media-services
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-media-services/logo.png b/quickstarts/azure/azure-media-services/logo.png
new file mode 100644
index 0000000000..9664106f55
Binary files /dev/null and b/quickstarts/azure/azure-media-services/logo.png differ
diff --git a/quickstarts/azure/azure-netapp-capacity-pools/config.yml b/quickstarts/azure/azure-netapp-capacity-pools/config.yml
new file mode 100644
index 0000000000..5377c1018e
--- /dev/null
+++ b/quickstarts/azure/azure-netapp-capacity-pools/config.yml
@@ -0,0 +1,41 @@
+id: 38dab6c5-98dd-4fbb-aeb8-3d73fc3c2234
+slug: azure-netapp-capacity-pools
+title: Azure NetApp Capacity Pools
+description: |-
+ ## What is Azure NetApp Capacity Pools?
+
+ Azure NetApp Capacity Pools are a way to organize and manage storage capacity in Azure NetApp Files. A capacity pool is a logical container for volumes that share the same performance characteristics and service level. You can create multiple capacity pools within a NetApp account. Azure NetApp Capacity Pool is measured by its provisioned capacity.
+
+ ### New Relic Azure NetApp Capacity Pools quickstart features
+
+ A standard dashboard that tracks key indicators like pool allocated size, pool allocated throughput, pool consumed size and Provisioned throughput for the pool. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure NetApp Capacity Pools with New Relic?
+
+ [New Relic Azure NetApp Capacity Pools](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure NetApp Capacity Pools via different metrics including pool allocated size, pool allocated throughput, pool consumed size and Provisioned throughput for the pool.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure NetApp Capacity Pools is critical to track the performance through key metrics. Download New Relic Azure NetApp Capacity Pools monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure NetApp Capacity Pools service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure NetApp Capacity Pools installation docs
+ description: |
+ Monitor Azure NetApp Capacity Pools by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-capacity-pools-monitoring-integration/
+keywords:
+ - azure
+ - netapp capacity pool
+ - netapp capacity pools
+ - product partnerships
+dashboards:
+ - azure-netapp-capacity-pools
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-netapp-capacity-pools/logo.png b/quickstarts/azure/azure-netapp-capacity-pools/logo.png
new file mode 100644
index 0000000000..6308414cbb
Binary files /dev/null and b/quickstarts/azure/azure-netapp-capacity-pools/logo.png differ
diff --git a/quickstarts/azure/azure-netapp-files/config.yml b/quickstarts/azure/azure-netapp-files/config.yml
new file mode 100644
index 0000000000..ee6c7a22ce
--- /dev/null
+++ b/quickstarts/azure/azure-netapp-files/config.yml
@@ -0,0 +1,41 @@
+id: 118491de-58f3-488c-aacf-bb11960495ec
+slug: azure-netapp-files
+title: Azure NetApp Files
+description: |-
+ ## What is Azure NetApp Files?
+
+ Azure NetApp Files is an Azure native, first-party, enterprise-class, high-performance file storage service. It provides NAS volumes as a service for which you can create NetApp accounts, capacity pools, select service and performance levels, create volumes and manage data protection. Azure NetApp Files supports SMB and NFS protocols and can be used for various use cases such as file sharing, home directories, databases, high-performance computing and more.
+
+ ### New Relic Azure NetApp Files quickstart features
+
+ A standard dashboard that tracks key indicators like average write latency, total throughput, volume consumed size percentage, xregion replication lag time and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure NetApp Files with New Relic?
+
+ [New Relic Azure NetApp Files](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure NetApp Files via different metrics including average write latency, total throughput, volume consumed size percentage, xregion replication lag time and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure NetApp Files is designed to provide high-performance file storage for enterprise workloads, provide high availability for your file storage needs, provides built-in data protection to help ensure the safe storage, availability and recoverability of your data. Download New Relic Azure NetApp Files monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure NetApp Files service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure NetApp Files installation docs
+ description: |
+ Monitor Azure NetApp Files by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-netapp-files-monitoring-integration/
+keywords:
+ - azure
+ - netapp file
+ - netapp files
+ - product partnerships
+dashboards:
+ - azure-netapp-files
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-netapp-files/logo.png b/quickstarts/azure/azure-netapp-files/logo.png
new file mode 100644
index 0000000000..674cabf84a
Binary files /dev/null and b/quickstarts/azure/azure-netapp-files/logo.png differ
diff --git a/quickstarts/azure/azure-network-interface/config.yml b/quickstarts/azure/azure-network-interface/config.yml
new file mode 100644
index 0000000000..c9050bcdc4
--- /dev/null
+++ b/quickstarts/azure/azure-network-interface/config.yml
@@ -0,0 +1,40 @@
+id: 997912ec-fb55-4fb0-8fae-7b717bf3c02d
+slug: azure-network-interface
+description: |-
+ ## What is Azure Network Interface?
+
+ A network interface enables an Azure VM to communicate with internet, Azure and on-premises resources. A VM has one or more network interfaces.
+
+ ### New Relic Azure Network Interface quickstart features
+
+ A standard dashboard solely focused on Azure Network Interface and tracks key indicators like bytes received rate, bytes sent rate, packet received rate and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Network Interface with New Relic?
+
+ [New Relic Azure Network Interface](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Network Interface via different metrics including bytes received rate, bytes sent rate, packet received rate and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Network Interface is critical to track the performance of the networks via key metrics. Download New Relic Azure Network Interface monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Network Interface service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Azure Network Interface
+documentation:
+ - name: Azure Network Interface installation docs
+ description: |
+ Monitor Azure Network Interface by first connecting Azure to New Relic and selecting Azure Networking.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-interface-monitoring-integration/
+keywords:
+ - azure
+ - networking
+ - network interface
+ - product partnerships
+dashboards:
+ - azure-network-interface
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-network-interface/logo.png b/quickstarts/azure/azure-network-interface/logo.png
new file mode 100644
index 0000000000..02b7dc8202
Binary files /dev/null and b/quickstarts/azure/azure-network-interface/logo.png differ
diff --git a/quickstarts/azure/azure-network-watcher/config.yml b/quickstarts/azure/azure-network-watcher/config.yml
new file mode 100644
index 0000000000..643df53493
--- /dev/null
+++ b/quickstarts/azure/azure-network-watcher/config.yml
@@ -0,0 +1,40 @@
+id: 95d69068-dbba-495f-9312-5e6e42708d5e
+slug: azure-network-watcher
+description: |-
+ ## What is Azure Network Watcher?
+
+ Azure Network Watcher provides tools to monitor, diagnose, view metrics and enable or disable logs for resources in an Azure virtual network.
+
+ ### New Relic Azure Network Watcher quickstart features
+
+ A standard dashboard that tracks key indicators like checks failed percent, round trip time, probes failed percent and test result. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Network Watcher with New Relic?
+
+ [New Relic Azure Network Watcher](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Network Watcher via different metrics including checks failed percent, round trip time, probes failed percent and test result.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Azure Network Watcher is designed to monitor and repair the network health of IaaS (Infrastructure-as-a-Service) products including virtual machines (VMs), virtual networks (VNets), application gateways, load balancers, etc. Download New Relic Azure Network Watcher monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Network Watcher service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Network Watcher
+documentation:
+ - name: Azure Network Watcher installation docs
+ description: |
+ Monitor Azure Network Watcher by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-network-watcher-monitoring-integration/
+keywords:
+ - azure
+ - network watcher
+ - product partnerships
+dashboards:
+ - azure-network-watcher
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-network-watcher/logo.png b/quickstarts/azure/azure-network-watcher/logo.png
new file mode 100644
index 0000000000..06f78f970b
Binary files /dev/null and b/quickstarts/azure/azure-network-watcher/logo.png differ
diff --git a/quickstarts/azure/azure-notification-hubs/config.yml b/quickstarts/azure/azure-notification-hubs/config.yml
new file mode 100644
index 0000000000..7972b94313
--- /dev/null
+++ b/quickstarts/azure/azure-notification-hubs/config.yml
@@ -0,0 +1,41 @@
+id: 7bfdc187-36b5-4f4a-a2fc-76052ed4531c
+slug: azure-notification-hubs
+title: Azure Notification Hubs
+description: |-
+ ## What is Azure Notification Hubs?
+
+ Azure Notification Hubs provide an easy-to-use and scaled-out push engine that enables you to send notifications to any platform(iOS, Android, Windows, etc.) from any back-end (cloud or on-premises).
+
+ ### New Relic Azure Notification Hubs quickstart features
+
+ A standard dashboard that tracks key indicators like all incoming requests, successful notifications, payload errors, authorization errors and registration operations. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Notification Hubs with New Relic?
+
+ [New Relic Azure Notification Hubs](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Notification Hubs via different metrics including all incoming requests, successful notifications, payload errors, authorization errors and registration operations.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Notification Hubs is critical to track the performance through key metrics. Download New Relic Azure Notification Hubs monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Notification Hubs service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Notification Hubs installation docs
+ description: |
+ Monitor Azure Notification Hubs by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-notification-hubs-monitoring-integration/
+keywords:
+ - azure
+ - notification hub
+ - notification hubs
+ - product partnerships
+dashboards:
+ - azure-notification-hubs
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-notification-hubs/logo.png b/quickstarts/azure/azure-notification-hubs/logo.png
new file mode 100644
index 0000000000..4761c0e833
Binary files /dev/null and b/quickstarts/azure/azure-notification-hubs/logo.png differ
diff --git a/quickstarts/azure/azure-peering-service/config.yml b/quickstarts/azure/azure-peering-service/config.yml
new file mode 100644
index 0000000000..7f0943daf3
--- /dev/null
+++ b/quickstarts/azure/azure-peering-service/config.yml
@@ -0,0 +1,40 @@
+id: 97f13ea2-f247-47d2-adef-bb9b8cd0f4cd
+slug: azure-peering-service
+title: Azure Peering Service
+description: |-
+ ## What is Azure Peering Service?
+
+ Azure Peering Service is a networking service that enhances the connectivity to Microsoft cloud services such as Microsoft 365, Dynamics 365, software as a service (SaaS) services, Azure, or any Microsoft services accessible via the public internet.
+
+ ### New Relic Azure Peering Service quickstart features
+
+ A standard dashboard that tracks key indicators like round trip time. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Peering Service with New Relic?
+
+ [New Relic Azure Peering Service](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Peering Service via round trip time.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Peering Service is critical to tracking the performance through key metrics. Install the New Relic Azure Peering Service monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Peering Service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Peering Service installation docs
+ description: |
+ Monitor Azure Peering Service by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-service-monitoring-integration/
+keywords:
+ - azure
+ - peering service
+ - product partnerships
+dashboards:
+ - azure-peering-service
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-peering-service/logo.png b/quickstarts/azure/azure-peering-service/logo.png
new file mode 100644
index 0000000000..97de56120b
Binary files /dev/null and b/quickstarts/azure/azure-peering-service/logo.png differ
diff --git a/quickstarts/azure/azure-peering/config.yml b/quickstarts/azure/azure-peering/config.yml
new file mode 100644
index 0000000000..32e1deb5ce
--- /dev/null
+++ b/quickstarts/azure/azure-peering/config.yml
@@ -0,0 +1,41 @@
+id: 88267c0e-1067-4abe-b053-6ee210474e4f
+slug: azure-peering
+title: Azure Peering
+description: |-
+ ## What is Azure Peering?
+
+ Peering is the interconnection between Microsoft's global network (ASN AS8075) and your network for the purpose of exchanging internet traffic between Microsoft online services and Microsoft Azure Services. Carriers or Service Providers can request to connect at any of Microsoft's edge locations.
+
+ ### New Relic Azure Peering quickstart features
+
+ A standard dashboard that tracks key indicators like egress traffic rate, flap counts, packet drop rate, session availability and more. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Peering with New Relic?
+
+ [New Relic Azure Peering](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Peering via different metrics including egress traffic rate, flap counts, packet drop rate, session availability and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Peering is critical to tracking the performance through key metrics. Install the New Relic Azure Peering monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Peering.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Peering installation docs
+ description: |
+ Monitor Azure Peering by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-peering-monitoring-integration/
+keywords:
+ - azure
+ - peering
+ - product partnerships
+dashboards:
+ - azure-peering
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-peering/logo.png b/quickstarts/azure/azure-peering/logo.png
new file mode 100644
index 0000000000..f6d58d41b6
Binary files /dev/null and b/quickstarts/azure/azure-peering/logo.png differ
diff --git a/quickstarts/azure/azure-personalizer/config.yml b/quickstarts/azure/azure-personalizer/config.yml
new file mode 100644
index 0000000000..5293ec53c4
--- /dev/null
+++ b/quickstarts/azure/azure-personalizer/config.yml
@@ -0,0 +1,41 @@
+id: 626ba87e-7915-4223-9d59-ee68f5cc7e0d
+slug: azure-personalizer
+description: |-
+ ## What is Azure Personalizer?
+
+ Azure Personalizer is an AI service that your applications make smarter decisions at scale using reinforcement learning. Personalizer processes information about the state of your application, scenario, and/or users (contexts), and a set of possible decisions and related attributes (actions) to determine the best decision to make. Feedback from your application (rewards) is sent to Personalizer to learn how to improve its decision-making ability in near-real time.
+
+ ### New Relic Azure Personalizer quickstart features
+
+ A standard dashboard that tracks key indicators like Actions per event, successful calls, Action featureId occurrences and Action features per event. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Personalizer with New Relic?
+
+ [New Relic Azure Personalizer](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Personalizer via different metrics including Actions per event, successful calls, Action featureId occurrences and Action features per event.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Personalizer is critical to track the performance through key metrics. Download New Relic Azure Personalizer monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Personalizer.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Personalizer
+documentation:
+ - name: Azure Personalizer installation docs.
+ description: |
+ Monitor Azure Personalizer by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - personalizer
+ - product partnerships
+dashboards:
+ - azure-personalizer
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-personalizer/logo.png b/quickstarts/azure/azure-personalizer/logo.png
new file mode 100644
index 0000000000..4e525cfd30
Binary files /dev/null and b/quickstarts/azure/azure-personalizer/logo.png differ
diff --git a/quickstarts/azure/azure-private-dns-zones/config.yml b/quickstarts/azure/azure-private-dns-zones/config.yml
new file mode 100644
index 0000000000..85fba9c102
--- /dev/null
+++ b/quickstarts/azure/azure-private-dns-zones/config.yml
@@ -0,0 +1,41 @@
+id: cbd1434b-02ae-44a2-a761-862e346776d1
+slug: azure-private-dns-zones
+title: Azure Private DNS Zones
+description: |-
+ ## What is Azure Private DNS Zones?
+
+ Azure Private DNS Zones provide a reliable and secure DNS service for your virtual network. It manages and resolves domain names in the virtual network without the need to configure a custom DNS solution.
+
+ ### New Relic Azure Private DNS Zones quickstart features
+
+ A standard dashboard that tracks key indicators like query volume, record set count, virtual network link count and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Private DNS Zones with New Relic?
+
+ [New Relic Azure Private DNS Zones](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Private DNS Zones via different metrics including query volume, record set capacity utilization, record set count and virtual network link count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Private DNS Zones is critical to track the performance through key metrics. Download New Relic Azure Private DNS Zones monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Private DNS Zones service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Private DNS Zones installation docs
+ description: |
+ Monitor Azure Private DNS Zones by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-private-dns-zones-monitoring-integration/
+keywords:
+ - azure
+ - private dns zone
+ - private dns zones
+ - product partnerships
+dashboards:
+ - azure-private-dns-zones
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-private-dns-zones/logo.png b/quickstarts/azure/azure-private-dns-zones/logo.png
new file mode 100644
index 0000000000..eceae32c11
Binary files /dev/null and b/quickstarts/azure/azure-private-dns-zones/logo.png differ
diff --git a/quickstarts/azure/azure-public-ip-addresses/config.yml b/quickstarts/azure/azure-public-ip-addresses/config.yml
new file mode 100644
index 0000000000..4b63917c7b
--- /dev/null
+++ b/quickstarts/azure/azure-public-ip-addresses/config.yml
@@ -0,0 +1,41 @@
+id: 8877fdff-5304-40a0-b3fd-fd5f6fa41572
+slug: azure-public-ip-addresses
+description: |-
+ ## What is Azure Public IP Addresses?
+
+ Public IP addresses allow Internet resources to communicate inbound to Azure resources. Public IP addresses enable Azure resources to communicate to Internet and public-facing Azure services.
+
+ ### New Relic Azure Public IP Addresses quickstart features
+
+ A standard dashboard that tracks key indicators like DDoS attack, packets by type, bytes by protocol. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Public IP Addresses with New Relic?
+
+ [New Relic Azure Public IP Addresses](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-public-ip-address-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Public IP Addresses via different metrics including DDoS attack, packets by type, bytes by protocol.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Public IP Addresses is critical to track the communication with resources running in Azure over the internet via key metrics. Download New Relic Azure Public IP Addresses monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Public IP Addresses service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Public IP Addresses
+documentation:
+ - name: Azure Public IP Addresses installation docs
+ description: |
+ Monitor Azure Public IP Addresses by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-public-ip-address-monitoring-integration/
+keywords:
+ - azure
+ - public ip addresses
+ - ip address
+ - product partnerships
+dashboards:
+ - azure-public-ip-address
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-public-ip-addresses/logo.png b/quickstarts/azure/azure-public-ip-addresses/logo.png
new file mode 100644
index 0000000000..8437f18de0
Binary files /dev/null and b/quickstarts/azure/azure-public-ip-addresses/logo.png differ
diff --git a/quickstarts/azure/azure-purview/config.yml b/quickstarts/azure/azure-purview/config.yml
new file mode 100644
index 0000000000..63e16b285d
--- /dev/null
+++ b/quickstarts/azure/azure-purview/config.yml
@@ -0,0 +1,42 @@
+id: 5337f5a2-5359-4547-837f-60c0759decf8
+slug: azure-purview
+title: Microsoft Purview
+description: |-
+ ## What is Microsoft Purview?
+
+ Microsoft Purview provides a unified data governance solution to help manage and govern your on-premises, multicloud, and software as a service (SaaS) data. Easily create a holistic, up-to-date map of your data landscape with automated data discovery, sensitive data classification, and end-to-end data lineage. Enable data consumers to access valuable, trustworthy data management.
+
+ ### New Relic Microsoft Purview quickstart features
+
+ A standard dashboard that tracks key indicators like scan cancelled count, scan completed count, scan failed count, data map capacity units count. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Microsoft Purview with New Relic?
+
+ [New Relic Microsoft Purview](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration/) monitoring quickstart empowers you to track the performance of Microsoft Purview via different metrics including scan failed count, scan cancelled count, scan completed count, data map capacity units count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Microsoft Purview is critical to tracking the performance through key metrics. Install the New Relic Microsoft Purview monitoring quickstart to get a pre-built dashboard tailored to monitor your Microsoft Purview service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Microsoft Purview installation docs
+ description: |
+ Monitor Microsoft Purview by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-purview-monitoring-integration/
+keywords:
+ - azure
+ - purview
+ - azure purview
+ - microsoft purview
+ - product partnerships
+dashboards:
+ - azure-purview
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-purview/logo.png b/quickstarts/azure/azure-purview/logo.png
new file mode 100644
index 0000000000..f7eaad50e4
Binary files /dev/null and b/quickstarts/azure/azure-purview/logo.png differ
diff --git a/quickstarts/azure/azure-question-answering/config.yml b/quickstarts/azure/azure-question-answering/config.yml
new file mode 100644
index 0000000000..89e81558f5
--- /dev/null
+++ b/quickstarts/azure/azure-question-answering/config.yml
@@ -0,0 +1,41 @@
+id: 9dabdaa2-c5bf-42a2-bf3c-fdf82b6f08b7
+slug: azure-question-answering
+description: |-
+ ## What is Azure Question answering?
+
+ Question answering provides cloud-based Natural Language Processing (NLP) that allows you to create a natural conversational layer over your data. It is used to find appropriate answers from customer input or from a project.
+
+ ### New Relic Azure Question answering quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, question answering text records, success rate and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Question answering with New Relic?
+
+ [New Relic Azure Question answering](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Question answering via different metrics including total calls, question answering text records, success rate and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Question answering is critical to track the performance through key metrics. Download New Relic Azure Question answering monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Question answering.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Question answering
+documentation:
+ - name: Azure Question answering installation docs.
+ description: |
+ Monitor Azure Question answering by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - Question answering
+ - product partnerships
+dashboards:
+ - azure-question-answering
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-question-answering/logo.png b/quickstarts/azure/azure-question-answering/logo.png
new file mode 100644
index 0000000000..287fae7ee4
Binary files /dev/null and b/quickstarts/azure/azure-question-answering/logo.png differ
diff --git a/quickstarts/azure/azure-relay/config.yml b/quickstarts/azure/azure-relay/config.yml
new file mode 100644
index 0000000000..1588748c5b
--- /dev/null
+++ b/quickstarts/azure/azure-relay/config.yml
@@ -0,0 +1,41 @@
+id: c1211981-229a-4f96-ac32-53e4e8a945bc
+slug: azure-relay
+description: |-
+ ## What is Azure Relay?
+
+ Azure Relay service securely exposes services that run in corporate network to the public cloud. Services can be exposed without opening a port on corporate firewall, or making intrusive changes to corporate network infrastructure.
+
+ ### New Relic Azure Relay quickstart features
+
+ A standard dashboard that tracks key indicators like active connections, active listeners, bytes transferred, success, server error and client error. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Relay with New Relic?
+
+ [New Relic Azure Relay](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Relay via different metrics including active connections, active listeners, bytes transferred, success, server error and client error.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Relay is critical to track the performance through key metrics. Download New Relic Azure Relay monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Relay service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Relay
+documentation:
+ - name: Azure Relay installation docs
+ description: |
+ Monitor Azure Relay by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-relay-monitoring-integration/
+keywords:
+ - azure
+ - relay
+ - product partnerships
+dashboards:
+ - azure-relay
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-relay/logo.png b/quickstarts/azure/azure-relay/logo.png
new file mode 100644
index 0000000000..7dbcd8c14d
Binary files /dev/null and b/quickstarts/azure/azure-relay/logo.png differ
diff --git a/quickstarts/azure/azure-signalr/config.yml b/quickstarts/azure/azure-signalr/config.yml
new file mode 100644
index 0000000000..bbbd1f39f1
--- /dev/null
+++ b/quickstarts/azure/azure-signalr/config.yml
@@ -0,0 +1,41 @@
+id: a422b946-443f-4071-8d61-d250a13b3be7
+slug: azure-signalr
+description: |-
+ ## What is Azure SignalR?
+
+ Azure SignalR Service simplifies the process of adding real-time web functionality to applications over HTTP. This real-time functionality allows the service to push content updates to connected clients, such as a single page web or mobile application.
+
+ ### New Relic Azure SignalR quickstart features
+
+ A standard dashboard that tracks key indicators like connection quota utilization, inbound traffic, user errors and message count. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure SignalR with New Relic?
+
+ [New Relic Azure SignalR](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure SignalR via different metrics including connection quota utilization, inbound traffic, user errors and message count.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure SignalR is critical to track the performance through key metrics. Download New Relic Azure SignalR monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure SignalR service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure SignalR
+documentation:
+ - name: Azure SignalR installation docs
+ description: |
+ Monitor Azure SignalR by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-signalr-monitoring-integration/
+keywords:
+ - azure
+ - signalr
+ - product partnerships
+dashboards:
+ - azure-signalr
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-signalr/logo.png b/quickstarts/azure/azure-signalr/logo.png
new file mode 100644
index 0000000000..a0defe0ab7
Binary files /dev/null and b/quickstarts/azure/azure-signalr/logo.png differ
diff --git a/quickstarts/azure/azure-speech/config.yml b/quickstarts/azure/azure-speech/config.yml
new file mode 100644
index 0000000000..633c9382d6
--- /dev/null
+++ b/quickstarts/azure/azure-speech/config.yml
@@ -0,0 +1,41 @@
+id: 113d1823-ecd1-4db9-ae24-9758e5c3e75b
+slug: azure-speech
+description: |-
+ ## What is Azure Speech?
+
+ The Speech service provides speech to text and text to speech capabilities with an Azure Speech resource. You can transcribe speech to text with high accuracy, produce natural sounding text to speech voices, translate spoken audio, and use speaker recognition during conversations.
+
+ ### New Relic Azure Speech quickstart features
+
+ A standard dashboard that tracks key indicators like audio seconds translated, synthesized characters, speaker profiles, total calls, successful calls, success rate and total errors. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Speech with New Relic?
+
+ [New Relic Speech](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Speech via different metrics including audio seconds translated, synthesized characters, speaker profiles, total calls, successful calls, success rate and total errors.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Speech is critical to track the performance through key metrics. Download New Relic Azure Speech monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Speech.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Speech
+documentation:
+ - name: Azure Speech installation docs.
+ description: |
+ Monitor Azure Speech by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - Speech
+ - product partnerships
+dashboards:
+ - azure-speech
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-speech/logo.png b/quickstarts/azure/azure-speech/logo.png
new file mode 100644
index 0000000000..8e501a1fe6
Binary files /dev/null and b/quickstarts/azure/azure-speech/logo.png differ
diff --git a/quickstarts/azure/azure-spring-apps/config.yml b/quickstarts/azure/azure-spring-apps/config.yml
new file mode 100644
index 0000000000..42d6493132
--- /dev/null
+++ b/quickstarts/azure/azure-spring-apps/config.yml
@@ -0,0 +1,41 @@
+id: 9402af65-890c-49d7-aa00-d450d80b1505
+slug: azure-spring-apps
+title: Azure Spring Apps
+description: |-
+ ## What is Azure Spring Apps?
+
+ Spring Cloud Azure is an open source project that helps make it easier to use Azure services in Spring applications.
+
+ ### New Relic Azure Spring Apps quickstart features
+
+ A standard dashboard that tracks key indicators like memory usage, CPU usage, global request total count and global request average time. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Spring Apps with New Relic?
+
+ [New Relic Azure Spring Apps](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Spring Apps via different metrics including memory usage, CPU usage, global request total count and global request average time.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Spring Apps is critical to track the performance through key metrics. Download New Relic Azure Spring Apps monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Spring Apps service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Spring Apps installation docs
+ description: |
+ Monitor Azure Spring Apps by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-spring-apps-monitoring-integration/
+keywords:
+ - azure
+ - spring app
+ - spring apps
+ - product partnerships
+dashboards:
+ - azure-spring-apps
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-spring-apps/logo.png b/quickstarts/azure/azure-spring-apps/logo.png
new file mode 100644
index 0000000000..d75c489aa3
Binary files /dev/null and b/quickstarts/azure/azure-spring-apps/logo.png differ
diff --git a/quickstarts/azure/azure-sql-elastic-pools/config.yml b/quickstarts/azure/azure-sql-elastic-pools/config.yml
new file mode 100644
index 0000000000..8d063c2e52
--- /dev/null
+++ b/quickstarts/azure/azure-sql-elastic-pools/config.yml
@@ -0,0 +1,41 @@
+id: 621022e3-cbc9-40d1-a89a-3cf076e5a98a
+slug: azure-sql-elastic-pools
+description: |-
+ ## What is Azure SQL Elastic pools?
+
+ Azure SQL Elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a single server and share a set number of resources at a set price. Elastic pools in SQL Database enable software as a service (SaaS) developers to optimize the price performance for a group of databases within a prescribed budget while delivering performance elasticity for each database.
+
+ ### New Relic Azure SQL Elastic pools quickstart features
+
+ A standard dashboard that tracks key indicators like CPU used, workers usage, physical data read percent, sessions count and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure SQL Elastic pools with New Relic?
+
+ [New Relic Azure SQL Elastic pools](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure SQL Elastic pools via different metrics including CPU used, workers usage, physical data read percent and sessions count and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure SQL Elastic pools is to track the price performance for a group of databases via key metrics. Download New Relic Azure SQL Elastic pools monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure SQL Elastic pools service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure SQL Elastic pools
+documentation:
+ - name: Azure SQL Elastic pools installation docs
+ description: |
+ Monitor Azure SQL Elastic pools by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-sql-database-monitoring-integration/
+keywords:
+ - azure
+ - sql elastic pool
+ - sql elastic pools
+ - product partnerships
+dashboards:
+ - azure-sql-elastic-pool
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-sql-elastic-pools/logo.png b/quickstarts/azure/azure-sql-elastic-pools/logo.png
new file mode 100644
index 0000000000..e0a2c04ca3
Binary files /dev/null and b/quickstarts/azure/azure-sql-elastic-pools/logo.png differ
diff --git a/quickstarts/azure/azure-storage-sync/config.yml b/quickstarts/azure/azure-storage-sync/config.yml
new file mode 100644
index 0000000000..18ddf6fc75
--- /dev/null
+++ b/quickstarts/azure/azure-storage-sync/config.yml
@@ -0,0 +1,35 @@
+id: 73e3df54-2252-4f95-9e67-450d93b91953
+slug: azure-storage-sync
+description: |-
+ ## What is Azure Storage Sync?
+
+ Azure Storage Sync enables centralizing your organization's file shares in Azure Files, while keeping the flexibility, performance and compatibility of a Windows file server.
+
+ ### Why monitor Azure Storage Sync with New Relic?
+
+ [New Relic Azure Storage Sync](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Storage Sync via different metrics including files synced, sync session result, bytes synced, server online status and files not syncing.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Storage Sync is critical to track the performance through key metrics. Download New Relic Azure Storage Sync monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Storage Sync service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Azure Storage Sync
+documentation:
+ - name: Azure Storage Sync installation docs
+ description: |
+ Monitor Azure Storage Sync by first connecting Azure to New Relic and selecting Azure Storage Sync.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-storage-sync-monitoring-integration/
+keywords:
+ - azure
+ - storage sync
+ - product partnerships
+dashboards:
+ - azure-storage-sync
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-storage-sync/logo.png b/quickstarts/azure/azure-storage-sync/logo.png
new file mode 100644
index 0000000000..589402c5f8
Binary files /dev/null and b/quickstarts/azure/azure-storage-sync/logo.png differ
diff --git a/quickstarts/azure/azure-stream-analytics/config.yml b/quickstarts/azure/azure-stream-analytics/config.yml
new file mode 100644
index 0000000000..41142267ba
--- /dev/null
+++ b/quickstarts/azure/azure-stream-analytics/config.yml
@@ -0,0 +1,40 @@
+id: eae1779f-9d4c-4996-ac13-a6c7d7f73d15
+slug: azure-stream-analytics
+title: Azure Stream Analytics
+description: |-
+ ## What is Azure Stream Analytics?
+
+ Azure Stream Analytics is a fully managed stream processing engine that is designed to analyze and process large volumes of streaming data with sub-millisecond latencies. Patterns and relationships can be identified in data that originates from a variety of input sources including applications, devices, sensors, clickstreams, and social media feeds.
+
+ ### New Relic Azure Stream Analytics quickstart features
+
+ A standard dashboard that tracks key indicators like failed requests, deserialization errors, late input events, resource utilization and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Stream Analytics with New Relic?
+
+ [New Relic Azure Stream Analytics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Stream Analytics via different metrics including failed requests, deserialization errors, late input events, resource utilization and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Stream Analytics is critical to tracking the performance through key metrics. Install the New Relic Azure Stream Analytics monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Stream Analytics service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Stream Analytics installation docs
+ description: |
+ Monitor Azure Stream Analytics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-stream-analytics-monitoring-integration/
+keywords:
+ - azure
+ - stream Analytics
+ - product partnerships
+dashboards:
+ - azure-stream-analytics
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-stream-analytics/logo.png b/quickstarts/azure/azure-stream-analytics/logo.png
new file mode 100644
index 0000000000..750d0deb1d
Binary files /dev/null and b/quickstarts/azure/azure-stream-analytics/logo.png differ
diff --git a/quickstarts/azure/azure-synapse-analytics/config.yml b/quickstarts/azure/azure-synapse-analytics/config.yml
new file mode 100644
index 0000000000..b284e4eb93
--- /dev/null
+++ b/quickstarts/azure/azure-synapse-analytics/config.yml
@@ -0,0 +1,40 @@
+id: 05729ec9-a69b-4ffa-91ee-3a34c1a2b10c
+slug: azure-synapse-analytics
+title: Azure Synapse Analytics
+description: |-
+ ## What is Azure Synapse Analytics?
+
+ Azure Synapse Analytics is an enterprise analytics service that accelerates time to insight across data warehouses and big data systems.
+
+ ### New Relic Azure Synapse Analytics quickstart features
+
+ A standard dashboard that tracks key indicators like builtin sql pool data processed bytes, total sql streaming conversion errors, integration link processing latency in seconds, sql streaming resource utilization and more. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Synapse Analytics with New Relic?
+
+ [New Relic Azure Synapse Analytics](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Synapse Analytics via different metrics including account builtin sql pool data processed bytes, total sql streaming conversion errors, integration link processing latency in seconds, sql streaming resource utilization and more.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Synapse Analytics is critical to tracking the performance through key metrics. Install the New Relic Azure Synapse Analytics monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Synapse Analytics service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Synapse Analytics installation docs.
+ description: |
+ Monitor Azure Synapse Analytics by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-synapse-analytics-monitoring-integration/
+keywords:
+ - azure
+ - synapse analytics
+ - product partnerships
+dashboards:
+ - azure-synapse-analytics
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-synapse-analytics/logo.png b/quickstarts/azure/azure-synapse-analytics/logo.png
new file mode 100644
index 0000000000..6814266ea3
Binary files /dev/null and b/quickstarts/azure/azure-synapse-analytics/logo.png differ
diff --git a/quickstarts/azure/azure-time-series-insights/config.yml b/quickstarts/azure/azure-time-series-insights/config.yml
new file mode 100644
index 0000000000..d989d54fa7
--- /dev/null
+++ b/quickstarts/azure/azure-time-series-insights/config.yml
@@ -0,0 +1,41 @@
+id: 65fd54e5-d724-4834-878b-8e0ea9c9cd8a
+slug: azure-time-series-insights
+title: Azure Time Series Insights
+description: |-
+ ## What is Azure Time Series Insights?
+
+ Azure Time Series Insights are the containers that hold the data ingested by the service. Each environment has a unique set of Time Series Insight features, such as retention policies, data access policies and query APIs.
+
+ ### New Relic Azure Time Series Insights quickstart features
+
+ A standard dashboard that tracks key indicators like ingress storage, ingress received bytes, ingress received messages and warm storage used properties. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Time Series Insights with New Relic?
+
+ [New Relic Azure Time Series Insights](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Time Series Insights via different metrics including ingress storage, ingress received bytes, ingress received messages and warm storage used properties.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insight.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Time Series Insights Cloud is a fully visualization service that makes it easy to explore and analyze via key metrics. Install the New Relic Azure Time Series Insight monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Time Series Insights service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Time Series insights installation docs
+ description: |
+ Monitor Azure Time Series Insights by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-time-series-insights-monitoring-integration/
+keywords:
+ - azure
+ - time series insight
+ - time series insights
+ - product partnerships
+dashboards:
+ - azure-time-series-insights
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-time-series-insights/logo.png b/quickstarts/azure/azure-time-series-insights/logo.png
new file mode 100644
index 0000000000..b1a066d4d9
Binary files /dev/null and b/quickstarts/azure/azure-time-series-insights/logo.png differ
diff --git a/quickstarts/azure/azure-traffic-manager/config.yml b/quickstarts/azure/azure-traffic-manager/config.yml
new file mode 100644
index 0000000000..4f4e3f1304
--- /dev/null
+++ b/quickstarts/azure/azure-traffic-manager/config.yml
@@ -0,0 +1,40 @@
+id: 867d591f-5401-4f59-9901-b206747fcc9b
+slug: azure-traffic-manager
+description: |-
+ ## What is Azure Traffic Manager?
+
+ Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions. Traffic Manager also provides your public endpoints with high availability and quick responsiveness.
+
+ ### New Relic Azure Traffic Manager quickstart features
+
+ A standard dashboard that tracks key indicators like probe agent current endpoint state by profile resourceId and Qps by endpoint. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Traffic Manager with New Relic?
+
+ [New Relic Azure Traffic Manager](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Traffic Manager via different metrics including probe agent current endpoint state by profile resourceId and Qps by endpoint.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Traffic Manager is critical to track the performance through key metrics. Download New Relic Azure Traffic Manager monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Traffic Manager service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Traffic Manager
+documentation:
+ - name: Azure Traffic Manager installation docs
+ description: |
+ Monitor Azure Traffic Manager by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-traffic-manager-monitoring-integration/
+keywords:
+ - azure
+ - traffic manager
+ - product partnerships
+dashboards:
+ - azure-traffic-manager
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-traffic-manager/logo.png b/quickstarts/azure/azure-traffic-manager/logo.png
new file mode 100644
index 0000000000..d7f1e4daa9
Binary files /dev/null and b/quickstarts/azure/azure-traffic-manager/logo.png differ
diff --git a/quickstarts/azure/azure-translator/config.yml b/quickstarts/azure/azure-translator/config.yml
new file mode 100644
index 0000000000..a53f71abd4
--- /dev/null
+++ b/quickstarts/azure/azure-translator/config.yml
@@ -0,0 +1,41 @@
+id: 5a0108de-2235-4d26-a6d6-a61e99cb1adf
+slug: azure-translator
+description: |-
+ ## What is Azure Translator?
+
+ Azure Translator is a cloud-based machine translation service you can use to translate text and documents with a simple REST API call.
+
+ ### New Relic Azure Translator quickstart features
+
+ A standard dashboard that tracks key indicators like total calls, total errors, Text trained characters, Successful calls and sucess rate. It runs custom queries and visualizes the data immediately.
+
+ ### Why monitor Azure Translator with New Relic?
+
+ [New Relic Azure Translator](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Translator via different metrics including total calls, total errors, Text trained characters, Successful calls and sucess rate.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Translator is critical to track the performance through key metrics. Download New Relic Azure Translator monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Translator.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+title: Azure Translator
+documentation:
+ - name: Azure Translator installation docs.
+ description: |
+ Monitor Azure Translator by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-cognitive-services-monitoring-integration/
+keywords:
+ - azure
+ - cognitive services
+ - translator
+ - product partnerships
+dashboards:
+ - azure-translator
+dataSourceIds:
+ - azure-monitor
\ No newline at end of file
diff --git a/quickstarts/azure/azure-translator/logo.png b/quickstarts/azure/azure-translator/logo.png
new file mode 100644
index 0000000000..cc06b080dc
Binary files /dev/null and b/quickstarts/azure/azure-translator/logo.png differ
diff --git a/quickstarts/azure/azure-vms/config.yml b/quickstarts/azure/azure-vms/config.yml
index 4277897575..81a138ad10 100644
--- a/quickstarts/azure/azure-vms/config.yml
+++ b/quickstarts/azure/azure-vms/config.yml
@@ -33,3 +33,5 @@ installPlans:
- azure-infrastructure-monitoring
dataSourceIds:
- microsoft-azure
+dashboards:
+ - azure-virtual-machines
diff --git a/quickstarts/azure/azure-web-apps/config.yml b/quickstarts/azure/azure-web-apps/config.yml
new file mode 100644
index 0000000000..0aefa1ed7c
--- /dev/null
+++ b/quickstarts/azure/azure-web-apps/config.yml
@@ -0,0 +1,42 @@
+id: 3f712d95-7823-4ce1-9bae-a3d82b615136
+slug: azure-web-apps
+title: Azure Web Apps
+description: |-
+ ## What is Azure Web Apps?
+
+ Azure Web Apps is an HTTP-based service for hosting web applications, REST APIs, and mobile back ends. You can develop in your favorite language, be it .NET, .NET Core, Java, Ruby, Node.js, PHP, or Python. Applications run and scale with ease on both Windows and Linux-based environments.
+
+ ### New Relic Azure Web Apps quickstart features
+
+ A standard dashboard that tracks key indicators like app connections, HTTP response time, bytes sent and bytes received. It runs custom queries and visualizes the data immediately.
+
+
+ ### Why monitor Azure Web Apps with New Relic?
+
+ [New Relic Azure Web Apps](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration/) monitoring quickstart empowers you to track the performance of Azure Web Apps via different metrics including app connections, HTTP response time, bytes sent and bytes received.
+
+ Our integration features a standard dashboard that provides interactive visualizations to explore your data, understand context, and get valuable insights.
+
+ Start ingesting your Azure data today and get immediate access to our visualization dashboards so you can optimize your Azure service.
+summary: |-
+ Monitoring Azure Web Apps is critical to track the performance of the application through key metrics. Download New Relic Azure Web Apps monitoring quickstart to get a pre-built dashboard tailored to monitor your Azure Web Apps service.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - New Relic Partner
+documentation:
+ - name: Azure Web Apps installation docs
+ description: |
+ Monitor Azure Web Apps by connecting Azure to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/azure-integrations-list/azure-web-apps-monitoring-integration/
+keywords:
+ - azure
+ - web app
+ - web apps
+ - product partnerships
+dashboards:
+ - azure-web-apps
+dataSourceIds:
+ - azure-monitor
diff --git a/quickstarts/azure/azure-web-apps/logo.png b/quickstarts/azure/azure-web-apps/logo.png
new file mode 100644
index 0000000000..4c7913454b
Binary files /dev/null and b/quickstarts/azure/azure-web-apps/logo.png differ
diff --git a/quickstarts/battlesnake/config.yml b/quickstarts/battlesnake/config.yml
index 77a936ad61..087f8cb7de 100644
--- a/quickstarts/battlesnake/config.yml
+++ b/quickstarts/battlesnake/config.yml
@@ -34,3 +34,4 @@ dashboards:
- battlesnake-game-tracking
- battlesnake-performance
- battlesnake-server-status
+
diff --git a/quickstarts/blazemeter/config.yml b/quickstarts/blazemeter/config.yml
new file mode 100644
index 0000000000..8a7f407430
--- /dev/null
+++ b/quickstarts/blazemeter/config.yml
@@ -0,0 +1,71 @@
+id: 0f6e2b85-ea73-4780-84eb-34e1e3675b33
+# Sets the URL name of the quickstart on public I/O (required)
+slug: blazemeter
+
+# Displayed in the UI (required)
+title: BlazeMeter
+
+# Long-form description of the quickstart (required)
+description: |
+ ## Quickstart for BlazeMeter API Test Monitoring
+ The BlazeMeter Continuous Testing Platform is a unified, end-to-end, next-generation software test automation platform built for both Agile and COE teams.
+ By connecting New Relic with BlazeMeter API Monitoring, you can collect metrics from your API tests and transform them into actionable insights about your applications in New Relic
+
+ This quickstart allows users to monitor BlazeMeter API tests inside New Relic and observe test results in the context of instrumented applications.
+ The BlazeMeter quickstart includes:
+ ## a dashboard
+ where users can easily monitor:
+ - Test Result Counts for Past Week
+ - Assertion Pass/Fail Counts by Day for Past Week
+ - Response Times Histogram Over Past Week
+ - Average/90th/95th/99th Percentile Response Times Over Past Day
+ - Response Status Codes for Past Day
+ - Test Run Summary
+ ## alert conditions
+ where users are notified on:
+ - Test Error Rate
+ - 90th Percentile Latency
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ This quickstart allows users to monitor BlazeMeter tests inside New Relic and observe API test results in the context of instrumented applications.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Munwar Mohammed
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - blazemeter
+ - api
+ - performance
+ - load
+ - stress
+ - functional
+ - testing web application
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - blazemeter
+
+alertPolicies:
+ - blazemeter
+
+dataSourceIds:
+ - blazemeter
+
+# Documentation references
+documentation:
+ - name: BlazeMeter New Relic Integration
+ url: https://guide.blazemeter.com/hc/en-us/articles/13326704491153-New-Relic-Insights-Integration
+ description: Information on how to connect New Relic with BlazeMeter API Monitoring and send metrics from API tests to New Relic
+ - name: Learn more about the BlazeMeter Continuous Testing Platform
+ url: https://www.blazemeter.com/
+ description: Information on how BlazeMeter can be utilized to shift testing left or right with enterprise-level GUI performance testing, API functional testing, API monitoring, and reporting
+
+# Content / Design
+icon: logo.png
+website: https://www.blazemeter.com/
\ No newline at end of file
diff --git a/quickstarts/blazemeter/logo.png b/quickstarts/blazemeter/logo.png
new file mode 100644
index 0000000000..9ccbcfcb24
Binary files /dev/null and b/quickstarts/blazemeter/logo.png differ
diff --git a/quickstarts/botolytics/config.yml b/quickstarts/botolytics/config.yml
new file mode 100644
index 0000000000..ed3970a51a
--- /dev/null
+++ b/quickstarts/botolytics/config.yml
@@ -0,0 +1,33 @@
+id: 28b3ade7-a395-4cdd-952a-0e260d6a2494
+
+slug: botolytics
+title: Botolytics
+description: |
+ ## Botolytics
+ On every well used website there are not only real users, but also many many bots. Those can be legitimate bots, like search bots, synthetic checks or other automated calls to your service. But even legitimate bots can distort your service's vitals in a way that they no longer represent your real customer's experience.
+ Being able to distinguish real traffic from bot traffic is crucial in various cases, for example when examining a marketing campaign or when analyzing your services vitals or service levels.
+ ### How to use Botolytics
+ This Quickstart works on top of your APM data. We have included the most common bots, but you can and should customize the dashboard with bots specific to your service.
+summary: |
+ Popular websites have real users and various bots. Legitimate bots, like search or checks, can distort data. Distinguishing real traffic from bots matters. It's crucial for marketing analysis and service insights. The Botolytic Dashboard helps analyze bot traffic.
+icon: logo.png
+level: Verified
+authors:
+ - Heiko Specht (New Relic)
+ - Linda Weimannn (New Relic)
+keywords:
+ - marketing
+ - bot
+ - traffic analysis
+ - apm
+
+documentation:
+ - name: Installation docs
+ url: https://docs.newrelic.com/introduction-apm
+ description: Add APM data to use this Quickstart
+
+dashboards:
+ - botolytics
+
+dataSourceIds:
+ - guided-install
\ No newline at end of file
diff --git a/quickstarts/botolytics/logo.png b/quickstarts/botolytics/logo.png
new file mode 100644
index 0000000000..dce9174686
Binary files /dev/null and b/quickstarts/botolytics/logo.png differ
diff --git a/quickstarts/browser/config.yml b/quickstarts/browser/config.yml
index 9dbf08cf88..aa13aed363 100644
--- a/quickstarts/browser/config.yml
+++ b/quickstarts/browser/config.yml
@@ -22,6 +22,7 @@ authors:
- New Relic
- Darren Doyle
- Alex York
+ - Kinsey
icon: logo.svg
documentation:
- name: Browser
@@ -43,3 +44,5 @@ dashboards:
- browser-pages-dashboard
- javascript-errors
- traffic-analysis
+alertPolicies:
+ - browser
\ No newline at end of file
diff --git a/quickstarts/chromadb/config.yml b/quickstarts/chromadb/config.yml
new file mode 100644
index 0000000000..dff93c8611
--- /dev/null
+++ b/quickstarts/chromadb/config.yml
@@ -0,0 +1,43 @@
+id: 3d4077eb-83ed-4ba5-9ee5-5f002c880e6d
+slug: chromadb
+description: |
+ ## Why should you monitor your usage of ChromaDB?
+ Monitor your vector searches on ChromaDB to get visibility on what you send to ChromaDB, responses retrieved from ChromaDB, latency, usage and errors.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic ChromaDB quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: ChromaDB
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - chromadb
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/chromadb/logo.png b/quickstarts/chromadb/logo.png
new file mode 100644
index 0000000000..ae25df89d6
Binary files /dev/null and b/quickstarts/chromadb/logo.png differ
diff --git a/quickstarts/circleci/config.yml b/quickstarts/circleci/config.yml
index 95b0dc1741..f390d97878 100644
--- a/quickstarts/circleci/config.yml
+++ b/quickstarts/circleci/config.yml
@@ -38,7 +38,6 @@ keywords:
- circleci
- circle
- cicd
- - featured
- logs
- NR1_addData
- NR1_sys
diff --git a/quickstarts/clickhouse/config.yml b/quickstarts/clickhouse/config.yml
new file mode 100644
index 0000000000..2476023346
--- /dev/null
+++ b/quickstarts/clickhouse/config.yml
@@ -0,0 +1,49 @@
+id: d85eeb08-8012-4d08-adba-84aace2f4688
+slug: clickhouse
+description: |
+ ## Why should you monitor your usage of ClickHouse?
+
+ Monitor your vector searches on ClickHouse to get visibility on what you send to ClickHouse, responses retrieved from ClickHouse, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic ClickHouse quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: ClickHouse
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - clickhouse
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/clickhouse/logo.png b/quickstarts/clickhouse/logo.png
new file mode 100644
index 0000000000..ba034c89fc
Binary files /dev/null and b/quickstarts/clickhouse/logo.png differ
diff --git a/quickstarts/cloudfoundry/config.yml b/quickstarts/cloudfoundry/config.yml
index 08e1812adb..d481aaba94 100644
--- a/quickstarts/cloudfoundry/config.yml
+++ b/quickstarts/cloudfoundry/config.yml
@@ -17,7 +17,5 @@ keywords:
- containers
- kubernetes
- k8s
-installPlans:
- - third-party-cloudfoundry
dataSourceIds:
- - cloudfoundry
+ - vmware-tanzu
diff --git a/quickstarts/codestream/codestream/config.yml b/quickstarts/codestream/codestream/config.yml
deleted file mode 100644
index fe7df0e9d5..0000000000
--- a/quickstarts/codestream/codestream/config.yml
+++ /dev/null
@@ -1,43 +0,0 @@
-id: 29bd9a4a-1c19-4219-9694-0942f6411ce7
-slug: codestream
-
-description: |
- ## What is New Relic CodeStream?
-
- New Relic CodeStream helps dev teams discuss, review, and understand code.
-
- ### Get started!
-
- New Relic CodeStream supercharges development workflows by putting collaboration tools in your IDE. It supports pull requests from GitHub, BitBucket and GitLab, issue management from Jira, Trello, Asana and 9 others, observability from New Relic One and Pixie, and provides code discussion that ties it all together, integrated with Slack, MS Teams, email, and in-editor notifications.
-
- With the New Relic One integration:
- - Click from Errors Inbox right to the code that caused it in your IDE
- - Step through stack-traces and method calls, navigating to specific lines of code
- - Add production logging on the fly, and see the results, without leaving your editor
- - Discover recent errors assigned to you, assign errors, and update their status
- - View telemetry such as error rate, throughput and executions/sec for a given method
-
- Install the extension for [VS Code](https://marketplace.visualstudio.com/items?itemName=CodeStream.codestream), [Visual Studio](https://marketplace.visualstudio.com/items?itemName=CodeStream.codestream-vs), and all [JetBrains](https://plugins.jetbrains.com/plugin/12206-codestream-github-gitlab-bitbucket-prs-and-code-review) editors.
-
- ### More info
-
- Check out the [documentation](https://docs.newrelic.com/docs/codestream/)
-summary: |
- View production telemetry and troubleshoot errors from your IDE
-icon: logo.svg
-level: New Relic
-authors:
- - New Relic
-title: CodeStream
-documentation:
- - name: Installation Docs
- description: View production telemetry and troubleshoot errors from your IDE
- url: >-
- https://docs.newrelic.com/docs/codestream/start-here/new-relic-codestream-quick-start/
- - name: New Relic CodeStream Demo
- description: See New Relic CodeStream in action
- url: https://codestream.com/demo
-website: https://codestream.com
-# Keywords for filtering / searching criteria in the UI
-keywords:
- - featured
diff --git a/quickstarts/codestream/codestream/logo.svg b/quickstarts/codestream/codestream/logo.svg
deleted file mode 100644
index 2de2b10dc1..0000000000
--- a/quickstarts/codestream/codestream/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/codestream/github-cs/config.yml b/quickstarts/codestream/github-cs/config.yml
deleted file mode 100644
index 87ac5df371..0000000000
--- a/quickstarts/codestream/github-cs/config.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-id: 364b0de9-f9b3-4ce2-a084-e01ccc328c43
-slug: github-for-codestream
-title: GitHub for CodeStream
-description: |
- GitHub is a code hosting platform for version control and collaboration. It lets developers and others work together on projects from anywhere.
-
- With CodeStream you can create, review, and merge GitHub PRs without ever leaving your IDE. All with full source-tree and full file access, your favorite keybindings, and all the code intelligence embedded in your development environment.
-
- [Check out our documentation](https://docs.newrelic.com/docs/codestream/start-here/install-codestream/#connect-tools) to learn how to connect New Relic CodeStream to GitHub.
-summary: |
- Connect New Relic CodeStream to GitHub.
-level: New Relic
-authors:
- - New Relic
-keywords:
- - codestream
- - github
- - pull request
- - errors inbox
-installPlans:
- - third-party-github-for-codestream
-dataSourceIds:
- - github-for-codestream
-documentation:
- - name: Installation Docs
- url: https://docs.newrelic.com/docs/codestream/start-here/install-codestream/#connect-tools
- description: How to set up GitHub with Codestream
-icon: logo.png
-website: https://www.newrelic.com
diff --git a/quickstarts/codestream/github-cs/logo.png b/quickstarts/codestream/github-cs/logo.png
deleted file mode 100644
index 353bb4e581..0000000000
Binary files a/quickstarts/codestream/github-cs/logo.png and /dev/null differ
diff --git a/quickstarts/codestream/slack-cs/config.yml b/quickstarts/codestream/slack-cs/config.yml
deleted file mode 100644
index b9fcb28950..0000000000
--- a/quickstarts/codestream/slack-cs/config.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-id: 5837b456-5f5b-4539-8b71-77193298d253
-slug: slack-for-codestream
-title: Slack for CodeStream
-description: |
- Slack is a messaging app for business that connects people to the information they need.
-
- When you post a comment, issue, or feedback request, your teammates are notified via the activity feed, and potentially via email. Sometimes, though, you might want to share to Slack as well. This allows you to reach people who haven’t yet joined CodeStream, or maybe don’t spend a lot of time in their IDE.
-
- [Check out our documentation](https://docs.newrelic.com/docs/codestream/codestream-integrations/slack-integration) to connect New Relic CodeStream to your team's Slack channel.
-summary: |
- Connect New Relic CodeStream to your team's Slack channel.
-level: New Relic
-authors:
- - New Relic
-keywords:
- - slack
- - codestream
- - ide
- - errors inbox
-installPlans:
- - third-party-slack-for-codestream
-dataSourceIds:
- - slack-for-codestream
-documentation:
- - name: Slack Integration Docs
- url: https://docs.newrelic.com/docs/codestream/codestream-integrations/slack-integration
- description: Documentation about the New Relic - Slack CodeStream integration
-icon: logo.png
-website: https://www.newrelic.com
diff --git a/quickstarts/codestream/slack-cs/logo.png b/quickstarts/codestream/slack-cs/logo.png
deleted file mode 100644
index c51a425f93..0000000000
Binary files a/quickstarts/codestream/slack-cs/logo.png and /dev/null differ
diff --git a/quickstarts/codestream/teams-cs/config.yml b/quickstarts/codestream/teams-cs/config.yml
deleted file mode 100644
index 7a48899a20..0000000000
--- a/quickstarts/codestream/teams-cs/config.yml
+++ /dev/null
@@ -1,28 +0,0 @@
-id: c1a50e3c-f81a-4af2-b2ab-878076c9cc82
-slug: microsoft-teams-for-codestream
-title: Microsoft Teams for CodeStream
-description: |
- Microsoft Teams helps bring people together so that they can get things done.
-
- When you post a codemark your teammates will get notified via the activity feed, and potentially via email. Sometimes, though, you might want to share to Microsoft Teams as well. This would allow you to reach people who haven’t yet joined CodeStream, or maybe don’t spend a lot of time in their IDE.
-
- [Check out our documentation](https://docs.newrelic.com/docs/codestream/codestream-integrations/msteams-integration/) to learn how to connect New Relic CodeStream to your Microsoft Teams channel.
-summary: |
- Connect New Relic CodeStream to your Microsoft Teams channel.
-level: Community
-authors:
- - New Relic
-keywords:
- - codestream
- - microsoft
- - teams
-installPlans:
- - third-party-microsoft-teams-for-codestream
-dataSourceIds:
- - microsoft-teams-for-codestream
-documentation:
- - name: Teams for CodeStream integration docs
- url: https://docs.newrelic.com/docs/codestream/codestream-integrations/msteams-integration/
- description: Guide to help you get set up using New Relic's Microsoft Teams for CodeStream.
-icon: logo.png
-website: https://www.newrelic.com
diff --git a/quickstarts/codestream/teams-cs/logo.png b/quickstarts/codestream/teams-cs/logo.png
deleted file mode 100644
index 1f4ba05f91..0000000000
Binary files a/quickstarts/codestream/teams-cs/logo.png and /dev/null differ
diff --git a/quickstarts/contentsquare/config.yml b/quickstarts/contentsquare/config.yml
index 50c51a6eee..7de985aec3 100644
--- a/quickstarts/contentsquare/config.yml
+++ b/quickstarts/contentsquare/config.yml
@@ -6,12 +6,17 @@ summary: |
platform that collects and quantifies user behavior across all your digital
properties showing you what users like, what they don’t like, where they
struggle, and why they leave.
+description: |
+ ## Contentsquare performance monitoring
+
Contentsquare surfaces opportunities to improve your customer experience
automatically and easily so you can increase your conversion rates, improve
customer loyalty, reduce costs and drive revenue.
-description: |
+
Get more value from your investments in Contentsquare and New Relic by seeing
how performance issues truly affect your customers’ digital experience.
+
+ ### What's included?
Through this integration, access Contentsquare Session Replay links directly
within New Relic. With this, Contentsquare shows you exactly what a user was
diff --git a/quickstarts/conviva/config.yml b/quickstarts/conviva/config.yml
new file mode 100644
index 0000000000..371389eee3
--- /dev/null
+++ b/quickstarts/conviva/config.yml
@@ -0,0 +1,79 @@
+id: 5fd7561f-2128-4270-9d51-f731819c7d50
+# Sets the URL name of the quickstart on public I/O (required)
+slug: conviva
+
+# Displayed in the UI (required)
+title: Conviva
+
+# Long-form description of the quickstart (required)
+description: |
+ ## What is Conviva?
+
+ [Conviva](https://www.conviva.com/) is a real-time analytics platform that
+ makes streaming data actionable.
+
+ ## What is the Conviva Integration?
+
+ The Conviva integration is a New Relic Infrastructure
+ [on-host integration](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations/)
+ that uses the [Conviva v3 Metrics API](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta)
+ to pull metrics from Conviva and push them into New Relic as dimensional
+ metrics.
+
+ The Conviva integration supports the following Conviva v3 Metrics API
+ concepts.
+
+ * [Single metrics and metric groups](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#single-metrics-and-metric-groups)
+ * [Multiple singular metrics](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#retrieving-multiple-singular-metrics-in-a-request)
+ * [Dimensions](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#dimensions)
+ * [Time ranges](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#time-range)
+ * [Interval granularity](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#interval-granularity)
+ * [Filtering](https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta#filtering-by-dimensions)
+
+ ## Getting Started
+
+ This quickstart is designed to help customers install and use the Conviva
+ integration to collect and work with Conviva metrics.
+
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ A New Relic quickstart designed to help customers install and use the Conviva
+ integration to collect and work with Conviva metrics.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Scott DeWitt
+ - Chris McCarthy
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - conviva
+ - video
+ - streaming
+ - NRI
+ - integration
+ - newrelic
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - conviva
+
+# Documentation references
+documentation:
+ - name: Installation
+ url: https://github.com/newrelic/nri-conviva#installation
+ description: Installing the Conviva integration
+ - name: Github Repository
+ url: https://github.com/newrelic/nri-conviva
+ description: The Conviva integration repository
+ - name: Conviva Metrics V3 API User Guide
+ url: https://developer.conviva.com/docs/metrics-api-v3/3e38d9ead39fc-metrics-v3-api-user-guide-beta
+ description: The Conviva Metrics V3 API documentation
+
+# Content / Design
+icon: logo.svg
+website: https://www.conviva.com
diff --git a/quickstarts/conviva/logo.svg b/quickstarts/conviva/logo.svg
new file mode 100644
index 0000000000..911b6d572e
--- /dev/null
+++ b/quickstarts/conviva/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/dapr/config.yml b/quickstarts/dapr/config.yml
new file mode 100644
index 0000000000..14282550be
--- /dev/null
+++ b/quickstarts/dapr/config.yml
@@ -0,0 +1,28 @@
+id: 33129991-fb5d-4251-bca2-d0b63176b7c2
+slug: dapr
+title: Dapr
+description: |
+ The Dapr quickstart allows you to add meaningful dashboards to New Relic that highlight key aspects of the Dapr platform.
+
+ A guide on how to set-up New Relic for distributed tracing with Dapr can be found [here](https://docs.dapr.io/operations/monitoring/tracing/newrelic/).
+summary: |
+ Dapr is a portable, event-driven runtime that makes it easy for any developer to build resilient, stateless and stateful applications that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
+level: Community
+authors:
+ - Harry Kimpel
+keywords:
+ - apm
+ - dapr
+dashboards:
+ - dapr-metrics
+ - dapr-system-services
+installPlans:
+ - third-party-dapr
+dataSourceIds:
+ - dapr
+documentation:
+ - name: Installation docs
+ url: https://docs.dapr.io/operations/monitoring/tracing/newrelic/
+ description: How-To Set-up New Relic for distributed tracing.
+icon: logo.svg
+website: https://www.dapr.io
diff --git a/quickstarts/dapr/logo.svg b/quickstarts/dapr/logo.svg
new file mode 100644
index 0000000000..716c3e4fe4
--- /dev/null
+++ b/quickstarts/dapr/logo.svg
@@ -0,0 +1,15 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/datazoom/logo.png b/quickstarts/datazoom/logo.png
index eb5dd69d83..7e620d36d5 100644
Binary files a/quickstarts/datazoom/logo.png and b/quickstarts/datazoom/logo.png differ
diff --git a/quickstarts/deeplake/config.yml b/quickstarts/deeplake/config.yml
new file mode 100644
index 0000000000..1dadb568d0
--- /dev/null
+++ b/quickstarts/deeplake/config.yml
@@ -0,0 +1,50 @@
+id: 094e1a4b-4798-45a2-95d6-1b61fee9b088
+slug: deeplake
+description: |
+ ## Why should you monitor your usage of Deep Lake?
+
+ Monitor your vector searches on Deep Lake to get visibility on what you send to Deep Lake, responses retrieved from Deep Lake, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Deep Lake quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Deep Lake
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - deep lake
+ - vector search
+ - vectordb
+ - vector db
+ - ai
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/deeplake/logo.png b/quickstarts/deeplake/logo.png
new file mode 100644
index 0000000000..e43b65ffcb
Binary files /dev/null and b/quickstarts/deeplake/logo.png differ
diff --git a/quickstarts/delphix/config.yml b/quickstarts/delphix/config.yml
index f7f9bad471..d7b9b391a1 100644
--- a/quickstarts/delphix/config.yml
+++ b/quickstarts/delphix/config.yml
@@ -18,7 +18,7 @@ description: |
The quickstart contains a sample Delphix Platform Dashboard and Storage Utilization Alert to help users get started.
- Populating data for dashboards, alerts, and workflows requires the [Delphix Integration](https://github.com/delphix/dct-newrelic-integration) and [Delphix Data Control Tower](https://docs.delphix.com/dct).
+ Populating data for dashboards, alerts, and workflows requires the [Delphix Integration](https://github.com/delphix/dct-newrelic-integration) and [Delphix Data Control Tower](https://dct.delphix.com/docs/latest).
icon: logo.svg
website: https://www.delphix.com
summary: |
diff --git a/quickstarts/docarray-hnswsearch/config.yml b/quickstarts/docarray-hnswsearch/config.yml
new file mode 100644
index 0000000000..77facdc52a
--- /dev/null
+++ b/quickstarts/docarray-hnswsearch/config.yml
@@ -0,0 +1,54 @@
+id: 9127f544-8f32-4250-9d2f-2b4be09e281d
+slug: docarray-hnswsearch
+description: |
+ ## Why should you monitor your usage of DocArray HnswSearch?
+ Monitor your vector searches with DocArray HnswSearch to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of DocArray HnswSearch
+ Track the behavior of DocArray HnswSearch. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of DocArray HnswSearch:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into DocArray HnswSearch's performance and identify areas of improvement.
+
+ ## Comprehensive monitoring quickstart for DocArray HnswSearch
+ DocArray HnswSearch quickstart provides metrics including Identify popular queries, sources, and content.
+
+ ## What’s included in this quickstart?
+ New Relic DocArray HnswSearch monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your DocArray HnswSearch. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic DocArray HnswSearch quickstart
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: DocArray HnswSearch
+documentation:
+ - name: DocArray HnswSearch integration documentation
+ description: |
+ Implement monitoring and instrumentation for DocArray HnswSearch, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - DocArray
+ - HnswSearch
+ - text search
+ - image search
+ - video search
+ - AI
+ - machine learning
+ - open source
+ - Hnsw Search
+ - Doc Array
+ - vector search
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
diff --git a/quickstarts/docarray-hnswsearch/logo.svg b/quickstarts/docarray-hnswsearch/logo.svg
new file mode 100644
index 0000000000..db2420c667
--- /dev/null
+++ b/quickstarts/docarray-hnswsearch/logo.svg
@@ -0,0 +1,20 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/docarray-inmemorysearch/config.yml b/quickstarts/docarray-inmemorysearch/config.yml
new file mode 100644
index 0000000000..1c4d20dfac
--- /dev/null
+++ b/quickstarts/docarray-inmemorysearch/config.yml
@@ -0,0 +1,57 @@
+id: c264449d-e7a1-4497-9b73-df1bdfe79f82
+
+slug: docarray-inmemorysearch
+description: |
+ ## Why should you monitor your usage of DocArray InMemorySearch?
+ Monitor your vector searches with DocArray InMemorySearch to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of DocArray InMemorySearch
+ Track the behavior of DocArray InMemorySearch. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of DocArray InMemorySearch
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into DocArray InMemorySearch's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+ New Relic DocArray InMemorySearch monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of DocArray InMemorySearch. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your DocArray InMemorySearch performance and quality with New Relic DocArray InMemorySearch quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: DocArray InMemorySearch
+documentation:
+ - name: DocArray InMemorySearch integration documentation
+ description: |
+ Implement monitoring and instrumentation for your DocArray InMemorySearch, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - docarray inmemorysearch
+ - doc array
+ - vector search
+ - in memory search
+ - in-memory search
+ - in memory
+ - document search
+ - multimodal search
+ - open source
+ - python
+ - machine learning
+ - artificial intelligence
+ - AI
+ - ML
+ - NLP
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/docarray-inmemorysearch/logo.svg b/quickstarts/docarray-inmemorysearch/logo.svg
new file mode 100644
index 0000000000..a3a5c8ae39
--- /dev/null
+++ b/quickstarts/docarray-inmemorysearch/logo.svg
@@ -0,0 +1,20 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/docker-otel/config.yml b/quickstarts/docker-otel/config.yml
new file mode 100644
index 0000000000..60138e63a4
--- /dev/null
+++ b/quickstarts/docker-otel/config.yml
@@ -0,0 +1,40 @@
+id: 67298fce-4bbe-40d0-8cda-b80aad183794
+slug: docker-otel
+title: Docker (OpenTelemetry)
+summary: |
+ Monitoring docker is essential to enable your team deliver high-quality software that yields a positive customer experience. Install New Relic Docker for Open Telemetry quickstart to proactively instrument Docker with the Dockerstats receiver.
+description: |
+ ## How to monitor Docker with New Relic?
+
+ Dockerstats OpenTelemetry receiver collects metrics from your running Docker containers on the host where OpenTelemetry Collector is installed.
+ The collected metrics allow you to observe the usage of CPU, memory, network, and more.
+
+ A New Relic container entity will be created for each container, making it easy to explore, configure alerts and compare metrics for all of your containers in one place.
+
+ Our monitoring quickstart includes a pre-built dashboard that displays aggregated metrics from all of your containers, with the ability to filter the data to focus on specific workloads.
+
+ ### Why monitor Docker with New Relic?
+
+ New Relic's Docker for Open Telemetry quickstart empowers you to get 360° visibility for your apps, server infrastructure, and Dockerized containers all in one place. Monitoring Docker is critical to get instant performance metrics for containerized applications across your entire environment. It enables you to provide a consistent customer experience, regardless of changes to the underlying platforms, tools, languages, or frameworks.
+
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+dataSourceIds:
+ - docker-otel
+alertPolicies:
+ - docker-otel
+documentation:
+ - name: Docker (OpenTelemetry) installation docs
+ description: |
+ Docker is a set of Platform-as-a-Service (PaaS) products that use OS-level virtualization to deliver software in packages called containers.
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-docker/
+dashboards:
+ - docker-otel
+keywords:
+ - containers
+ - open telemetry
+ - docker
+ - infrastructure
+ - featured
diff --git a/quickstarts/docker-otel/logo.svg b/quickstarts/docker-otel/logo.svg
new file mode 100644
index 0000000000..de97544316
--- /dev/null
+++ b/quickstarts/docker-otel/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/dojo/config.yml b/quickstarts/dojo/config.yml
index 31c07c0d5b..2667a0cd37 100644
--- a/quickstarts/dojo/config.yml
+++ b/quickstarts/dojo/config.yml
@@ -33,8 +33,6 @@ documentation:
keywords:
- dojo
- browser monitoring
-installPlans:
- - dojo
dataSourceIds:
- dojo
dashboards:
diff --git a/quickstarts/dotnet/csharp/config.yml b/quickstarts/dotnet/csharp/config.yml
index 4209c87c40..7b9de6f9c2 100644
--- a/quickstarts/dotnet/csharp/config.yml
+++ b/quickstarts/dotnet/csharp/config.yml
@@ -3,29 +3,40 @@ slug: c-sharp
description: |
## C# performance monitoring
With our C# integration, you can find and address performance bottlenecks while operating in a live development environment. Monitor your app via our dashboard quickstarts and ensure you're delivering the best user experience.
-
- ### Common C# performance errors
+
+ ## Common C# performance errors
Here are the common C# performance errors that you can handle with New Relic integration:
- - Memory management: C# uses automatic memory management, which takes the burden of manual allocation from developers. However, C# can sometimes run into memory error thereby inhibiting its memory management performance. Our integration offers the best solution to fix that.
- - CPU usage: New Relic’s high CPU utilization alert is the key to monitoring CPU usage to prevent any potential error.
- - Garbage collection: Garbage Collector (GC) manages the allocation and release of memory for your application. When the memory is under distress, our C# integration will easily notify you via the memory usage alert.
- - High volume of requests: Getting a high volume of requests can affect your app’s response time and reduce user satisfaction. With Apdex score, you can track requests and measure user satisfaction.
- - JIT compiler: If JIT compiler fails to load, it may be due to an out-of-memory exception or internal limitation error. The pathway towards getting the insights you need is the New Relic C# integration.
+
+ **Memory management**: C# uses automatic memory management, which takes the burden of manual allocation from developers. However, C# can sometimes run into memory error thereby inhibiting its memory management performance. Our integration offers the best solution to fix that.
+
+ **CPU usage**: New Relic’s high CPU utilization alert is the key to monitoring CPU usage to prevent any potential error.
+
+ **Garbage collection**: Garbage Collector (GC) manages the allocation and release of memory for your application. When the memory is under distress, our C# integration will easily notify you via the memory usage alert.
+
+ **High volume of requests**: Getting a high volume of requests can affect your app’s response time and reduce user satisfaction. With Apdex score, you can track requests and measure user satisfaction.
+
+ **JIT compiler**: If JIT compiler fails to load, it may be due to an out-of-memory exception or internal limitation error. The pathway towards getting the insights you need is the New Relic C# integration.
+
### C# monitoring use cases
+
- Focus on the issues that affect your critical business transactions.
- - Gain knowledge on your system's behavior in advance and learn the whole story of performance errors, from beginning to end.
+ - Resolve problems quickly.
+ - Gain knowledge on your system's behavior in advance.
+ - Learn the whole story of performance errors, from beginning to end.
- Use traces to connect latency issues to errors, getting you to the root cause as quickly as possible.
- See the filename and line number from the C# stack trace so you never have to guess. To reduce noise, logically filter and aggregate C# exceptions.
- Scalable error monitoring without affecting production flow.
- Maintain low latency with fast throughput.
- - Get meaningful data about C# errors from your dashboard.
+ - Get meaningful data about C# errors from your dashboard.
+
+ ### End-to-end visibility into your C# operations
- ## End-to-end visibility into your C# operations
Our C# dashboard translates your ingested data into a map that lets you trace business transactions across your C# stack. See your performance errors in context and prioritize your most critical operations.
## What’s included in this quickstart?
+
New Relic's C# monitoring quickstart boasts instant full-stack observability out-of-the-box:
- Dashboards (Throughput, Error rate, Logs, Web transaction time, Apdex Score and more).
diff --git a/quickstarts/elastic-knn-search/config.yml b/quickstarts/elastic-knn-search/config.yml
new file mode 100644
index 0000000000..c2f8cf35d1
--- /dev/null
+++ b/quickstarts/elastic-knn-search/config.yml
@@ -0,0 +1,55 @@
+id: 9c5273f1-ddc0-4db4-8a31-41fe1ea320e3
+
+slug: elastic-knn-search
+description: |
+ ## Why should you monitor your usage of Elastic KNN Search?
+ Monitor your vector searches with Elastic KNN Search to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of Elastic KNN Search
+ Track the behavior of Elastic KNN Search. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of Elastic KNN Search
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into Elastic KNN Search's performance and identify areas of improvement.
+
+
+ ## What’s included in this quickstart?
+ New Relic Elastic KNN Search monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of Elastic KNN Search. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Elastic KNN Search's performance and quality with New Relic Elastic KNN Search quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Elastic KNN Search
+documentation:
+ - name: Elastic KNN Search integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Elastic KNN Search, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - elastic knn search
+ - k-nearest neighbors
+ - KNN
+ - vector search
+ - nearest neighbor search
+ - machine learning
+ - artificial intelligence
+ - AI
+ - ML
+ - data science
+ - big data
+ - elasticsearch
+ - elastic search
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/elastic-knn-search/logo.png b/quickstarts/elastic-knn-search/logo.png
new file mode 100644
index 0000000000..8980878308
Binary files /dev/null and b/quickstarts/elastic-knn-search/logo.png differ
diff --git a/quickstarts/elastic-vector-search/config.yml b/quickstarts/elastic-vector-search/config.yml
new file mode 100644
index 0000000000..a3b0a70a72
--- /dev/null
+++ b/quickstarts/elastic-vector-search/config.yml
@@ -0,0 +1,55 @@
+id: 3619a864-7d96-4a6a-9900-758c7e380ec7
+
+slug: elastic-vector-search
+description: |
+ ## Why should you monitor your usage of Elastic Vector Search?
+ Monitor your vector searches with Elastic Vector Search to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of Elastic Vector Search
+ Track the behavior of your Elastic Vector Search. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of Elastic Vector Search
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into Elastic Vector Search's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+ New Relic Elastic Vector Search monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Elastic Vector Search. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Elastic Vector Search's performance and quality with New Relic Elastic Vector Search quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Elastic Vector Search
+documentation:
+ - name: Elastic Vector Search integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Elastic Vector Search, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - elastic search
+ - elastic vector search
+ - vector search
+ - dense vector search
+ - sparse vector search
+ - distributed vector search
+ - real-time vector search
+ - elasticsearch
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+ - AI
+ - ML
+ - NLP
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/elastic-vector-search/logo.png b/quickstarts/elastic-vector-search/logo.png
new file mode 100644
index 0000000000..04dcd53fea
Binary files /dev/null and b/quickstarts/elastic-vector-search/logo.png differ
diff --git a/quickstarts/elixir/config.yml b/quickstarts/elixir/config.yml
index 2a64ea6a2a..93c1769e9c 100644
--- a/quickstarts/elixir/config.yml
+++ b/quickstarts/elixir/config.yml
@@ -22,10 +22,13 @@ keywords:
- apm
- elixir
- language agent
+
installPlans:
- setup-elixir-agent
+
dataSourceIds:
- elixir
+
documentation:
- name: Elixir installation docs
description: Popular open source programming language with automated features.
diff --git a/quickstarts/example-dashboard/example-dashboard.json b/quickstarts/example-dashboard/example-dashboard.json
index 019aca7119..56217a9f95 100644
--- a/quickstarts/example-dashboard/example-dashboard.json
+++ b/quickstarts/example-dashboard/example-dashboard.json
@@ -18,7 +18,7 @@
},
"title": " ",
"rawConfiguration": {
- "text": "![Image](https://s3.amazonaws.com/nr-cloud-adoption/CloudAdoption-Plan.png)\n"
+ "text": "![Image](https://raw.githubusercontent.com/newrelic/newrelic-quickstarts/bb8038eb251fb37c0e15f1f2ea930569f0eb1cb5/_template/quickstarts/example-quickstart/logo.svg)\n"
}
},
{
diff --git a/quickstarts/f5/config.yml b/quickstarts/f5/config.yml
index 1f1ec4e09c..3b91987a4e 100644
--- a/quickstarts/f5/config.yml
+++ b/quickstarts/f5/config.yml
@@ -1,34 +1,42 @@
id: 0da402d7-e8ef-4a97-8e3f-fc476a86a3c0
slug: f5
+title: F5
description: |
## What is F5?
- F5 is a family of software and hardware products designed around application availability, access control, and security.
+ F5 is a set of application delivery products that work together to ensure high availability, improved performance, application security, and access control.
## Get started!
Use New Relic's F5 BIG-IP integration to collect and send inventory and metrics from your F5 BIG-IP instance, where you can aggregate and visualize key performance metrics.
- We collect data at the system, application, pool, pool member, virtual server, and node levels.
+ We collect data at the system, node, pool, pool member, and virtual server levels.
Follow the [F5 monitoring integration documentation](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/f5-monitoring-integration) to get started.
summary: |
- Monitor your F5 BIG-IP with New Relic.
-icon: logo.svg
+ Monitor your F5 BIG-IP system with New Relic.
level: New Relic
authors:
- New Relic
-title: F5
-documentation:
- - name: F5 installation docs
- description: |
- Family of software and hardware products designed around application
- availability, access control, and security.
- url: https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/f5-monitoring-integration
+ - Zack Mutchler
keywords:
- infrastructure
+ - f5
+ - big-ip
+ - big ip
- load balancer
installPlans:
- third-party-f5
dataSourceIds:
- f5
+alertPolicies:
+ - f5
+dashboards:
+ - f5
+documentation:
+ - name: F5 installation docs
+ description: |
+ Set of application delivery products that work together to ensure
+ high availability, improved performance, application security, and access control.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/f5-monitoring-integration/#install
+icon: logo.svg
diff --git a/quickstarts/faiss/config.yml b/quickstarts/faiss/config.yml
new file mode 100644
index 0000000000..bee9eeefad
--- /dev/null
+++ b/quickstarts/faiss/config.yml
@@ -0,0 +1,49 @@
+id: 351b326f-a2c5-4994-80c0-437f74d5398a
+slug: faiss
+description: |
+ ## Why should you monitor your usage of FAISS?
+
+ Monitor your vector searches on FAISS to get visibility on what you send to FAISS, responses retrieved from FAISS, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic FAISS quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: FAISS
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - FAISS
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/faiss/logo.png b/quickstarts/faiss/logo.png
new file mode 100644
index 0000000000..caff5572de
Binary files /dev/null and b/quickstarts/faiss/logo.png differ
diff --git a/quickstarts/flutter-android/config.yml b/quickstarts/flutter-android/config.yml
new file mode 100644
index 0000000000..7c493267aa
--- /dev/null
+++ b/quickstarts/flutter-android/config.yml
@@ -0,0 +1,44 @@
+id: 4dbabbe7-1e32-47fc-b80b-a792aaa38ba7
+slug: flutter-android
+description: |
+ ## Comprehensive monitoring quickstart for Flutter Android
+
+ Monitor your Flutter applications and analyze performance bottlenecks while operating in a live development environment. You can use this dashboard to visualize your web user experience with your application rendition.
+
+ ## Why monitor Flutter Android?
+ Monitoring app performance allows you to avoid crashes, bugs, or user complaints by taking a preventative approach rather than waiting until an issue arises. With New Relic Android and Flutter agents, you can track important metrics such as network failures, HTTP response times, slow launches, and custom traces.
+
+ You can optimize the process once you have a comprehensive picture of all releases by prioritizing active issues and marking errors as corrected. Identify the release in which the problem first appeared, merge duplicates, and assess whether the issue may worsen. Send deploy emails instantly with commit information, and suggest an owner for each application error.
+
+ ## What’s included in this quickstart?
+ New Relic Android and Flutter monitoring agents capture the following metrics:
+
+ - Get alerted when critical issues affect your Flutter application
+ - Dashboards (error rate, app launches, app installations, app crashes and more)
+ - Monitor Flutter Dart exceptions and errors
+ - Monitor HTTP responses & errors, and mobile events
+
+summary: |
+ Identify and optimize Flutter Android app performance with New Relic Flutter Android monitoring.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Flutter Android
+documentation:
+ - name: Flutter Android integration documentation
+ description: |
+ Monitor the performance metrics of your Flutter Android application instances in real-time with New Relic Android and Flutter agents.
+ url: >-
+ https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile-flutter/monitor-your-flutter-application/
+keywords:
+ - flutter
+ - flutter android application
+ - android agent
+ - flutter agent
+dashboards:
+ - flutter-android
+alertPolicies:
+ - flutter-android
+dataSourceIds:
+ - flutter-android
\ No newline at end of file
diff --git a/quickstarts/flutter-android/logo.png b/quickstarts/flutter-android/logo.png
new file mode 100644
index 0000000000..cfc0ee42f3
Binary files /dev/null and b/quickstarts/flutter-android/logo.png differ
diff --git a/quickstarts/flutter-ios/config.yml b/quickstarts/flutter-ios/config.yml
new file mode 100644
index 0000000000..0e0aabb3aa
--- /dev/null
+++ b/quickstarts/flutter-ios/config.yml
@@ -0,0 +1,46 @@
+id: e39b2930-856a-4023-90b6-1275ab889ba5
+slug: flutter-ios
+description: |
+ ## Comprehensive monitoring quickstart for Flutter iOS
+
+ Monitor your Flutter applications and analyze performance bottlenecks while operating in a live development environment. You can use this dashboard to visualize your web user experience with your application rendition.
+
+ ## Why monitor Flutter iOS?
+ Monitoring app performance allows you to avoid crashes, bugs, or user complaints by taking a preventative approach rather than waiting until an issue arises. With New Relic iOS and Flutter agents, you can track important metrics such as network failures, HTTP response times, slow launches, and custom traces.
+
+ You can optimize the process once you have a comprehensive picture of all releases by prioritizing active issues and marking errors as corrected. Identify the release in which the problem first appeared, merge duplicates, and assess whether the issue may worsen. Send deploy emails instantly with commit information, and suggest an owner for each application error.
+
+
+
+ ## What’s included in this quickstart?
+ New Relic iOS and Flutter monitoring agents capture the following metrics:
+
+ - Get alerted when critical issues affect your Flutter application
+ - Dashboards (error rate, app launches, app installations, app crashes and more)
+ - Monitor Flutter Dart exceptions and errors
+ - Monitor HTTP responses & errors, and mobile events
+
+summary: |
+ Identify and optimize Flutter iOS app performance with New Relic Flutter iOS monitoring.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Flutter iOS
+documentation:
+ - name: Flutter iOS integration documentation
+ description: |
+ Monitor the performance metrics of your Flutter iOS application instances in real-time with New Relic iOS and Flutter agents.
+ url: >-
+ https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile-flutter/monitor-your-flutter-application/
+keywords:
+ - flutter
+ - flutter ios application
+ - ios agent
+ - flutter agent
+dashboards:
+ - flutter-ios
+alertPolicies:
+ - flutter-ios
+dataSourceIds:
+ - flutter-ios
diff --git a/quickstarts/flutter-ios/logo.png b/quickstarts/flutter-ios/logo.png
new file mode 100644
index 0000000000..5ae499e057
Binary files /dev/null and b/quickstarts/flutter-ios/logo.png differ
diff --git a/quickstarts/flutter-web/config.yml b/quickstarts/flutter-web/config.yml
new file mode 100644
index 0000000000..5aefae2eca
--- /dev/null
+++ b/quickstarts/flutter-web/config.yml
@@ -0,0 +1,42 @@
+id: 03dec978-0ea3-4126-a722-7423ee3deaf4
+slug: flutter-web
+description: |
+ ## Why monitor Flutter Web?
+ Monitoring application performance helps you to take a preventative approach to enhance quality rather than waiting for a crash, issue, or user complaint to occur. The New Relic Flutter web monitoring quickstart allows you to track important metrics including Apdex ratings, UI hangs, network timeouts and issues, slow launches, tracking custom traces, and more.
+ By prioritizing active issues and marking errors as corrected, you may optimize the process once you have a comprehensive picture of all releases. Find out which version the problem first appeared in, merge duplicates, and assess whether anything may get worse in a later release. Add commit information to send deploy emails instantly and suggest an owner for each application error.
+
+ ## Comprehensive monitoring quickstart for Flutter Web.
+
+ Monitor your Flutter applications, and analyze performance bottlenecks in the production environment. Visually monitor your web user experience across the world along with your application performance via the dashboard.
+ Install and start monitoring your data today!
+
+ ## What’s included in this quickstart?
+ New Relic's Browser monitoring agent captured the metrics out of the box:
+ - Get alerts when your application suffers critical failures and errors..
+ - Dashboards (Throughput, Error rate, Web transaction Time, Apdex Score, Page views, and more).
+ - Monitor scripts and functions.
+ - Monitor web transactions.
+
+summary: |
+ Instrument and monitor your Flutter Web application with the New Relic Browser Monitoring agent. Analyze your performance data (Errors, Page load time, User traffic, and Page views) in view for the best code diagnosis, improvement, and optimization.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Flutter Web
+documentation:
+ - name: Flutter Web integration documentation
+ description: |
+ Monitor the performance metrics of your Flutter Web application instances in real-time with New Relic Browser agent.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/browser-monitoring-integrations/flutter-web-integration/
+keywords:
+ - flutter
+ - flutter web application
+ - browser agent
+dataSourceIds:
+ - flutter-web
+dashboards:
+ - flutter-web
+alertPolicies:
+ - flutter-web
\ No newline at end of file
diff --git a/quickstarts/flutter-web/logo.png b/quickstarts/flutter-web/logo.png
new file mode 100644
index 0000000000..cfc0ee42f3
Binary files /dev/null and b/quickstarts/flutter-web/logo.png differ
diff --git a/quickstarts/gatsby-build/config.yml b/quickstarts/gatsby-build/config.yml
index 10f0a84906..00e00d47a3 100644
--- a/quickstarts/gatsby-build/config.yml
+++ b/quickstarts/gatsby-build/config.yml
@@ -22,7 +22,5 @@ documentation:
description: |
Ship performance data from Gatsby builds using OpenTelemetry
url: https://newrelic.com/blog/best-practices/optimize-gatsby-build-opentelemetry
-keywords:
- - featured
dashboards:
- gatsby-build
diff --git a/quickstarts/gcp/gcp-alloydb/config.yml b/quickstarts/gcp/gcp-alloydb/config.yml
new file mode 100644
index 0000000000..f8736026bd
--- /dev/null
+++ b/quickstarts/gcp/gcp-alloydb/config.yml
@@ -0,0 +1,35 @@
+id: 27c65f9b-b15d-4894-ab44-e8a45e045fb8
+slug: gcp-alloydb
+description: |-
+ ## What is AlloyDB?
+
+ A fully managed PostgreSQL-compatible database service for your most demanding enterprise database workloads. AlloyDB combines the best of Google
+ with one of the most popular open-source database engines, PostgreSQL, for superior performance, scale, and availability.
+
+ ### Get started!
+
+ Start monitoring AlloyDB by connecting Google Cloud Platform (GCP) to New Relic!
+ Check out our AlloyDB documentation to instrument your cloud service and manage the stability, scalability, and reliability of your systems with
+ New Relic's infrastructure monitoring capabilities.
+
+ ### More info
+
+ Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-alloydb-monitoring-integration/) to learn more about New Relic monitoring for AlloyDB.
+summary: Monitor AlloyDB by connecting GCP to New Relic
+icon: icon.png
+level: New Relic
+authors:
+ - New Relic
+title: AlloyDB
+documentation:
+ - name: AlloyDB integration docs
+ description: Monitor AlloyDB by connecting GCP to New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-alloydb-monitoring-integration/
+keywords:
+ - gcp
+ - google cloud platform
+ - alloydb
+dataSourceIds:
+ - gcp-infrastructure-monitoring
+dashboards:
+ - gcp-alloydb
diff --git a/quickstarts/gcp/gcp-alloydb/icon.png b/quickstarts/gcp/gcp-alloydb/icon.png
new file mode 100644
index 0000000000..54e8591d5c
Binary files /dev/null and b/quickstarts/gcp/gcp-alloydb/icon.png differ
diff --git a/quickstarts/gcp/google-cloud-spanner-otel/config.yml b/quickstarts/gcp/google-cloud-spanner-otel/config.yml
index 2bdcff171a..d9f39d7fa8 100644
--- a/quickstarts/gcp/google-cloud-spanner-otel/config.yml
+++ b/quickstarts/gcp/google-cloud-spanner-otel/config.yml
@@ -24,7 +24,7 @@ description: |-
- The dashboard included in this quickstart works by using finding `instrumentation.source = gcpspanner.` If you want to use this without changing the queries, be sure to use this as the name to identify the data source from the prometheus link.
- You can add key identifying variables like project, instance, and database to your dashboard by selecting the `Add variable` option at the top of the dashboard
summary: Leverage OTel to monitor GCP Cloud Spanner
-icon: logo.svg
+icon: gcpspanner.png
level: verified
authors:
- New Relic
diff --git a/quickstarts/gcp/google-cloud-spanner-otel/gcpspanner.png b/quickstarts/gcp/google-cloud-spanner-otel/gcpspanner.png
new file mode 100644
index 0000000000..a6c852de7c
Binary files /dev/null and b/quickstarts/gcp/google-cloud-spanner-otel/gcpspanner.png differ
diff --git a/quickstarts/gcp/google-cloud-spanner-otel/logo.svg b/quickstarts/gcp/google-cloud-spanner-otel/logo.svg
deleted file mode 100644
index c14b248faf..0000000000
--- a/quickstarts/gcp/google-cloud-spanner-otel/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/gcp/google-cloud-spanner/config.yml b/quickstarts/gcp/google-cloud-spanner/config.yml
index 008ea81f64..a335255ce8 100644
--- a/quickstarts/gcp/google-cloud-spanner/config.yml
+++ b/quickstarts/gcp/google-cloud-spanner/config.yml
@@ -17,7 +17,7 @@ description: |-
Check out the [documentation](https://docs.newrelic.com/docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-spanner-monitoring-integration/) to learn more about New Relic monitoring for Google Cloud Spanner.
summary: Monitor Google Cloud Spanner by connecting GCP to New Relic
-icon: logo.svg
+icon: gcpspanner.png
level: New Relic
authors:
- New Relic
@@ -31,6 +31,8 @@ keywords:
- gcp
- google cloud platform
- database
+dashboards:
+ - gcp-spanner
installPlans:
- gcp-infrastructure-monitoring
dataSourceIds:
diff --git a/quickstarts/gcp/google-cloud-spanner/gcpspanner.png b/quickstarts/gcp/google-cloud-spanner/gcpspanner.png
new file mode 100644
index 0000000000..a6c852de7c
Binary files /dev/null and b/quickstarts/gcp/google-cloud-spanner/gcpspanner.png differ
diff --git a/quickstarts/gcp/google-cloud-spanner/logo.svg b/quickstarts/gcp/google-cloud-spanner/logo.svg
deleted file mode 100644
index c14b248faf..0000000000
--- a/quickstarts/gcp/google-cloud-spanner/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/gh-gates/config.yml b/quickstarts/gh-gates/config.yml
new file mode 100644
index 0000000000..612f6c27ff
--- /dev/null
+++ b/quickstarts/gh-gates/config.yml
@@ -0,0 +1,42 @@
+id: 91464093-cc5d-4599-8fee-23f4de0183b5
+slug: github-deployment-protection
+title: GitHub Deployment Protection Rules
+description: |+
+ ## What are Deployment Protection Rules
+ Deployment Protection Rules for GitHub Actions provides additional control to your [GitHub Actions](https://github.com/features/actions) CI/CD workflows. Developers can enforce quality gates on every deployment environment, preventing deployments that do not meet specific criteria from reaching production.
+
+ ### Why Set Up Deployment Protection Rules
+ By setting up Deployment Protection Rules and integrating them into their release processes, teams can break down silos and create tighter collaboration between development, operations, and other groups for faster, more reliable releases. This can also lead to a better overall development lifecycle, with fewer bugs, better testing, and more reliable code.
+
+ ## Integrate New Relic with GitHub Actions releases
+ New Relic and GitHub have made it easy to set up rigorous control mechanisms that ensure only high-quality thoroughly tested code reaches production.
+
+ With the [New Relic Gate App](https://github.com/apps/new-relic-gate), you can leverage anomaly detection to automatically intercept and validate deployment requests. This lets you prevent issues earlier in the release cycle to reduce alarming on higher level environments and build better software.
+
+ ### Benefits
+ With this integration, you can connect software performance and environment health analysis to actual deployment criteria, allowing you to:
+
+ - **Protect downstream environments from potential issues.** Connect New Relic signals with your deployment gates to prevent hazards and issues from being deployed downstream.
+ - **Gain flexible control with New Relic AIOps.** Whether it's errors, performance changes, or anomalies, anything you monitor can become a deployment gate.
+ - **Catch issues earlier in the release cycle.** Shift left and prevent issues before they make it to production.
+
+ ## Get Started
+ - [Learn more](https://docs.newrelic.com/whats-new/2023/04/whats-new-04-20-github-integration/)
+ - [See instructions](https://github.com/apps/new-relic-gate)and install the app.
+
+summary: Use New Relic anomaly detection to create GitHub deployment protection rules
+level: New Relic
+authors:
+ - New Relic
+keywords:
+ - github
+ - gates
+ - anomaly detection
+ - notifications
+ - AIOps
+ - Incident Intelligence
+documentation:
+ - name: Get Started
+ url: https://docs.newrelic.com/whats-new/2023/04/whats-new-04-20-github-integration/
+ description: Create GitHub Actions Deployment Protection Rules with New Relic AIOps
+icon: logo.svg
diff --git a/quickstarts/gh-gates/logo.svg b/quickstarts/gh-gates/logo.svg
new file mode 100644
index 0000000000..d5e6491854
--- /dev/null
+++ b/quickstarts/gh-gates/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/gigamon-appinsights/config.yml b/quickstarts/gigamon-appinsights/config.yml
new file mode 100644
index 0000000000..8f98f2aa0d
--- /dev/null
+++ b/quickstarts/gigamon-appinsights/config.yml
@@ -0,0 +1,48 @@
+id: 77af041f-de6c-45d1-9ac1-8d77d48ab9a9
+
+
+slug: gigamon-appinsights
+
+title: Gigamon Application Insights
+
+description: |
+ ## Deep Application Visibility
+ Analytics tools are only as smart as the data they receive. Gigamon Application Metadata Intelligence empowers
+ New Relic with critical metadata attributes across thousands of business, consumer and IT applications and services.
+ Get deep application visibility to rapidly pinpoint performance bottlenecks, quality issues and potential network security risks.
+
+summary: |
+ Powered by Gigamon's Application Metadata Intelligence (AMI), part of Application Intelligence, to help you monitor and manage complex digital initiatives.
+
+level: Verified
+
+authors:
+ - Gigamon
+
+keywords:
+ - gigamon
+ - application
+ - network
+ - AMI
+ - intelligence
+ - metadata
+ - siem
+ - newrelic partner
+ - NR1_addData
+ - NR1_sys
+
+documentation:
+ - name: Application Metadata Intelligence
+ url: https://www.gigamon.com/products/optimize-traffic/application-intelligence/application-metadata
+ description: Application Metadata Intelligence (AMI) helps you monitor and manage complex digital applications using network traffic analytics.
+
+icon: gigamon-appint.png
+
+dashboards:
+ - gigamon-appinsights
+
+installPlans:
+ - third-party-gigamon-appinsights
+
+dataSourceIds:
+ - gigamon-appinsights
diff --git a/quickstarts/gigamon-appinsights/gigamon-appint.png b/quickstarts/gigamon-appinsights/gigamon-appint.png
new file mode 100755
index 0000000000..900f571a6c
Binary files /dev/null and b/quickstarts/gigamon-appinsights/gigamon-appint.png differ
diff --git a/quickstarts/github-repo/config.yml b/quickstarts/github-repo/config.yml
new file mode 100644
index 0000000000..66cafda020
--- /dev/null
+++ b/quickstarts/github-repo/config.yml
@@ -0,0 +1,30 @@
+id: f9bee2fb-ce0a-472f-a32a-64de90a6c1c3
+
+slug: github-repo
+title: GitHub Repo
+description: |-
+ ## What is GitHub?
+
+ GitHub is where over 100 million developers shape the future of software, together.
+
+ Contribute to the open source community, manage your Git repositories, review code like a pro, track bugs and features, power your CI/CD and DevOps workflows, and secure code before you commit it.
+summary: |
+ Monitor GitHub Repositories in New Relic by adding Headerless Log API endpoint as a GitHub Repository Webhook.
+level: Community
+authors:
+ - New Relic
+ - Peter Nguyen
+keywords:
+ - github
+ - repository
+ - workflows
+ - pipelines
+dashboards:
+ - github-repo
+documentation:
+ - name: Send Logs to New Relic API Endpoint
+ url: https://docs.newrelic.com/docs/logs/log-api/introduction-log-api/
+ description: Generate your log API endpoint in New Relic with your Api-Key as the query parameter.
+icon: logo.png
+website: https://www.newrelic.com
+
diff --git a/quickstarts/github-repo/logo.png b/quickstarts/github-repo/logo.png
new file mode 100644
index 0000000000..f1f2899acd
Binary files /dev/null and b/quickstarts/github-repo/logo.png differ
diff --git a/quickstarts/gitlab/config.yml b/quickstarts/gitlab/config.yml
index 716718a338..aaa5663ce5 100644
--- a/quickstarts/gitlab/config.yml
+++ b/quickstarts/gitlab/config.yml
@@ -30,3 +30,4 @@ documentation:
description: Monitor your Gitlab pipelines with New Relic, making it easier to get observability into your CI/CD pipeline health and performance.
icon: logo.svg
website: https://www.newrelic.com
+
diff --git a/quickstarts/golden-signals-dashboard/config.yml b/quickstarts/golden-signals-dashboard/config.yml
new file mode 100644
index 0000000000..6b9e0bae5d
--- /dev/null
+++ b/quickstarts/golden-signals-dashboard/config.yml
@@ -0,0 +1,79 @@
+id: b9e3fc9f-c54a-4e30-8f2a-0319a07f7ac3
+# Sets the URL name of the quickstart on public I/O (required)
+slug: golden-signals-dashboard-for-new-relic
+
+# Displayed in the UI (required)
+title: Golden signals for New Relic
+
+# Long-form description of the quickstart (required)
+description: |
+ Dashboard to monitor golden signals across APM, Infrastructure, Synthetics, Browser and Mobile with template variables to dynamically filter widgets.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ Monitoring the golden signals allows you to quickly see an overview of the health of your application. This dashboard lets you monitor golden signals across APM, Infrastructure, Synthetics, Browser and Mobile with template variables to dynamically filter widgets.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Zahra Siddiqa
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - golden signals
+ - monitoring
+ - latency
+ - traffic
+ - errors
+ - error rates
+ - availability
+
+# # Reference to alert policies to be included in this quickstart
+# alertPolicies:
+# - condition-a
+# - condition-b
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - golden-signals-dashboard
+
+# Documentation references
+documentation:
+ - name: Install APM agent
+ url: https://docs.newrelic.com/introduction-apm/
+ description: Monitor everything from the hundreds of dependencies of a modern stack down to simple web-transaction times and throughput of an app.
+
+ - name: Install Infrastructure agent
+ url: https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent/
+ description: New Relic's infrastructure monitoring agent collects data about your hosts. It also reports data from some third party services, if enabled, and also log data.
+
+ - name: Set up Synthetic monitor
+ url: https://docs.newrelic.com/docs/synthetics/synthetic-monitoring/getting-started/get-started-synthetic-monitoring/
+ description: Synthetic monitoring helps you proactively catch and resolve issues before they affect your customers, all without an installation.
+
+ - name: Install Browser agent
+ url: https://docs.newrelic.com/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent/
+ description: The browser agent is a snippet of JavaScript code that monitors the performance of your app/site.
+
+ - name: Install Mobile agent
+ url: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/
+ description: New Relic's mobile monitoring capabilities provide deeper visibility into the performance and crash troubleshooting of your Android, iOS, or hybrid mobile applications.
+
+dataSourceIds:
+ - golang
+ - microsoftnet
+ - java
+ - node-js
+ - php
+ - python
+ - ruby
+ - new-relic-infrastructure-agent
+ - new-relic-synthetics
+ - new-relic-browser
+ - mobile-getting-started
+
+# Content / Design
+icon: logo.svg
+website: https://www.newrelic.com
diff --git a/quickstarts/golden-signals-dashboard/logo.svg b/quickstarts/golden-signals-dashboard/logo.svg
new file mode 100644
index 0000000000..565d92d4e7
--- /dev/null
+++ b/quickstarts/golden-signals-dashboard/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/gridgain/config.yml b/quickstarts/gridgain/config.yml
new file mode 100644
index 0000000000..f2d16d5ba0
--- /dev/null
+++ b/quickstarts/gridgain/config.yml
@@ -0,0 +1,67 @@
+id: 6c88da16-0dbf-4159-9313-0ccfc48ffbaf
+slug: gridgain
+title: GridGain
+
+description: |
+ # What is GridGain?
+
+ GridGain is a unified real-time data platform that is designed to
+ tackle speed and scale challenges. It is built on Apache Ignite, a top
+ 5 ASF project.
+
+ ## Getting started
+
+ GridGain exports extensive metrics and this quickstart allows you to
+ view them in New Relic. The same steps should also work with Apache
+ Ignite. To get started with GridGain, please check out [the
+ documentation](https://www.gridgain.com/docs/latest/).
+
+ ## Dashboard
+
+ This quickstart includes a sample dashboard. Note that the widgets
+ included are reasonable defaults but will likely need to be updated
+ depending on your configuration (persistence), use case (compute,
+ caching) and product (snapshots, data center replication).
+
+ ## More information
+
+ More information can be found in [our
+ documentation](https://docs.gridgain.com). Download GridGain
+ [here](https://www.gridgain.com/download) or launch your own cluster
+ in the cloud [here](https://portal.gridgain.com).
+
+summary: |
+ A quickstart for monitoring GridGain and Apache Ignite clusters.
+
+level: Community
+
+authors:
+ - GridGain
+ - Stephen Darlington
+
+keywords:
+ - database
+ - java
+ - cluster
+ - sql
+ - cache
+ - compute-grid
+ - apache-ignite
+ - ignite
+
+dataSourceIds:
+ - gridgain-data-source
+
+dashboards:
+ - gridgain
+
+documentation:
+ - name: GridGain documentation
+ url: https://www.gridgain.com/docs/latest/
+ description: Getting started with GridGain.
+ - name: GridGain integration document
+ url: https://www.gridgain.com/docs/tutorials/new-relic/new-relic-tutorial
+ description: Capture the logs and metrics from GridGain in New Relic.
+
+icon: gridgain.svg
+website: https://www.gridgain.com/
diff --git a/quickstarts/gridgain/gridgain.svg b/quickstarts/gridgain/gridgain.svg
new file mode 100644
index 0000000000..7376a3634a
--- /dev/null
+++ b/quickstarts/gridgain/gridgain.svg
@@ -0,0 +1,3 @@
+
diff --git a/quickstarts/harbor/config.yml b/quickstarts/harbor/config.yml
index 62faa36705..243e81547a 100644
--- a/quickstarts/harbor/config.yml
+++ b/quickstarts/harbor/config.yml
@@ -20,6 +20,7 @@ keywords:
- remote-write
- promql
- grafana
+ - featured
documentation:
- name: Prometheus Installation Docs
url: https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/
diff --git a/quickstarts/hivemq/config.yml b/quickstarts/hivemq/config.yml
new file mode 100644
index 0000000000..5c4b73191e
--- /dev/null
+++ b/quickstarts/hivemq/config.yml
@@ -0,0 +1,58 @@
+id: e3494e28-dcfb-4df2-a3d8-c7cca67525e0
+# Name of the quickstart
+slug: hivemq
+
+# Title of the quickstart
+title: HiveMQ (Prometheus)
+
+# Description of the quickstart
+description: |
+ ## HiveMQ Monitoring
+
+ HiveMQ's MQTT broker makes it easy to move data to and from connected devices in an efficient, fast and reliable manner. It's metrics subsystem reports all relevant metrics to monitor your MQTT brokers.
+
+ ### What’s Included?
+
+ New Relic + HiveMQ quickstart - New Relic’s instant observability quickstart provides the metrics reported by HiveMQ metrics subsystem.
+
+ Monitor HiveMQ with New Relic to quickly gain visibility into single node and clustered HiveMQ servers, including: cache rates, message statistics, system and JVM metrics and more.
+
+ ### Value of HiveMQ Quickstarts
+
+ [HiveMQ monitoring with New Relic](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-hivemq/) offers advanced features, including:
+ - Create custom queries and charts of your data integrations.
+ - Filter and analyze metrics in Infrastructure UI.
+
+ New Relic’s instant observability quickstart helps developers reduce administrative overheads and accelerate time to value. As New Relic is SaaS-based, you also don’t have to worry about maintenance or onboarding.
+
+summary: |
+ New Relic's HiveMQ quickstart provides data from HiveMQ metrics subsystem. Install the quickstart to better understand utilization of resources and monitor performance issues.
+
+# Support level
+level: New Relic
+
+# Design
+icon: logo.svg
+website: https://www.hivemq.com/
+
+# Authors of the quickstart
+authors:
+ - New Relic
+
+documentation:
+ - name: HiveMQ
+ description: |
+ MQTT broker that makes it easy to move data to and from connected devices.
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-hivemq/
+
+installPlans:
+ - hivemq-integration-docs
+
+dataSourceIds:
+ - hivemq-integration-docs
+
+keywords:
+ - infrastructure
+ - messaging
+ - queue
+ - prometheus
diff --git a/quickstarts/hivemq/logo.svg b/quickstarts/hivemq/logo.svg
new file mode 100644
index 0000000000..fe041eb022
--- /dev/null
+++ b/quickstarts/hivemq/logo.svg
@@ -0,0 +1,110 @@
+
+
+
diff --git a/quickstarts/hologres-matching-engine/config.yml b/quickstarts/hologres-matching-engine/config.yml
new file mode 100644
index 0000000000..98365e9961
--- /dev/null
+++ b/quickstarts/hologres-matching-engine/config.yml
@@ -0,0 +1,57 @@
+id: 949f80ee-2167-4727-80ad-c1d43cb9520e
+slug: hologres-matching-engine
+description: |
+ ## Why should you monitor Hologres Matching Engine?
+
+ Monitor your vector searches on Hologres Matching Engine to get visibility on what you send to Hologres Matching Engine, responses retrieved from Hologres Matching Engine, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+ New Relic Hologres Matching Engine quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Hologres Matching Engine app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor the performance and quality of your vector searches with New Relic Hologres Matching Engine quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Hologres Matching Engine
+documentation:
+ - name: Hologres Matching Engine integration documentation
+ description: |
+ Implement monitoring and instrumentation for your vector data store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - hologres
+ - hologres matching engine
+ - graph processing engine
+ - distributed graph processing
+ - real-time graph processing
+ - real time graph processing
+ - vector search
+ - nearest-neighbor search
+ - nearest neighbor search
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+ - data science
+ - big data
+ - AI
+ - ML
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/hologres-matching-engine/logo.png b/quickstarts/hologres-matching-engine/logo.png
new file mode 100644
index 0000000000..a6ca898501
Binary files /dev/null and b/quickstarts/hologres-matching-engine/logo.png differ
diff --git a/quickstarts/hugging-face/config.yml b/quickstarts/hugging-face/config.yml
new file mode 100644
index 0000000000..3b1da1aa93
--- /dev/null
+++ b/quickstarts/hugging-face/config.yml
@@ -0,0 +1,48 @@
+id: 4debe1f5-1662-4bc9-aefa-ebcaea8575cb
+slug: hugging-face
+description: |
+ ## Why should you monitor your usage of Hugging Face?
+ Monitor your application powered by Hugging Face language models to ensure, get visibility to what you send to Hugging Face, responses received from Hugging Face, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive Hugging Face monitoring quickstart
+ Our Hugging Face quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the Hugging Face quickstart?
+ New Relic Hugging Face monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Hugging Face usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your Hugging Face usage with New Relic Hugging Face quickstart.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: Hugging Face
+documentation:
+ - name: Hugging Face integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Hugging Face app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - hugging face
+ - mlops
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - ai
+ - generative ai
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/hugging-face/logo.png b/quickstarts/hugging-face/logo.png
new file mode 100644
index 0000000000..e7ee81c6a9
Binary files /dev/null and b/quickstarts/hugging-face/logo.png differ
diff --git a/quickstarts/ibmmq/config.yml b/quickstarts/ibmmq/config.yml
index 1e70957511..aa24ea72ff 100644
--- a/quickstarts/ibmmq/config.yml
+++ b/quickstarts/ibmmq/config.yml
@@ -47,3 +47,4 @@ dataSourceIds:
- ibmmq-integration-docs
dashboards:
- ibmmq
+
diff --git a/quickstarts/java/rmi/config.yml b/quickstarts/java/rmi/config.yml
new file mode 100644
index 0000000000..6261bb4dbb
--- /dev/null
+++ b/quickstarts/java/rmi/config.yml
@@ -0,0 +1,49 @@
+id: 2c586cea-b68d-46bb-9a75-99bdfa40b5cf
+slug: newrelic-java-rmi
+title: RMI Java Agent Extension
+description: |
+ # What is RMI?
+ RMI stands for Remote Method Invocation. It is a Java-based application programming interface (API) that allows objects
+ in one Java virtual machine (JVM) to invoke methods on objects located in another JVM, whether they are on the same machine
+ or on a remote system. RMI enables distributed computing by providing a mechanism for objects to interact and communicate with
+ each other across different JVMs.
+
+ With RMI, a client program can access and invoke methods on remote objects as if they were local objects, abstracting the complexities
+ of network communication and serialization. RMI handles the low-level details of communication, such as marshaling and unmarshaling parameters
+ and results, so developers can focus on writing the application logic.
+
+ RMI relies on Java's object serialization mechanism to pass objects between JVMs. It allows objects to be passed as parameters, return values, or exceptions in method invocations, enabling distributed computing scenarios such as remote method calls, distributed object models, and distributed event notification systems.
+
+summary: |
+ RMI Java agent extension that effectively links client-initiated calls with remote server calls, facilitating the monitoring of these interactions.
+ Once deployed, the client and server transactions will be tied together with Distributed Tracing.
+
+level: Community
+
+keywords:
+ - nrlabs
+ - nrlabs-data
+ - apm
+ - java
+ - rmi
+ - remote method invocation
+icon: logo.svg
+authors:
+ - New Relic Labs
+dataSourceIds:
+ - newrelic-java-rmi
+documentation:
+ - name: Java agent extension for RMI
+ description: |
+ Provides instrumentation for the Java RMI on both the server and client side.
+ url: https://github.com/newrelic/newrelic-java-rmi/tree/main#installation
+
+ - name: Java RMI Example
+ description: |
+ Provides a working sample for both RMI Client and Server
+ url: https://github.com/newrelic/newrelic-java-rmi/blob/main/docs/rmi_sample_userguide.pdf
+
+dashboards:
+ - java
+alertPolicies:
+ - java
diff --git a/quickstarts/java/rmi/logo.svg b/quickstarts/java/rmi/logo.svg
new file mode 100644
index 0000000000..44dad2a2ed
--- /dev/null
+++ b/quickstarts/java/rmi/logo.svg
@@ -0,0 +1,78 @@
+
+
diff --git a/quickstarts/java/websphere-liberty-profile/config.yml b/quickstarts/java/websphere-liberty-profile/config.yml
index 35165ada8e..c03ff9cddf 100644
--- a/quickstarts/java/websphere-liberty-profile/config.yml
+++ b/quickstarts/java/websphere-liberty-profile/config.yml
@@ -1,6 +1,6 @@
id: 24dd2335-8e24-4923-9560-67612b409762
slug: websphere-liberty-profile
-title: Websphere Liberty Profile
+title: IBM Websphere Liberty Profile
description: |
## Monitoring WebSphere Liberty Profile
@@ -27,7 +27,7 @@ description: |
Install the New Relic WebSphere Liberty Profile quickstart to effectively monitor Liberty Profile key performance indicators with our Java agent. This quickstart is the key to making sure that you detect and respond to any incident quickly and efficiently.
summary: |
Monitoring WebSphere Liberty Profile is critical to ensure that you detect incidents and respond to them quickly. Download the New Relic quickstart to track WebSphere Liberty Profile performance metrics.
-icon: logo.svg
+icon: logo.png
level: Community
authors:
- New Relic
@@ -40,6 +40,10 @@ dataSourceIds:
- java
documentation:
- name: Installation Docs
- url: https://docs.newrelic.com/docs/agents/java-agent/installation/include-java-agent-jvm-argument/#Installing_on_WebSphere_Liberty_Profile
+ url: https://docs.newrelic.com/install/java/?deployment=appServer&framework=websphere
description: |
Installation instructions for the Java agent and configuration options for Websphere Liberty Profile
+dashboards:
+ - websphere-liberty-profile
+alertPolicies:
+ - websphere-liberty-profile
\ No newline at end of file
diff --git a/quickstarts/java/websphere-liberty-profile/logo.png b/quickstarts/java/websphere-liberty-profile/logo.png
new file mode 100644
index 0000000000..cfe333e493
Binary files /dev/null and b/quickstarts/java/websphere-liberty-profile/logo.png differ
diff --git a/quickstarts/java/websphere-liberty-profile/logo.svg b/quickstarts/java/websphere-liberty-profile/logo.svg
deleted file mode 100644
index b66e072186..0000000000
--- a/quickstarts/java/websphere-liberty-profile/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/jfrog-platform/config.yml b/quickstarts/jfrog-platform/config.yml
index 1b703caddf..cb48405615 100644
--- a/quickstarts/jfrog-platform/config.yml
+++ b/quickstarts/jfrog-platform/config.yml
@@ -33,11 +33,13 @@ keywords:
- artifactory
- xray
- security
+ - featured
+ - NR1_addData
documentation:
- name: JFrog Observability Solution
- url: https://github.com/jfrog/log-analytics-newrelic
+ url: https://jfrog.com/help/r/jfrog-platform-administration-documentation/new-relic
description: |
- JFrog Github documentation
+ JFrog integration documentation
icon: icon.svg
dashboards:
- jfrog-artifactory
diff --git a/quickstarts/jina-ai/config.yml b/quickstarts/jina-ai/config.yml
new file mode 100644
index 0000000000..43b88143fb
--- /dev/null
+++ b/quickstarts/jina-ai/config.yml
@@ -0,0 +1,56 @@
+id: 803470a2-15f2-4e64-92f4-e5d4c9563e6d
+slug: jina-ai
+description: |
+ ## Why should you monitor your usage of Jina AI?
+ Monitor your application powered by Jina AI language models to ensure, get visibility to what you send to Jina AI, responses received from Jina AI, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive Jina AI monitoring quickstart
+ Our Jina AI quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the Jina AI quickstart?
+ New Relic Jina AI monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Jina AI usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your Jina AI usage with New Relic Jina AI quickstart.
+icon: logo.jpeg
+level:
+ - New Relic
+authors:
+ - New Relic
+title: Jina AI
+documentation:
+ - name: Jina AI integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Jina AI app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - jina-ai
+ - large language model
+ - natural language processing
+ - nlp
+ - machine learning
+ - artificial intelligence
+ - ai
+ - jina ai
+ - cloud native
+ - llm
+ - llm chains
+ - generative ai
+ - jinaai
+ - multimodal ai
+ - neural search
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/jina-ai/logo.jpeg b/quickstarts/jina-ai/logo.jpeg
new file mode 100644
index 0000000000..4c313f647d
Binary files /dev/null and b/quickstarts/jina-ai/logo.jpeg differ
diff --git a/quickstarts/jmeter/config.yml b/quickstarts/jmeter/config.yml
new file mode 100644
index 0000000000..9fc3af9fc9
--- /dev/null
+++ b/quickstarts/jmeter/config.yml
@@ -0,0 +1,67 @@
+id: 18db3f9a-9033-4ff2-a2da-537409a500ac
+# Sets the URL name of the quickstart on public I/O (required)
+slug: jmeter
+
+# Displayed in the UI (required)
+title: JMeter
+
+# Long-form description of the quickstart (required)
+description: |
+ ## Quickstart for Jmeter Test Monitoring
+ Apache JMeter is open source software, a Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.
+ The link to JMeter plug-in provided enables you to send test results to New Relic.
+ This quickstart allows users to monitor JMeter tests inside New Relic and observe test results in the context of instrumented applications.
+ The JMeter quickstart includes:
+ ## a dashboard
+ where users can easily monitor:
+ - Thread Group Details
+ - HTTP Responses
+ - Summary Report
+ - View Results in Table
+ ## alert conditions
+ where users are notified on:
+ - Test Error Rate
+ - 90th Percentile Latency
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ This quickstart allows users to monitor JMeter tests inside New Relic and observe test results in the context of instrumented applications.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Munwar Mohammed
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - jmeter
+ - performance
+ - load
+ - stress
+ - functional
+ - testing web application
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - jmeter
+
+alertPolicies:
+ - jmeter
+
+dataSourceIds:
+ - jmeter
+
+# Documentation references
+documentation:
+ - name: Set up JMeter to send data to New Relic
+ url: https://github.com/darrensmithwtc/jmeter-backend-newrelic
+ description: Information on how to setup JMeter plug-in to send test results to New Relic
+ - name: Learn more about Apache JMeter
+ url: https://jmeter.apache.org/
+ description: Information on how Apache JMeter can be utilized to performance test dynamic web applications
+
+# Content / Design
+icon: logo.png
+website: https://jmeter.apache.org/
\ No newline at end of file
diff --git a/quickstarts/jmeter/logo.png b/quickstarts/jmeter/logo.png
new file mode 100644
index 0000000000..d30a4a9ee6
Binary files /dev/null and b/quickstarts/jmeter/logo.png differ
diff --git a/quickstarts/k6/config.yml b/quickstarts/k6/config.yml
new file mode 100644
index 0000000000..fc8a8fbd1e
--- /dev/null
+++ b/quickstarts/k6/config.yml
@@ -0,0 +1,50 @@
+id: b9ef4c73-0875-43dd-b9d5-4c3bb74632ea
+slug: k6
+
+title: k6
+
+description: |
+ ## Quickstart for k6 Load Test Monitoring
+
+ k6 can send performance metrics to New Relic through the New Relic StatsD integration. By integrating New Relic and k6, you can visualize and correlate test result data, alert on performance data, and share advanced load testing results and their KPI's with your teams. View alongside all of your other telemetry data in New Relic for added insights.
+ Installation is as simple as running the NR StatsD integration and including NR StatsD as an output in your k6 load testing script.
+
+ This quickstart includes dashboards for the following k6 charts:
+ - Number of virtual users
+ - Max, median, and average Request Durations
+ - Rate of requests (per second)
+ - Histogram bucketing requests
+ - Data sent and data received
+ - Rate of change in the number of requests
+ - Blocked requests
+ - Response timings (90th percentile)
+ - List of all available k6 metrics
+
+summary: |
+ Send k6 performance metrics to New Relic through the New Relic StatsD integration.
+
+level: Community
+icon: logo.png
+
+authors:
+ - Kinsey
+
+keywords:
+ - k6
+ - grafana
+ - load testing
+ - statsD
+
+documentation:
+ - name: Set up k6 to send data to New Relic
+ url: https://k6.io/docs/results-output/real-time/new-relic/
+ description: Information on how to set up k6 to send data to New Relic, including all configuration options from k6.
+ - name: Learn more about the New Relic StatsD integration
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/statsd-monitoring-integration-version-2/
+ description: The StatsD integration is required to send k6 data to New Relic.
+
+dataSourceIds:
+ - k6
+
+dashboards:
+ - k6
\ No newline at end of file
diff --git a/quickstarts/k6/logo.png b/quickstarts/k6/logo.png
new file mode 100644
index 0000000000..ddc4841123
Binary files /dev/null and b/quickstarts/k6/logo.png differ
diff --git a/quickstarts/kubernetes/azure-kubernetes-service/config.yml b/quickstarts/kubernetes/azure-kubernetes-service/config.yml
index 4a2b57a6db..0639d34035 100644
--- a/quickstarts/kubernetes/azure-kubernetes-service/config.yml
+++ b/quickstarts/kubernetes/azure-kubernetes-service/config.yml
@@ -26,6 +26,7 @@ keywords:
- aks
installPlans:
- kubernetes-install
-
+dataSourceIds:
+ - kubernetes
dashboards:
- - aks
\ No newline at end of file
+ - aks
diff --git a/quickstarts/kubernetes/google-kubernetes-engine/config.yml b/quickstarts/kubernetes/google-kubernetes-engine/config.yml
index 831f1d131e..d214f1fa26 100644
--- a/quickstarts/kubernetes/google-kubernetes-engine/config.yml
+++ b/quickstarts/kubernetes/google-kubernetes-engine/config.yml
@@ -26,8 +26,9 @@ keywords:
- google
installPlans:
- kubernetes-install
-
+dataSourceIds:
+ - kubernetes
dashboards:
- google-kubernetes-engine
alertPolicies:
- - google-kubernetes-engine
\ No newline at end of file
+ - google-kubernetes-engine
diff --git a/quickstarts/lacework/config.yml b/quickstarts/lacework/config.yml
index 0f7ccbdab4..46253d17fd 100644
--- a/quickstarts/lacework/config.yml
+++ b/quickstarts/lacework/config.yml
@@ -2,11 +2,16 @@ id: 8a7a7220-e8ec-4959-b35d-0fe082be8039
slug: lacework
title: Lacework
summary: Integrate Lacework's security events into the New Relic platform
-description: |-
+description: |
+ ## Lacework introduction
+
Lacework is a comprehensive cloud security platform. We aim to turn security into a data problem and replace the frictionful processes for things like breach investigations or achieving compliance standards with simple, contextualized workflows.
+
Technically, our approach is that we replace the traditional 'rules' based mentality that requires you to predict attacker patterns ahead of time with a fully ML based approach. We baseline what normal user, application and network behaviors look like across your workloads and cloud accounts automatically and then only alert you to deviations from the norm. This significantly reduces the amount of toil in setting up and maintaining our solution, but also drastically improves the efficacy and amount of security alerts you will receive.
- The following Quickstart brings the curated security alerts for misconfigurations and anomalous security behaviors into the New Relic platform so you can easily triage against your wealth of observability data or easily transition from monitoring to security investigations from a single interface!
- If you encounter any issues, have feedback or would like more details on how to get started, please head over to support.lacework.com or send an email to adam.larson@lacework.net!
+
+ This integration with Lacework and New Relic brings the curated security alerts for misconfigurations and anomalous security behaviors into the New Relic platform so you can easily triage against your wealth of observability data or easily transition from monitoring to security investigations from a single interface!
+
+ For more information/support, head over to [support.lacework.com](https://support.lacework.com/)!
icon: logo.jpg
level: Verified
website: https://lacework.com/
@@ -14,8 +19,8 @@ authors:
- Lacework, Inc
documentation:
- name: Lacework installation docs
- description: The only prerequisite is to setup the New Relic integration within the Lacework UI. Details on how to do that can be found below!
- url: https://support.lacework.com/hc/en-us/articles/360005842354-New-Relic
+ description: Setup the New Relic integration within the Lacework UI.
+ url: https://docs.lacework.net/onboarding/new-relic
keywords:
- security
- compliance
diff --git a/quickstarts/lambdatest/config.yml b/quickstarts/lambdatest/config.yml
new file mode 100644
index 0000000000..4547bd6d62
--- /dev/null
+++ b/quickstarts/lambdatest/config.yml
@@ -0,0 +1,63 @@
+id: d05d8fc5-b6cb-46aa-a5d8-06ef5d6fb0af
+slug: lambdatest
+title: LambdaTest
+description: |
+ ## About LambdaTest
+
+ LambdaTest is an AI-powered test orchestration and execution platform to run manual and automated tests at scale. With LambdaTest, developers and testers can test their websites and mobile applications across 3000+ real browsers, devices, and operating systems.
+
+ ## About LambdaTest and New Relic Integration
+
+ The integration of LambdaTest with New Relic offers a seamless experience for users aiming to optimize and monitor their stats during automated test execution. By bridging the gap between testing and performance monitoring, this integration brings forward an out-of-the-box dashboard that enables users to visualize and understand their testing metrics in real-time, set against the backdrop of broader application performance insights offered by New Relic.
+
+ ## LambdaTest Dashboard and Visualization
+
+ Upon successful integration, the LambdaTest Dashboard in New Relic becomes a hub of insights. This tailored interface showcases key testing metrics, offering a comprehensive perspective on your automated testing endeavors. Gain a high-level view of test executions, failures, and compatibility issues, ensuring you're always in the know about the quality of your web or mobile applications.
+
+ ### Test Overview
+
+ - Holistic view of automated testing activities.
+ - Displays key metrics such as test execution counts, pass rates, durations, etc.
+ - Insights on website compatibility across different browsers and devices.
+ - Immediate understanding of application's cross-browser functionality.
+
+ ### Test Errors Overview
+
+ - Focuses on discrepancies and anomalies in tests.
+ - Deep insights into test failures.
+ - Highlights the nature and frequency of errors.
+ - Provides information on environments where errors occurred.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+
+summary: |
+ LambdaTest offers a streamlined entry into automated testing. With just a few clicks, users can instantly set up, monitor, and evaluate their application's performance.
+level: Community
+authors:
+ - Prateek Saini
+ - LambdaTest
+keywords:
+ - lambdatest
+ - logs
+ - newrelic partner
+ - devops
+ - cicd
+ - testing
+ - cross-browser
+ - featured
+ - NR1_addData
+
+documentation:
+ - name: LambdaTest installation docs
+ description: Setup the New Relic integration within the LambdaTest UI.
+ url: https://www.lambdatest.com/support/docs/new-relic-integration/
+# Reference to install plans located under /install directory
+# Allows us to construct reusable "install plans" and just use their ID in the quickstart config
+
+dataSourceIds:
+ - lambdatest
+
+icon: logo.svg
+website: https://www.lambdatest.com/
+dashboards:
+ - lambdatest
\ No newline at end of file
diff --git a/quickstarts/lambdatest/logo.svg b/quickstarts/lambdatest/logo.svg
new file mode 100644
index 0000000000..03d0f6a2a2
--- /dev/null
+++ b/quickstarts/lambdatest/logo.svg
@@ -0,0 +1,3 @@
+
diff --git a/quickstarts/lampy/config.yml b/quickstarts/lampy/config.yml
new file mode 100644
index 0000000000..8a991cc4bf
--- /dev/null
+++ b/quickstarts/lampy/config.yml
@@ -0,0 +1,66 @@
+id: e2564ad3-d9d0-4a84-b842-17295cd87a08
+
+# Name of the quickstart
+slug: lampy-stack
+
+# Title of the quickstart
+title: LAMPy stack
+
+summary: |
+ With New Relic LAMPy integration, you can monitor your apps, infrastructure, web servers, databases, and databases, using Linux, Apache, MySQL, and Python agents.
+# Description of the quickstart
+description: |
+ ## Comprehensive LAMPy stack monitoring system:
+ LAMPy is a free, open source software stack used for building web sites and applications. LAMPy is an acronym for the operating system (Linux), the webserver (Apache), the database server (MySQL), and the programming language (Python).
+ ## What should you look for in a LAMPy dashboard?
+ - Linux: CPU usage, total memory usage, disk usage, etc
+ - Apache: Requests per second, bytes per second, workers status, etc
+ - MySQL: Operations per second, InnoDB read & writes, etc
+ - Python: Throughput, transaction overview, WSGI, etc
+ - In addition, you are free to create your own charts using the stored metrics
+ ## What’s included in the LAMPy quickstart?
+ This quickstart includes the following preconfigured observability solutions:
+ - Application metrics with your server’s primary health metrics, like CPU usage, memory, disk usage and more
+ - Multiple high-value alerts including latest number of questions per second, error transactions percentage, memory usage and CPU utilization
+ - Informative dashboards (Busy worker status, operations, InnoDB read and write, etc)
+
+# The logo of the quickstart
+icon: logo.png
+
+# Support level
+level: New Relic
+
+# Authors of the quickstart
+authors:
+ - New Relic
+ - Ramana Reddy
+
+installPlans:
+ - apache-integration
+ - mysql-integration
+ - setup-python-agent
+
+keywords:
+ - LAMPy
+ - linux
+ - apache
+ - mysql
+ - python
+
+dashboards:
+ - lampy
+alertPolicies:
+ - lampy
+
+documentation:
+ - name: LAMPy stack integration documentation
+ description: |
+ Integrate your LAMPy app and get your data into New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/lampy-integration/
+
+dataSourceIds:
+ - linux
+ - apache
+ - mysql
+ - python
diff --git a/quickstarts/lampy/logo.png b/quickstarts/lampy/logo.png
new file mode 100644
index 0000000000..86890ba963
Binary files /dev/null and b/quickstarts/lampy/logo.png differ
diff --git a/quickstarts/lancedb/config.yml b/quickstarts/lancedb/config.yml
new file mode 100644
index 0000000000..fcd4fe5ce8
--- /dev/null
+++ b/quickstarts/lancedb/config.yml
@@ -0,0 +1,49 @@
+id: 2da598ad-ca3c-43a7-b6a1-cd4b7f3b7af6
+slug: lancedb
+description: |
+ ## Why should you monitor your usage of LanceDB?
+
+ Monitor your vector searches on LanceDB to get visibility on what you send to LanceDB, responses retrieved from LanceDB, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic LanceDB quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: LanceDB
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - lancedb
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/lancedb/logo.png b/quickstarts/lancedb/logo.png
new file mode 100644
index 0000000000..24f091c06e
Binary files /dev/null and b/quickstarts/lancedb/logo.png differ
diff --git a/quickstarts/langchain-vectordb/config.yml b/quickstarts/langchain-vectordb/config.yml
new file mode 100644
index 0000000000..ff269fc992
--- /dev/null
+++ b/quickstarts/langchain-vectordb/config.yml
@@ -0,0 +1,47 @@
+id: d40f70e5-c346-4c2e-9e5a-03a8f5485fc5
+slug: langchain-vectordb
+description: |
+ ## Why should you monitor your usage of Vector Stores?
+
+ Monitor your vector searches to get visibility on what you send to your vector store, responses retrieved from them, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic LangChain Vector Stores quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: LangChain Vector Stores
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/langchain-vectordb/logo.png b/quickstarts/langchain-vectordb/logo.png
new file mode 100644
index 0000000000..240e64b569
Binary files /dev/null and b/quickstarts/langchain-vectordb/logo.png differ
diff --git a/quickstarts/lighttpd/config.yml b/quickstarts/lighttpd/config.yml
new file mode 100644
index 0000000000..0788ea8ce4
--- /dev/null
+++ b/quickstarts/lighttpd/config.yml
@@ -0,0 +1,40 @@
+id: c51dca70-14f4-4c1b-b0af-c2576b48f39f
+slug: lighttpd
+description: |
+ ## Comprehensive monitoring for your lighttpd server
+
+ Lighttpd is an open-source web server designed for high-performance situations while staying standards-compliant, secure, and adaptable.
+
+ ### Why monitor your lighttpd web server?
+
+ Lighttpd monitoring provides important information to help you construct a complete picture of your web server's performance. This performance data includes uptime, network in bytes and packets, number of requests, and more.
+
+ ### What’s included?
+
+ Use New Relic to monitor your lighttpd server for immediate full-stack visibility, including:
+ - Alerts on things like busy servers, average number of requests and high memory usage.
+ - Dashboards to monitor crucial performance metrics such as uptime, busy servers, idle servers, networks, requests per second, and more.
+
+summary: |
+ With our Lighttpd integration you can monitor the performance of your web server. See your uptime, network in bytes and packets, number of connections, and more.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Lighttpd
+dashboards:
+ - lighttpd
+alertPolicies:
+ - lighttpd
+documentation:
+ - name: Lighttpd
+ description: |
+ Use our infrastructure agent and Flex configuration to export lighttpd data to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/lighttpd-integration/
+dataSourceIds:
+ - lighttpd
+keywords:
+ - Lighttpd
+ - web server
+ - infrastructure
diff --git a/quickstarts/lighttpd/logo.png b/quickstarts/lighttpd/logo.png
new file mode 100644
index 0000000000..4994b5278e
Binary files /dev/null and b/quickstarts/lighttpd/logo.png differ
diff --git a/quickstarts/loadmill/config.yml b/quickstarts/loadmill/config.yml
new file mode 100644
index 0000000000..bf9e1772f4
--- /dev/null
+++ b/quickstarts/loadmill/config.yml
@@ -0,0 +1,44 @@
+id: 17b3235b-e501-47d4-8be9-2a32d23c8bb4
+# Sets the URL name of the quickstart on public I/O (required)
+slug: loadmill
+
+# Displayed in the UI (required)
+title: Loadmill Tests Results
+
+# Long-form description of the quickstart (required)
+description: |
+ Monitor your Loadmill's test results.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ Monitor your Loadmill's test results
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Loadmill L.T.D
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - tests
+ - loadmill
+ - API tests
+ - automation
+ - AI
+ - network
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - loadmill
+
+# Documentation references
+documentation:
+ - name: Loadmill Docs
+ url: https://docs.loadmill.com
+ description: Loadmill documentation
+
+# Content / Design
+icon: logo.svg
+website: https://www.loadmill.com
diff --git a/quickstarts/loadmill/logo.svg b/quickstarts/loadmill/logo.svg
new file mode 100644
index 0000000000..7c2c9f1829
--- /dev/null
+++ b/quickstarts/loadmill/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/magento-business-insights/config.yml b/quickstarts/magento-business-insights/config.yml
new file mode 100644
index 0000000000..3e7751c28b
--- /dev/null
+++ b/quickstarts/magento-business-insights/config.yml
@@ -0,0 +1,51 @@
+id: f99bd30d-bac2-4b6d-a6cb-9b582b4d0dc5
+slug: magento-business-insights
+description: |
+ ## Comprehensive monitoring quickstart for Magento Business Insights
+ Magento Business Insights involves tracking key performance indicators and other metrics in real-time, to ensure that the system is performing optimally and to identify potential issues before they become major problems.
+ ## Why monitor your Magento app?
+ Magento Ecommerce store monitoring is crucial to ensuring that the system is functioning smoothly and providing accurate data insights.
+ There are several reasons for this:
+ ### Revenue tracking:
+ Monitoring Magento Ecommerce store allows business owners and ecommerce managers to track revenue performance in real-time, ensuring that sales data is accurate and up-to-date. This information can be critical for making informed decisions around marketing and inventory management.
+ ### Downtime impact:
+ A business's revenue can be directly affected by downtime if customers are unable to purchase. Keeping track of downtime and lost revenue can help businesses quantify the impact of these issues.
+ ### Order tracking:
+ With Magento Business Insights, businesses can monitor order details such as total orders, average order value, and latest orders in order to get insight into their customer's buying behavior.
+ ### Customer details:
+ Analyzing customer details, such as new vs. returning customers and cart abandonment rates, can help businesses better understand their target market.
+ ### Funnel monitoring:
+ A funnel monitor tracks and analyzes the behavior of customers as they move through your e-commerce site. By monitoring the funnel, businesses can identify where customers are dropping off and where they need to improve the user experience to drive conversions.
+ ## What's included?
+ You'll have full-stack observability of your Magento app out-of-the-box:
+ - Alerts (Downtime (%), HTTP Errors and Largest Contentful Paint (LCP))
+ - Dashboards (Executive summary, Customers, Orders, Funnel and more)
+ - Keep an eye on the performance and reliability of your Magento site
+ - Keep track of your transactions and bottom of the funnel on a desktop or mobile device
+summary: |
+ Magento Business Insights quickstart offers a tailored business insights platform for Magento store owners and ecommerce managers. It facilitates real-time data extraction for informed decision-making.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic, Jyothi Surampudi
+title: Magento Business Insights
+documentation:
+ - name: Magento Business Insights documentation
+ description: |
+ Magento Business Insights Quickstart provides pre-configured packages for businesses to gain real-time insights.
+ url: https://docs.newrelic.com/docs/apm/agents/php-agent/other-integrations/magento-business-insights/
+keywords:
+ - magento business insights
+ - magento
+ - nri-flex
+dataSourceIds:
+ - new-relic-infrastructure-agent
+ - php
+ - mysql
+ - apache
+ - elasticsearch
+ - new-relic-synthetics
+dashboards:
+ - magento-business-insights
+alertPolicies:
+ - magento-business-insights
diff --git a/quickstarts/magento-business-insights/logo.svg b/quickstarts/magento-business-insights/logo.svg
new file mode 100644
index 0000000000..6ca1841720
--- /dev/null
+++ b/quickstarts/magento-business-insights/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/marqo/config.yml b/quickstarts/marqo/config.yml
new file mode 100644
index 0000000000..a68ca252bd
--- /dev/null
+++ b/quickstarts/marqo/config.yml
@@ -0,0 +1,49 @@
+id: cce580f3-7ba5-4519-9d7b-90f72d55440e
+slug: marqo
+description: |
+ ## Why should you monitor your usage of Marqo?
+
+ Monitor your vector searches on Marqo to get visibility on what you send to Marqo, responses retrieved from Marqo, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Marqo quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: Marqo
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - marqo
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/marqo/logo.svg b/quickstarts/marqo/logo.svg
new file mode 100644
index 0000000000..0b7c9fbdf2
--- /dev/null
+++ b/quickstarts/marqo/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/mean/config.yml b/quickstarts/mean/config.yml
new file mode 100644
index 0000000000..8d2157d021
--- /dev/null
+++ b/quickstarts/mean/config.yml
@@ -0,0 +1,51 @@
+id: 53147329-a8d4-47c3-ad53-6444a4610315
+slug: mean-stack
+description: |
+ ## Comprehensive MEAN Stack Monitoring System
+ MEAN Stack is a popular open-source framework used to build dynamic web pages and online applications. It comprises of four essential components, namely MongoDB, ExpressJS, Angular, and NodeJS, all of which are based on JavaScript and JSON. These components integrate seamlessly and logically, making it easy to create web applications using this powerful technology stack. Each of the four components has a crucial role to play in the development of web applications.
+
+ ## What should you look for in a MEAN dashboard?
+ - MongoDB metrics such as active connections, database details, and usage time
+ - For ExpressJS and NodeJS, there are a variety of metrics available, including web transactions, top ten errors, and memory usage
+ - Angular metrics include viewed urls, page views by city, ajax requests, etc. In addition, you may create your own chart based on the metrics collected
+
+ ## What’s included in the MEAN quickstart?
+ Install this quickstart to setup preconfigured observability solutions:
+ - A number of high-value alerts are available including the average number of connections created, the FCP score and the memory usage
+ - Informative dashboards (the top 10 transactions, connections, database indexes, and more)
+
+summary: |
+ Monitor your apps using New Relic MEAN integration with Angular, MongoDB and NodeJS agents for browser, database and application monitoring.
+
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: MEAN Stack
+documentation:
+ - name: MEAN Stack installation documentation
+ description: |
+ Integrate your MEAN app and get your data into New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/browser/browser-integrations/mexn-integration/
+keywords:
+ - MEAN
+ - MongoDB
+ - database
+ - ExpressJS
+ - Angular
+ - NodeJS
+ - Fullstack
+ - MEAN Stack
+ - browser agent
+ - language agent
+ - featured
+
+dataSourceIds:
+ - node-js
+ - new-relic-browser
+ - mongodb
+dashboards:
+ - mexn
+alertPolicies:
+ - mexn
diff --git a/quickstarts/mean/logo.png b/quickstarts/mean/logo.png
new file mode 100644
index 0000000000..82e69a2029
Binary files /dev/null and b/quickstarts/mean/logo.png differ
diff --git a/quickstarts/meilisearch/config.yml b/quickstarts/meilisearch/config.yml
new file mode 100644
index 0000000000..7eeca529be
--- /dev/null
+++ b/quickstarts/meilisearch/config.yml
@@ -0,0 +1,49 @@
+id: d8ad16aa-f4cf-45e1-9651-696ad775c3fa
+slug: meilisearch
+description: |
+ ## Why should you monitor your usage of Meilisearch?
+
+ Monitor your vector searches on Meilisearch to get visibility on what you send to Meilisearch, responses retrieved from Meilisearch, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Meilisearch quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Meilisearch
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - meilisearch
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/meilisearch/logo.png b/quickstarts/meilisearch/logo.png
new file mode 100644
index 0000000000..ab0386896a
Binary files /dev/null and b/quickstarts/meilisearch/logo.png differ
diff --git a/quickstarts/mern/config.yml b/quickstarts/mern/config.yml
new file mode 100644
index 0000000000..c6ec9378ef
--- /dev/null
+++ b/quickstarts/mern/config.yml
@@ -0,0 +1,60 @@
+id: ef98b152-9ccc-4e9b-8fc6-0d3b3215faeb
+# Name of the quickstart
+slug: mern-stack
+
+# Title of the quickstart
+title: MERN Stack
+
+summary: |
+ Monitor your apps using New Relic MERN integration with ReactJS, MongoDB and NodeJS agents for browser, database and application monitoring.
+
+# Description of the quickstart
+description: |
+ ## Comprehensive MERN Stack Monitoring System
+ MERN Stack is a widely used open-source framework that is based on JavaScript and is used to create dynamic web pages and online applications. The framework comprises of four components, namely MongoDB, ExpressJS, ReactJS, and NodeJS, all of which play a vital role in the development of web applications. These four technologies integrate seamlessly and logically, making it easy to build web applications using the MERN Stack. Each of these components is based on JavaScript and JSON, which makes the integration process simpler and more efficient.
+
+ ## What should you look for in a MERN dashboard?
+ - MongoDB metrics such as active connections, database details, and usage time
+ - For ExpressJS and NodeJS, there are a variety of metrics available, including web transactions, top ten errors, and memory usage
+ - ReactJS metrics include page views by city, ajax requests, and viewed urls. Additionally, you can create your own chart based on the metrics collected
+
+ ## What’s included in the MERN quickstart?
+ Install this quickstart to setup preconfigured observability solutions:
+ - A number of high-value alerts are available including the average number of connections created, the FCP score and the memory usage
+ - Informative dashboards (the top 10 transactions, connections, database indexes, and more)
+
+# The logo of the quickstart
+icon: logo.png
+
+# Support level
+level: New Relic
+
+# Authors of the quickstart
+authors:
+ - New Relic
+
+keywords:
+ - MERN
+ - MongoDB
+ - ExpressJS
+ - ReactJS
+ - NodeJS
+ - Fullstack application monitoring
+ - browser agent
+ - language agent
+ - featured
+
+dashboards:
+ - mexn
+alertPolicies:
+ - mexn
+documentation:
+ - name: MERN Stack installation documentation
+ description: |
+ Integrate your MERN app and get your data into New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/browser/browser-integrations/mexn-integration/
+dataSourceIds:
+ - node-js
+ - new-relic-browser
+ - mongodb
\ No newline at end of file
diff --git a/quickstarts/mern/logo.png b/quickstarts/mern/logo.png
new file mode 100644
index 0000000000..6bdec32359
Binary files /dev/null and b/quickstarts/mern/logo.png differ
diff --git a/quickstarts/mevn/config.yml b/quickstarts/mevn/config.yml
new file mode 100644
index 0000000000..e204c73a75
--- /dev/null
+++ b/quickstarts/mevn/config.yml
@@ -0,0 +1,59 @@
+id: 28967bd0-fe5a-4482-9f1f-49ef042db9f1
+
+# Name of the quickstart
+slug: mevn-stack
+
+# Title of the quickstart
+title: MEVN Stack
+
+summary: |
+ Monitor your apps using New Relic MEVN integration with Vue, MongoDB and NodeJS agents for browser, database and application monitoring.
+
+# Description of the quickstart
+description: |
+ ## Comprehensive MEVN Stack Monitoring System
+ MEVN stack is a popular Javascript software stack that has become very popular in recent times to build powerful web applications. It comprises four essential components, namely MongoDB, ExpressJS, Vue, and NodeJS. These components integrate seamlessly and logically, making it easy to create web applications using this powerful technology stack. Each of these four components has a crucial role to play in the development of web applications.
+
+ ## What’s included in the MEVN quickstart?
+ Install this quickstart to setup preconfigured observability solutions:
+ - MongoDB metrics such as active connections, database details, and usage time
+ - For ExpressJS and NodeJS, there are a variety of metrics available, including web transactions, the top ten errors, and memory usage
+ - Vue metrics include viewed urls, page views by city, AJAX requests, etc. In addition, you may create your own chart based on the metrics collected
+ - A number of high-value alerts are available including the average number of connections created, the FCP score and memory usage
+
+# The logo of the quickstart
+icon: logo.png
+
+# Support level
+level: New Relic
+
+# Authors of the quickstart
+authors:
+ - New Relic
+ - Ramana Reddy
+
+keywords:
+ - MEVN
+ - MongoDB
+ - ExpressJS
+ - Vue
+ - NodeJS
+ - Fullstack application monitoring
+ - browser agent
+ - language agent
+ - featured
+
+dashboards:
+ - mexn
+alertPolicies:
+ - mexn
+documentation:
+ - name: MEVN Stack installation documentation
+ description: |
+ Integrate your MEVN app and get your data into New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/browser/browser-integrations/mexn-integration/
+dataSourceIds:
+ - node-js
+ - new-relic-browser
+ - mongodb
diff --git a/quickstarts/mevn/logo.png b/quickstarts/mevn/logo.png
new file mode 100644
index 0000000000..d0a599e422
Binary files /dev/null and b/quickstarts/mevn/logo.png differ
diff --git a/quickstarts/milvus/config.yml b/quickstarts/milvus/config.yml
new file mode 100644
index 0000000000..cedc41353d
--- /dev/null
+++ b/quickstarts/milvus/config.yml
@@ -0,0 +1,49 @@
+id: 2270ea63-1da5-4503-ae43-140b0e5f4f77
+slug: milvus
+description: |
+ ## Why should you monitor your usage of Milvus?
+
+ Monitor your vector searches on Milvus to get visibility on what you send to Milvus, responses retrieved from Milvus, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Milvus quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Milvus
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - milvus
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/milvus/logo.png b/quickstarts/milvus/logo.png
new file mode 100644
index 0000000000..bfc85e9b1f
Binary files /dev/null and b/quickstarts/milvus/logo.png differ
diff --git a/quickstarts/mlops/bring-your-own/config.yml b/quickstarts/mlops/bring-your-own/config.yml
index f40f1d6202..97a4c0bdf5 100644
--- a/quickstarts/mlops/bring-your-own/config.yml
+++ b/quickstarts/mlops/bring-your-own/config.yml
@@ -24,3 +24,5 @@ documentation:
description: Documentation on how to bring your own ML data
icon: logo.svg
website: https://github.com/newrelic-experimental/ml-performance-monitoring
+alertPolicies:
+ - bring-your-own-data
diff --git a/quickstarts/mlops/google-jax/config.yml b/quickstarts/mlops/google-jax/config.yml
new file mode 100644
index 0000000000..ddc0619ae8
--- /dev/null
+++ b/quickstarts/mlops/google-jax/config.yml
@@ -0,0 +1,50 @@
+id: 07fbb1f8-28e8-494d-b795-495fa5d29587
+slug: google-jax
+description: |
+ ## Why should you monitor Google JAX?
+ Google JAX is an open-source machine learning library widely employed to develop and train neural network-based deep learning models. New Relic's Google JAX quickstart performance monitoring provides out-of-the-box observability for Google JAX models.
+ By using the Google JAX quickstart, you will be able to:
+ ### Identify performance bottlenecks:
+ Enhance the efficiency of your Google JAX models by pinpointing and optimizing performance-heavy areas.
+ ### Ensure model accuracy:
+ Monitor the output of your models in real-time to detect and correct discrepancies, thereby ensuring the desired model performance.
+ ### Error identification and resolution:
+ Active monitoring allows for quick detection and rectification of errors, ensuring the reliability and robustness of your Google JAX models.
+ ## Comprehensive monitoring quickstart for Google JAX models
+ With New Relic's Google JAX quickstart, you can actively oversee the performance of your Google JAX models, gaining insights to ensure they run effectively and efficiently, especially in real-world deep learning applications.
+
+ ## What’s included in the Google JAX quickstart?
+ New Relic Google JAX monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your Google JAX models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use New Relic quickstart to monitor and analyze your Google JAX models.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: Google JAX
+documentation:
+ - name: Google JAX integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Google JAX models, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - google jax
+ - jax
+ - torch
+ - py torch
+ - python
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - ai
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
diff --git a/quickstarts/mlops/google-jax/logo.png b/quickstarts/mlops/google-jax/logo.png
new file mode 100644
index 0000000000..3a615d6584
Binary files /dev/null and b/quickstarts/mlops/google-jax/logo.png differ
diff --git a/quickstarts/mlops/keras/config.yml b/quickstarts/mlops/keras/config.yml
new file mode 100644
index 0000000000..e386009de2
--- /dev/null
+++ b/quickstarts/mlops/keras/config.yml
@@ -0,0 +1,47 @@
+id: 0f6fe78c-27fd-45aa-b375-7384f42eccf4
+slug: keras
+description: |
+ ## Why monitor your Keras models during inference?
+ Once Keras models are trained and deployed, monitoring during the inference phase becomes paramount for various reasons:
+ ### Improve performance:
+ Inference, especially with large models, can be computationally intensive. Monitoring metrics like inference latency, memory usage, and GPU utilization can identify bottlenecks, allowing for necessary optimizations.
+ ### Model health:
+ Over time, the distribution of input data might change, a phenomenon known as data drift. Monitoring allows for the early detection of such scenarios, ensuring the model remains robust and accurate.
+ ### Data quality:
+ As models make predictions on new, unseen data, ensuring the quality and consistency of input data is vital. Monitoring can help detect anomalies or inconsistencies in real-time data that could adversely affect model output.
+
+ ## Comprehensive monitoring for Keras models during inference
+ Properly monitoring your Keras models during the inference phase ensures optimal performance and sustained accuracy. Tracking key metrics will help maintain model health and swiftly detect potential issues.
+
+ ## What’s included in the Keras monitoring quickstart?
+ The New Relic Keras monitoring quickstart offers specialized out-of-the-box reporting for inference:
+ - Real-time visibility: Gain insights into the performance of your Keras models, tracking metrics like inference latency and throughput in real-time.
+ - Data Integrity Checks: Ensure that the input data for inference aligns with expected formats and does not have any anomalies that could affect model outputs.
+ - Proactive alerts: Receive immediate notifications about critical issues affecting your Keras model's performance or reliability during inference.
+ - Resource Utilization: Monitor the computational resources (CPU, GPU, memory) being used during the inference process to optimize deployments and control costs.
+summary: |
+ Boost the performance of your Keras models by integrating with New Relic, providing comprehensive monitoring and optimization for the entire inference process.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Keras
+documentation:
+ - name: Keras integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Keras models, and ensure that your monitoring data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - keras
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+ - ai
+alertPolicies:
+ - bring-your-own-data
\ No newline at end of file
diff --git a/quickstarts/mlops/keras/logo.png b/quickstarts/mlops/keras/logo.png
new file mode 100644
index 0000000000..eab70a3041
Binary files /dev/null and b/quickstarts/mlops/keras/logo.png differ
diff --git a/quickstarts/mlops/langchain/config.yml b/quickstarts/mlops/langchain/config.yml
new file mode 100644
index 0000000000..361fec280f
--- /dev/null
+++ b/quickstarts/mlops/langchain/config.yml
@@ -0,0 +1,55 @@
+id: 74d4643a-7e19-43fc-81eb-e272f7bf0882
+slug: langchain
+description: |
+ ## Why monitor your LangChain application?
+ LangChain is a framework for developing applications powered by language models. By monitoring your LangChain app, we are providing you visibility on the chains, tools as well as inputs and outputs.
+ By using the LangChain quickstart, you will be able to:
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ## Comprehensive monitoring quickstart for your LangChain app
+ Our LangChain quickstart provides metrics including error rate, input & output, latency, queries, retrieved document content and lets you integrate with different LLM providers and vector stores.
+
+ ## What’s included in this quickstart?
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+ - LLM calls and chains
+ - Tools
+ - Vector searches
+ - Alerts for errors, requests per model, and response time
+summary: |
+ Improve your LangChain app's performance with New Relic LangChain quickstart.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: LangChain
+documentation:
+ - name: LangChain integration documentation
+ description: |
+ Implement monitoring and instrumentation for your LangChain app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - langchain
+ - langchain ai
+ - lang
+ - chain
+ - ai
+ - lang chain
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - NR1_addData
+ - mlops
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/mlops/langchain/logo.png b/quickstarts/mlops/langchain/logo.png
new file mode 100644
index 0000000000..240e64b569
Binary files /dev/null and b/quickstarts/mlops/langchain/logo.png differ
diff --git a/quickstarts/mlops/lightgbm/config.yml b/quickstarts/mlops/lightgbm/config.yml
new file mode 100644
index 0000000000..33467fb02f
--- /dev/null
+++ b/quickstarts/mlops/lightgbm/config.yml
@@ -0,0 +1,49 @@
+id: 3928ad94-68db-4201-a732-fb851dc52547
+slug: lightgbm
+description: |
+ ## Why should you monitor LightGBM?
+ LightGBM is an open-source machine learning library widely employed to develop and train neural network-based deep learning models. New Relic's LightGBM quickstart performance monitoring provides out-of-the-box observability for LightGBM models.
+ By using the LightGBM quickstart, you will be able to:
+ ### Identify performance bottlenecks:
+ Enhance the efficiency of your LightGBM models by pinpointing and optimizing performance-heavy areas.
+ ### Ensure model accuracy:
+ Monitor the output of your models in real-time to detect and correct discrepancies, thereby ensuring the desired model performance.
+ ### Error identification and resolution:
+ Active monitoring allows for quick detection and rectification of errors, ensuring the reliability and robustness of your LightGBM models.
+ ## Comprehensive monitoring quickstart for LightGBM models
+ With New Relic's LightGBM quickstart, you can actively oversee the performance of your LightGBM models, gaining insights to ensure they run effectively and efficiently, especially in real-world deep learning applications.
+
+ ## What’s included in the LightGBM quickstart?
+ New Relic LightGBM monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your LightGBM models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use New Relic quickstart to monitor and analyze your LightGBM models.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: LightGBM
+documentation:
+ - name: LightGBM integration documentation
+ description: |
+ Implement monitoring and instrumentation for your LightGBM models, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - lightgbm
+ - ai
+ - torch
+ - py torch
+ - python
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
\ No newline at end of file
diff --git a/quickstarts/mlops/lightgbm/logo.png b/quickstarts/mlops/lightgbm/logo.png
new file mode 100644
index 0000000000..48c9fcf5dc
Binary files /dev/null and b/quickstarts/mlops/lightgbm/logo.png differ
diff --git a/quickstarts/mlops/pytorch/config.yml b/quickstarts/mlops/pytorch/config.yml
new file mode 100644
index 0000000000..a7b46a1a2f
--- /dev/null
+++ b/quickstarts/mlops/pytorch/config.yml
@@ -0,0 +1,50 @@
+id: 23a25d27-cafd-410d-a04c-209ee1281ed9
+slug: pytorch
+description: |
+ ## Why should you monitor PyTorch?
+ PyTorch is an open-source machine learning library widely employed to develop and train neural network-based deep learning models. New Relic's PyTorch quickstart performance monitoring provides out-of-the-box observability for PyTorch models.
+ By using the PyTorch quickstart, you will be able to:
+ ### Identify performance bottlenecks:
+ Enhance the efficiency of your PyTorch models by pinpointing and optimizing performance-heavy areas.
+ ### Ensure model accuracy:
+ Monitor the output of your models in real-time to detect and correct discrepancies, thereby ensuring the desired model performance.
+ ### Error identification and resolution:
+ Active monitoring allows for quick detection and rectification of errors, ensuring the reliability and robustness of your PyTorch models.
+ ## Comprehensive monitoring quickstart for PyTorch models
+ With New Relic's PyTorch quickstart, you can actively oversee the performance of your PyTorch models, gaining insights to ensure they run effectively and efficiently, especially in real-world deep learning applications.
+
+ ## What’s included in the PyTorch quickstart?
+ New Relic PyTorch monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your PyTorch models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use New Relic quickstart to monitor and analyze your PyTorch models.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: PyTorch
+documentation:
+ - name: PyTorch integration documentation
+ description: |
+ Implement monitoring and instrumentation for your PyTorch models, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - pytorch
+ - pytorch ai
+ - torch
+ - py torch
+ - python
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
\ No newline at end of file
diff --git a/quickstarts/mlops/pytorch/logo.png b/quickstarts/mlops/pytorch/logo.png
new file mode 100644
index 0000000000..3acc6f0f3a
Binary files /dev/null and b/quickstarts/mlops/pytorch/logo.png differ
diff --git a/quickstarts/mlops/sagemaker/config.yml b/quickstarts/mlops/sagemaker/config.yml
deleted file mode 100644
index 528bc36032..0000000000
--- a/quickstarts/mlops/sagemaker/config.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-id: cee03961-f9e3-46e1-89fd-70a626cfe8ce
-slug: mlops-sagemaker
-title: Amazon SageMaker
-description: |
- Use this integration to quickly monitor your Amazon SageMaker metrics and objects (sent to AWS CloudWatch) and view them as entities and dashboards in New Relic One.
-summary: |
- By integrating Amazon SageMaker telemetry into New Relic One you will be able to get a view of the performance metrics, visualize sophisticated ML models and create a comprehensive monitoring dashboards in New Relic for your ML models and applications pipelines.
-level: New Relic
-authors:
- - New Relic
-keywords:
- - mlops
- - ml
- - ai
- - sagemaker
- - amazon-sagemaker
- - aws-sagemaker
- - machine-learning
-installPlans:
- - third-party-amazon-sagemaker
-dataSourceIds:
- - amazon-sagemaker
-documentation:
- - name: Sagemaker Docs
- url: https://docs.newrelic.com/docs/mlops/integrations/aws-sagemaker-mlops-integration/
- description: |
- Documentation on the Amazon SageMaker integration
-icon: logo.svg
-website: https://aws.amazon.com/sagemaker/
diff --git a/quickstarts/mlops/sagemaker/logo.svg b/quickstarts/mlops/sagemaker/logo.svg
deleted file mode 100644
index 542ea19dd3..0000000000
--- a/quickstarts/mlops/sagemaker/logo.svg
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
\ No newline at end of file
diff --git a/quickstarts/mlops/scikit-learn/config.yml b/quickstarts/mlops/scikit-learn/config.yml
new file mode 100644
index 0000000000..ae9c3efed9
--- /dev/null
+++ b/quickstarts/mlops/scikit-learn/config.yml
@@ -0,0 +1,49 @@
+id: 078db030-c128-4f61-b24b-2080fafcec55
+slug: scikit-learn
+description: |
+ ## The Importance of Monitoring scikit-learn Models in Production
+ scikit-learn is a widely-used machine learning library in the Python ecosystem. When deploying these models in production environments, continuous monitoring during inference becomes essential for several key reasons:
+ ### Performance optimization:
+ By keeping an eye on your models, you can detect and rectify performance bottlenecks, ensuring that predictions are made efficiently and promptly.
+ ### Early detection of issues:
+ Through vigilant monitoring, problems such as delayed inference times or unexpected outputs can be identified early on, allowing for swift interventions and minimal service disruption.
+ ### Assured Reliability:
+ Active monitoring guarantees that the scikit-learn models remain dependable, reinforcing user trust in the predictions and insights provided.
+
+ ## Comprehensive monitoring quickstart for scikit-learn
+ By placing emphasis on real-time monitoring during the inference phase, you not only ensure the efficacy of your training but also guarantee that your scikit-learn models are robust and reliable when serving users.
+
+ ## What’s included in the scikit-learn quickstart?
+ New Relic scikit-learn monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your scikit-learn models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use the New Relic scikit-learn quickstart to improve the performance of your scikit-learn.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: scikit-learn
+documentation:
+ - name: scikit-learn integration documentation
+ description: |
+ Implement monitoring and instrumentation for your scikit-learn, and ensure that your scikit-learn's data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - scikit-learn
+ - scikit-learn ai
+ - scitkit learn
+ - scikit
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
\ No newline at end of file
diff --git a/quickstarts/mlops/scikit-learn/logo.png b/quickstarts/mlops/scikit-learn/logo.png
new file mode 100644
index 0000000000..ced1931f66
Binary files /dev/null and b/quickstarts/mlops/scikit-learn/logo.png differ
diff --git a/quickstarts/mlops/tensorflow/config.yml b/quickstarts/mlops/tensorflow/config.yml
new file mode 100644
index 0000000000..112b8986a8
--- /dev/null
+++ b/quickstarts/mlops/tensorflow/config.yml
@@ -0,0 +1,50 @@
+id: 0aac0df6-057e-48d4-890d-283b9b8ee190
+slug: tensorflow
+description: |
+ ## Why should you monitor TensorFlow?
+ TensorFlow is an open-source machine learning library widely employed to develop and train neural network-based deep learning models. New Relic's TensorFlow quickstart performance monitoring provides out-of-the-box observability for TensorFlow models.
+ By using the TensorFlow quickstart, you will be able to:
+ ### Identify performance bottlenecks:
+ Enhance the efficiency of your TensorFlow models by pinpointing and optimizing performance-heavy areas.
+ ### Ensure model accuracy:
+ Monitor the output of your models in real-time to detect and correct discrepancies, thereby ensuring the desired model performance.
+ ### Error identification and resolution:
+ Active monitoring allows for quick detection and rectification of errors, ensuring the reliability and robustness of your TensorFlow models.
+ ## Comprehensive monitoring quickstart for TensorFlow models
+ With New Relic's TensorFlow quickstart, you can actively oversee the performance of your TensorFlow models, gaining insights to ensure they run effectively and efficiently, especially in real-world deep learning applications.
+
+ ## What’s included in the TensorFlow quickstart?
+ New Relic TensorFlow monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your TensorFlow models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use New Relic quickstart to monitor and analyze your TensorFlow models.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: TensorFlow
+documentation:
+ - name: TensorFlow integration documentation
+ description: |
+ Implement monitoring and instrumentation for your TensorFlow models, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - tensorflow
+ - tensor flow
+ - torch
+ - py torch
+ - python
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - ai
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
diff --git a/quickstarts/mlops/tensorflow/logo.png b/quickstarts/mlops/tensorflow/logo.png
new file mode 100644
index 0000000000..8a1a9e6a5b
Binary files /dev/null and b/quickstarts/mlops/tensorflow/logo.png differ
diff --git a/quickstarts/mlops/xgboost/config.yml b/quickstarts/mlops/xgboost/config.yml
new file mode 100644
index 0000000000..fca8e5dd00
--- /dev/null
+++ b/quickstarts/mlops/xgboost/config.yml
@@ -0,0 +1,49 @@
+id: 0764ea85-0021-4c47-969e-9d8ec2eb016d
+slug: xgboost
+description: |
+ ## Why should you monitor XGBoost?
+ XGBoost is an open-source machine learning library widely employed to develop and train neural network-based deep learning models. New Relic's XGBoost quickstart performance monitoring provides out-of-the-box observability for XGBoost models.
+ By using the XGBoost quickstart, you will be able to:
+ ### Identify performance bottlenecks:
+ Enhance the efficiency of your XGBoost models by pinpointing and optimizing performance-heavy areas.
+ ### Ensure model accuracy:
+ Monitor the output of your models in real-time to detect and correct discrepancies, thereby ensuring the desired model performance.
+ ### Error identification and resolution:
+ Active monitoring allows for quick detection and rectification of errors, ensuring the reliability and robustness of your XGBoost models.
+ ## Comprehensive monitoring quickstart for XGBoost models
+ With New Relic's XGBoost quickstart, you can actively oversee the performance of your XGBoost models, gaining insights to ensure they run effectively and efficiently, especially in real-world deep learning applications.
+
+ ## What’s included in the XGBoost quickstart?
+ New Relic XGBoost monitoring quickstart provides quality out-of-the-box reporting:
+ - Obtain insights into how your XGBoost models are performing in real-time
+ - Alerts on model performance: Set up proactive notifications for any unusual behavior or degradation in the performance of your models
+
+summary: |
+ Use New Relic quickstart to monitor and analyze your XGBoost models.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: XGBoost
+documentation:
+ - name: XGBoost integration documentation
+ description: |
+ Implement monitoring and instrumentation for your XGBoost models, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic-experimental/ml-performance-monitoring
+dataSourceIds:
+ - bring-your-own-data
+keywords:
+ - xgboost
+ - ai
+ - torch
+ - py torch
+ - python
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - bring-your-own-data
\ No newline at end of file
diff --git a/quickstarts/mlops/xgboost/logo.png b/quickstarts/mlops/xgboost/logo.png
new file mode 100644
index 0000000000..70014b9fe5
Binary files /dev/null and b/quickstarts/mlops/xgboost/logo.png differ
diff --git a/quickstarts/mobile-crash-analytics/config.yml b/quickstarts/mobile-crash-analytics/config.yml
index c5bc06d455..4dd49ab632 100644
--- a/quickstarts/mobile-crash-analytics/config.yml
+++ b/quickstarts/mobile-crash-analytics/config.yml
@@ -12,10 +12,11 @@ description: |
summary: |
Real time mobile application crash & network analysis to ensure ongoing reliability and performance.
level: Community
-icon: logo.png
+icon: icon.png
authors:
- New Relic
- Siddhartha Khare
+ - Ruairi Douglas
keywords:
- dashboard
- mobile-crash
@@ -33,9 +34,14 @@ documentation:
- name: Adding a dashboard
url: https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#get-started
description: How to add a dashboard to New Relic
+ - name: Mobile app Alerts
+ url: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information/
+ description: How to set up alerts for your mobile app
dashboards:
- mobile-crash-analytics
installPlans:
- mobile-dashboard-install
dataSourceIds:
- mobile-getting-started
+alertPolicies:
+ - mobile-crash-analytics
diff --git a/quickstarts/mobile-crash-analytics/icon.png b/quickstarts/mobile-crash-analytics/icon.png
new file mode 100644
index 0000000000..06116828cd
Binary files /dev/null and b/quickstarts/mobile-crash-analytics/icon.png differ
diff --git a/quickstarts/mobile-crash-analytics/logo.png b/quickstarts/mobile-crash-analytics/logo.png
deleted file mode 100644
index 0255bded29..0000000000
Binary files a/quickstarts/mobile-crash-analytics/logo.png and /dev/null differ
diff --git a/quickstarts/mobile-network-performance/config.yml b/quickstarts/mobile-network-performance/config.yml
new file mode 100644
index 0000000000..e233ac1ffe
--- /dev/null
+++ b/quickstarts/mobile-network-performance/config.yml
@@ -0,0 +1,49 @@
+id: 617ced9b-e5ad-4759-bd42-7a4353a26e18
+slug: mobile-network-performance-quickstart
+
+title: Mobile Network Performance
+
+description: |
+ ## Network performance Quickstart
+
+ Get deeper insights into the networking details from your mobile application perspective.
+
+ Receive details about the HTTP errors, Network failure, HTTP Request data, type of network errors.
+
+ Help page on the dashboard will guide you on how to enable data filtering.
+
+summary: |
+ Real time mobile application network analysis to ensure ongoing reliability and performance.
+
+level: Community
+icon: logo.png
+
+authors:
+ - Siddhartha Khare
+
+keywords:
+ - dashboard
+ - mobile-crash
+ - mobile network
+ - mobile agent
+ - HTTP data
+ - android
+ - ios
+ - apps
+
+documentation:
+ - name: Instrument your mobile application with New Relic
+ url: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/introduction-mobile-monitoring/
+ description: How to instrument your mobile application with New Relic
+
+ - name: Adding a dashboard
+ url: https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#get-started
+ description: How to add a dashboard to New Relic
+
+dashboards:
+ - mobile-network-performance
+
+installPlans:
+ - mobile-network-performance-install
+dataSourceIds:
+ - mobile-network-performance-install
diff --git a/quickstarts/mobile-network-performance/logo.png b/quickstarts/mobile-network-performance/logo.png
new file mode 100644
index 0000000000..06116828cd
Binary files /dev/null and b/quickstarts/mobile-network-performance/logo.png differ
diff --git a/quickstarts/mobile/config.yml b/quickstarts/mobile/config.yml
index 04def6754e..fe88037d4e 100644
--- a/quickstarts/mobile/config.yml
+++ b/quickstarts/mobile/config.yml
@@ -2,12 +2,14 @@ id: 4b785b4d-0689-4516-b9db-fbf7227e2e1c
slug: mobile-quickstart
title: Mobile dashboard quickstart
description: |
- A dashboard for basic mobile metrics such as active users, installs and error rate.
+ A dashboard for basic mobile metrics such as app launches and installs, version breakdowns and memory usage.
summary: |
- A dashboard for basic mobile metrics such as active users, installs and error rate.
+ A dashboard for basic mobile metrics such as app launches and installs, version breakdowns and memory usage.
level: Community
authors:
- Víctor Pérez
+ - Ruairi Douglas
+ - Siddhartha Khare
keywords:
- dashboard
- mobile
@@ -22,6 +24,9 @@ documentation:
- name: Adding a dashboard
url: https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/#get-started
description: How to add a dashboard to New Relic
+ - name: Mobile app Alerts
+ url: https://docs.newrelic.com/docs/mobile-monitoring/new-relic-mobile/get-started/mobile-monitoring-alert-information/
+ description: How to set up alerts for your mobile app
icon: icon.png
dashboards:
- mobile
@@ -29,3 +34,6 @@ installPlans:
- mobile-dashboard-install
dataSourceIds:
- mobile-getting-started
+alertPolicies:
+ - mobile
+ - mobile-crash-analytics
diff --git a/quickstarts/mongodb-atlas-vector-search/config.yml b/quickstarts/mongodb-atlas-vector-search/config.yml
new file mode 100644
index 0000000000..b71c3480cf
--- /dev/null
+++ b/quickstarts/mongodb-atlas-vector-search/config.yml
@@ -0,0 +1,58 @@
+id: 5f20a4e7-c554-44dd-8077-7f7d43456915
+slug: mongodb-atlas-vector-search
+description: |
+ ## Why should you monitor your usage of MongoDB Atlas Vector Search?
+ Monitor your vector searches with MongoDB Atlas Vector Search to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of MongoDB Atlas Vector Search
+ Track the behavior of MongoDB Atlas Vector Search. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of MongoDB Atlas Vector Search:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into MongoDB Atlas Vector Search's performance and identify areas of improvement.
+
+ ## Comprehensive monitoring quickstart for MongoDB Atlas Vector Search
+ MongoDB Atlas Vector Search quickstart provides metrics including Identify popular queries, sources, and content.
+
+ ## What’s included in this quickstart?
+ New Relic MongoDB Atlas Vector Search monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your MongoDB Atlas Vector Search app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic MongoDB Atlas Vector Search quickstart
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: MongoDB Atlas Vector Search
+documentation:
+ - name: MongoDB Atlas Vector Search integration documentation
+ description: |
+ Implement monitoring and instrumentation for MongoDB Atlas Vector Search, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - mongodb
+ - atlas vector search
+ - mongodb atlas vector search
+ - vector search
+ - vector database
+ - cloud-based vector search
+ - managed vector search
+ - machine learning
+ - artificial intelligence
+ - AI
+ - ML
+ - NLP
+ - CV
+ - text search
+ - image search
+ - video search
+ - product search
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
diff --git a/quickstarts/mongodb-atlas-vector-search/logo.svg b/quickstarts/mongodb-atlas-vector-search/logo.svg
new file mode 100644
index 0000000000..a8c8bd434d
--- /dev/null
+++ b/quickstarts/mongodb-atlas-vector-search/logo.svg
@@ -0,0 +1,11 @@
+
\ No newline at end of file
diff --git a/quickstarts/mongodb-prometheus/config.yml b/quickstarts/mongodb-prometheus/config.yml
index 91164eac21..80c4d37129 100644
--- a/quickstarts/mongodb-prometheus/config.yml
+++ b/quickstarts/mongodb-prometheus/config.yml
@@ -6,7 +6,7 @@ description: |
MongoDB enables the unlimited virtual scaling of applications. Utilities like mongostat and mongotop offer immediate results but fail to provide insights into trends in a highly graphical visual dashboard. MongoDB dashboards provide insights into key metrics like connections saturation, oplog size, query and document operations, databases and indexes size, collections and transactions latency, replica set and members status.
- Avoid slow queries with proper indexes that impact performance. Instantly monitor your entire MongoDB database with our instant observability kit or the MongoDB free monitoring tool.
+ Avoid slow queries with proper indexes that impact performance. Instantly monitor your entire MongoDB database with our instant observability kit or the MongoDB free monitoring tool.
The critical differences between MongoDB free monitoring and monitoring MongoDB with New Relic’s instant observability quickstart are efficiency, usability, scope, and cost. MongoDB free monitoring focuses on standalone instances and replica sets. Data collected on disk utilization, memory, and operation execution times are uploaded periodically.
@@ -16,7 +16,7 @@ description: |
New Relic + MongoDB quickstart - New Relic’s instant observability quickstart provides multiple metrics related to instances, replica sets, members, databases, and collections.
New Relic’s MongoDB quickstart contains a dashboard with meaningful insights, including:
- - Predefined dashboard filters by Cluster, databases, collections, replica sets, and members.
+ - Predefined dashboard filters by Instance, databases, collections, replica sets, and members.
- Connections saturation, operations by type, databases objects and size, indexes size, commands latency and duration, replica set and member status, and more.
Monitor MongoDB with New Relic to quickly gain improved distribution and increased visibility into real-time user and app response times, throughput and breakdown by component and layer, and long-term data trends over time.
@@ -30,7 +30,7 @@ description: |
New Relic’s instant observability quickstart helps developers reduce administrative overheads and accelerate time to value. As New Relic is SaaS-based, you also don’t have to worry about maintenance or onboarding.
summary: |
- New Relic's MongoDB quickstart provides insights including total commands, requests per second, and database size. Install the quickstart to better understand utilization of resources and monitor performance issues.
+ New Relic's MongoDB quickstart provides insights including total commands, requests per second, and database size. Install the quickstart to better understand the utilization of resources and monitor performance issues.
level: New Relic
icon: logo.jpeg
website: https://www.mongodb.com/
@@ -41,8 +41,6 @@ documentation:
description: |
Open source, document-oriented database where you store data in JSON-like files with dynamic schemas.
url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/mongodb/mongodb-monitoring-integration-new/
-installPlans:
- - mongodb-prometheus-integration-docs
dataSourceIds:
- mongodb-prometheus-integration-docs
keywords:
@@ -50,5 +48,6 @@ keywords:
- database
- featured
- prometheus
+ - mongodb
dashboards:
- mongodb-prometheus
diff --git a/quickstarts/mongodb/config.yml b/quickstarts/mongodb/config.yml
index bdd9506e3d..0d490e2176 100644
--- a/quickstarts/mongodb/config.yml
+++ b/quickstarts/mongodb/config.yml
@@ -48,6 +48,5 @@ dataSourceIds:
keywords:
- infrastructure
- database
- - featured
dashboards:
- mongodb
diff --git a/quickstarts/mosaicml/config.yml b/quickstarts/mosaicml/config.yml
new file mode 100644
index 0000000000..c99914f3e1
--- /dev/null
+++ b/quickstarts/mosaicml/config.yml
@@ -0,0 +1,50 @@
+id: 4b436d48-741d-4092-8be6-d05c836fb827
+slug: mosaicml
+description: |
+ ## Why should you monitor your usage of MosaicML?
+ Monitor your application powered by MosaicML language models to ensure, get visibility to what you send to MosaicML, responses received from MosaicML, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your MosaicML app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive MosaicML monitoring quickstart
+ Our MosaicML quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the MosaicML quickstart?
+ New Relic MosaicML monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your MosaicML usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your MosaicML usage with New Relic MosaicML quickstart.
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+title: MosaicML
+documentation:
+ - name: MosaicML integration documentation
+ description: |
+ Implement monitoring and instrumentation for your MosaicML app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - mosaicml
+ - mosaicml ai
+ - langchain
+ - mlops
+ - large language model
+ - natural language processing
+ - machine learning
+ - artificial intelligence
+ - ai
+ - generative ai
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/mosaicml/logo.svg b/quickstarts/mosaicml/logo.svg
new file mode 100644
index 0000000000..8f6aadb955
--- /dev/null
+++ b/quickstarts/mosaicml/logo.svg
@@ -0,0 +1,38 @@
+
diff --git a/quickstarts/mux-video/config.yml b/quickstarts/mux-video/config.yml
new file mode 100644
index 0000000000..6644d05378
--- /dev/null
+++ b/quickstarts/mux-video/config.yml
@@ -0,0 +1,34 @@
+id: 65bd74f6-cfb7-4fb9-83a3-38cea143d839
+slug: mux-video
+description: |
+ ## What is Mux?
+
+ Mux is video infrastructure for the internet. With just a few lines of code, companies can get real-time analytics at world-leading scale, and understand their streaming data, monitor user engagement, and improve the quality of experience for viewers. Mux is trusted by today’s largest broadcasters and leaders in streaming video to reach their goals with actionable insights. And together with Mux Video, developers can also build video into their products quickly, reliably, and at global scale.
+ Learn more at [mux.com/data](https://mux.com/data)
+
+
+ ### Get started!
+
+ The Mux - New Relic integration utilizes Amazon Kinesis Firehose to get data into New Relic.
+
+ Check out the [documentation](https://docs.newrelic.com/docs/logs/forward-logs/mux-video-streaming-firehose/) to learn more about setting up New Relic monitoring for of data from Mux.
+summary: |
+ Mux is video infrastructure that makes it easy for development teams to get actionable data at industry-leading scale, and build video into their products quickly and reliably.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic (Joseph Counts)
+title: Mux Video Analytics (via Amazon Firehose)
+dataSourceIds:
+ - mux-video
+dashboards:
+ - mux-video-analytics
+documentation:
+ - name: Mux installation docs
+ description: Send Mux logs to New Relic using Amazon Firehose
+ url: https://docs.newrelic.com/docs/logs/forward-logs/mux-video-streaming-firehose/
+keywords:
+ - mux
+ - video
+ - streaming
+ - newrelic partner
diff --git a/quickstarts/mux-video/logo.svg b/quickstarts/mux-video/logo.svg
new file mode 100644
index 0000000000..8ef574f0c4
--- /dev/null
+++ b/quickstarts/mux-video/logo.svg
@@ -0,0 +1,25 @@
+
+
+
diff --git a/quickstarts/myscale/config.yml b/quickstarts/myscale/config.yml
new file mode 100644
index 0000000000..5bc53192de
--- /dev/null
+++ b/quickstarts/myscale/config.yml
@@ -0,0 +1,63 @@
+id: 466de6fd-07b2-4ca8-a105-48b2ec7abeae
+slug: myscale
+description: |
+ ## Why should you monitor your usage of MyScale?
+
+ Monitor your vector searches on MyScale to get visibility on what you send to MyScale, responses retrieved from MyScale, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ MyScale uses the LangChain Vector Database to connect to New Relic. This quickstart provides a variety of a pre-built dashboard, which will help you gain insights into the health and performance of your AI app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor the performance and quality of your vector searches with New Relic MyScale quickstart.
+icon: logo.jpeg
+level: New Relic
+authors:
+ - New Relic
+title: MyScale
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your vector data store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - myscale
+ - vector search
+ - vectordb
+ - vector db
+ - my scale
+ - myscale ai
+ - my scale ai
+ - conversational ai
+ - ai
+ - chatbots
+ - natural language processing
+ - nlp
+ - machine learning
+ - deep learning
+ - aiops
+ - devops
+ - cloud computing
+ - intelligent automation
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/myscale/logo.jpeg b/quickstarts/myscale/logo.jpeg
new file mode 100644
index 0000000000..ef6e2871be
Binary files /dev/null and b/quickstarts/myscale/logo.jpeg differ
diff --git a/quickstarts/netlify/netlify-builds/config.yml b/quickstarts/netlify/netlify-builds/config.yml
index 438b801c6e..e066d719a4 100644
--- a/quickstarts/netlify/netlify-builds/config.yml
+++ b/quickstarts/netlify/netlify-builds/config.yml
@@ -34,7 +34,6 @@ keywords:
- continuous integration
- continuous deployment
- newrelic partner
- - featured
- NR1_addData
- NR1_sys
installPlans:
diff --git a/quickstarts/netlify/netlify-logs/config.yml b/quickstarts/netlify/netlify-logs/config.yml
index 2eea2efdbf..ebb8bf0a73 100644
--- a/quickstarts/netlify/netlify-logs/config.yml
+++ b/quickstarts/netlify/netlify-logs/config.yml
@@ -41,7 +41,6 @@ keywords:
- jamstack
- serverless functions
- newrelic partner
- - featured
- NR1_addData
- NR1_sys
installPlans:
diff --git a/quickstarts/nextcloud/config.yml b/quickstarts/nextcloud/config.yml
index 9ffdb6c804..2510966259 100644
--- a/quickstarts/nextcloud/config.yml
+++ b/quickstarts/nextcloud/config.yml
@@ -2,22 +2,34 @@ id: fe6eb60f-faff-46f9-bf64-666a874ac855
slug: nextcloud
description: |
## Comprehensive monitoring for your Nextcloud server
- You can use New Relic's infrastructure agent to monitor the performance of your Nextcloud server in near real-time, correlate transactions as they move across the app environment, and identify issues to troubleshoot.
- ### Why monitor your Nextcloud server?
- Use the power of our infrastructure monitoring agent and the Prometheus open metric integration to control, monitor, and secure the data on your Nextcloud server. Use our dashboards to get a high-level overview of your server's performance.
- - See a map of your server's processes to help you track down the source of your issues fast.
- - Use our tools to help you maintain quick throughput and low latency on your server.
- - Check the health of your database, application, and server Nextcloud dependencies.
+ Empower yourself with New Relic's cutting-edge Nextcloud monitoring system and gain complete control over the health of your platform. Stay ahead of the curve by monitoring your Nextcloud in real-time, connecting the dots between transactions across your application environment, and swiftly troubleshoot any issues that arise with ease.
+
+ ## Why monitor Nextcloud?
+
+ ### Solve login problems
+ Users may experience issues with logging into their Nextcloud accounts, such as incorrect login credentials or connection errors.
+
+ ### Quickly identify performance issues
+ Nextcloud can become slow or unresponsive, especially if the server is running low on resources or if the network connection is slow.
+
+ ### Identify storage limitations
+ Nextcloud can experience storage limitations if the server's disk space is running low, or if there are issues with the underlying storage infrastructure.
+
+ ### Catch file syncing issues
+ Users may experience issues with file syncing, such as conflict errors or delayed updates, which can result in data loss or corruption.
+
### What’s included?
Use New Relic to monitor and observe your Nextcloud server to:
- Be alerted on things like excessive heap memory usage and scrape errors.
- Use dashboards to monitor crucial performance metrics, such as uptime, free space, total active users, and more.
- Enable your Nextcloud admins to keep track of the status and operation of your server installations.
+
summary: |
- The controllable self-hosted productivity platform. Monitor the server, check the condition of it and keep a watch on what happens to your files with our Infrastructure agent and Prometheus open metric integration.
-icon: logo.png
+ Achieve greater control over your productivity with our self-hosted platform. Stay on top of the performance of your server and ensure the optimal functioning of your system by monitoring it through our Infrastructure agent and utilizing the powerful integration with Prometheus open metrics.
+
level: New Relic
+icon: logo.png
authors:
- New Relic
title: Nextcloud
diff --git a/quickstarts/nr-logs-summary/config.yml b/quickstarts/nr-logs-summary/config.yml
new file mode 100644
index 0000000000..e784f576f3
--- /dev/null
+++ b/quickstarts/nr-logs-summary/config.yml
@@ -0,0 +1,34 @@
+id: 32f0ff6d-4f4e-420e-a042-c0e71e5252fc
+slug: nr-logs-summary
+title: New Relic Logs Summary
+description: |
+ This quickstart contains the following:
+
+ A Log Summary Dashboard that includes tabs for:
+ - Estimates on overall ingestion by partition, along with ingest estimates based on various attributes for log type, source, etc.
+ - Breakdown of logs by well known attributes such as logtype, filePath, level, etc.
+ - APM Log details (logs received by our APM agents)
+ - Logging related NRIntegration errors
+
+ A pre-built alert for Logging NrIntegration Errors
+ - An alert that fires when a Logging NrIntegration error is detected in a 5m window.
+ - Modify the threshold based on your environment / preferences.
+summary: |
+ Get better insights into your logs.
+level: New Relic
+authors:
+ - Marcel Schlapfer
+keywords:
+ - logs
+ - APM
+dataSourceIds:
+ - guided-install
+documentation:
+ - name: Get started with log management
+ url: https://docs.newrelic.com/docs/logs/get-started/get-started-log-management/
+ description: Get started with log management
+icon: logo.svg
+dashboards:
+ - nr-logs-summary
+alertPolicies:
+ - nr-logs-summary
diff --git a/quickstarts/nr-logs-summary/logo.svg b/quickstarts/nr-logs-summary/logo.svg
new file mode 100644
index 0000000000..ea60419c6b
--- /dev/null
+++ b/quickstarts/nr-logs-summary/logo.svg
@@ -0,0 +1,13 @@
+
diff --git a/quickstarts/nr-reports/config.yml b/quickstarts/nr-reports/config.yml
new file mode 100644
index 0000000000..a681c55ad6
--- /dev/null
+++ b/quickstarts/nr-reports/config.yml
@@ -0,0 +1,62 @@
+id: 260438fc-9bbb-4f7a-8a03-930b5a0ae0bc
+# Sets the URL name of the quickstart on public I/O (required)
+slug: nr-reports
+
+# Displayed in the UI (required)
+title: New Relic Reports
+
+# Long-form description of the quickstart (required)
+description: |
+ New Relic Reports is an engine for automating the generation of custom reports
+ built using telemetry in the New Relic Telemetry Data Platform and the delivery
+ of those reports via a variety of channels.
+
+ ## Installation
+
+ Installing New Relic Reports is easy. First make sure you check
+ [the prerequisites](https://github.com/newrelic/nr-reports#prerequisites).
+ Then follow the [installed steps](https://github.com/newrelic/nr-reports#installation).
+
+ ## Getting Started
+
+ Check out [the Getting Started](https://github.com/newrelic/nr-reports#getting-started)
+ documentation to see an example of generating each type of report.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ New Relic Reports is a report generation and automation framework for New Relic.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Scott DeWitt
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - report
+ - reports
+ - custom
+
+# Reference to alert policies to be included in this quickstart
+alertPolicies: []
+
+# Reference to dashboards to be included in this quickstart
+dashboards: []
+
+# Documentation references
+documentation:
+ - name: Installation
+ url: https://github.com/newrelic/nr-reports#installation
+ description: Installing New Relic Reports
+ - name: Getting Started
+ url: https://github.com/newrelic/nr-reports#getting-started
+ description: A tutorial to get you started with New Relic Reports.
+ - name: New Relic Reports Repository
+ url: https://github.com/newrelic/nr-reports
+ description: The New Relic Reports repository.
+
+# Content / Design
+icon: logo.svg
+website: https://github.com/newrelic/nr-reports
diff --git a/quickstarts/nr-reports/logo.svg b/quickstarts/nr-reports/logo.svg
new file mode 100644
index 0000000000..ea60419c6b
--- /dev/null
+++ b/quickstarts/nr-reports/logo.svg
@@ -0,0 +1,13 @@
+
diff --git a/quickstarts/nuxtjs/config.yml b/quickstarts/nuxtjs/config.yml
index 30cf225d37..96c71082be 100644
--- a/quickstarts/nuxtjs/config.yml
+++ b/quickstarts/nuxtjs/config.yml
@@ -40,8 +40,6 @@ documentation:
description: |
Integrate your NuxtJS app with our Vue browser monitoring and get your data into New Relic.
url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/browser-monitoring-integrations/nuxt-js-integration/
-installPlans:
- - nuxtjs
dataSourceIds:
- nuxtjs
dashboards:
diff --git a/quickstarts/nvidia-dcgm/config.yml b/quickstarts/nvidia-dcgm/config.yml
new file mode 100644
index 0000000000..937e1bf5d2
--- /dev/null
+++ b/quickstarts/nvidia-dcgm/config.yml
@@ -0,0 +1,46 @@
+id: 7f86bb7f-0502-418b-aae7-4ad327964874
+slug: nvidia-dcgm
+description: |
+ ## Why monitor NVIDIA DCGM?
+ monitoring NVIDIA DCGM is essential for maintaining the health and efficiency of your GPU infrastructure in a data center. It helps with performance optimization, fault detection, resource management, energy efficiency, and overall data center health, while also aiding in troubleshooting, security, and compliance.
+
+ ## Comprehensive monitoring quickstart for NVIDIA DCGM
+ New Relic comprehensive monitoring of your GPU infrastructure in your data center. This setup will allow you to monitor GPU performance and health while leveraging the capabilities of New Relic for data visualization, alerting, and analysis.
+
+ ## What’s included in this quickstart?
+ New Relic NVIDIA DCGM monitoring quickstart provides quality out-of-the-box reporting:
+ - Dashboards (power usage, GPU utilisation, clocks, etc)
+ - Alerts for NVIDIA DCGM (GPU temperature, Xid error)
+
+
+summary: |
+ Monitor and analyze your NVIDIA DCGM infrastructure with New Relic.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: NVIDIA DCGM
+documentation:
+ - name: NVIDIA DCGM integration documentation
+ description: |
+ Monitor and instrument your NVIDIA DCGM with New Relic to gain deep insights into your performance.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/nvidia-dcgm-integration/
+keywords:
+ - NVIDIA DCGM
+ - AI Acceleration
+ - Machine Learning Acceleration
+ - GPU Management
+ - AI Management
+ - Machine Learning Management
+ - Deep Learning Performance
+ - AI Performance
+ - GPU Optimization
+ - AI Optimization
+ - NR1_addData
+dataSourceIds:
+ - nvidia-dcgm
+dashboards:
+ - nvidia-dcgm
+alertPolicies:
+ - nvidia-dcgm
\ No newline at end of file
diff --git a/quickstarts/nvidia-dcgm/logo.png b/quickstarts/nvidia-dcgm/logo.png
new file mode 100644
index 0000000000..36d7822f35
Binary files /dev/null and b/quickstarts/nvidia-dcgm/logo.png differ
diff --git a/quickstarts/nvidia-gpu/config.yml b/quickstarts/nvidia-gpu/config.yml
new file mode 100644
index 0000000000..ac2c67d986
--- /dev/null
+++ b/quickstarts/nvidia-gpu/config.yml
@@ -0,0 +1,39 @@
+id: 6aa90868-0102-4c56-9493-51e9875c6fdb
+slug: nvidia-gpu
+
+title: Nvidia GPU Monitoring
+
+description: |
+ Our NVIDIA GPU integration assists you in monitoring the status of GPUs.
+ This integration leverages our infrastructure agent and the Flex integration, which is seamlessly integrated with NVIDIA's SMI utility.
+ It provides you with a pre-built dashboard containing crucial GPU metrics, including GPU utilization, ECC error counts,
+ active compute processes, clock and performance states, temperature, fan speed, as well as dynamic and static information about each supported device.
+
+summary: |
+ Monitor NVidia GPUs performance and state.
+
+level: Community
+
+authors:
+ - New Relic
+
+keywords:
+ - nvidia
+ - gpu
+ - infrastructure
+
+documentation:
+ - name: NVIDIA GPU integration
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/nvidia-gpu-integration/
+ description: Monitor the status and performance of NVidia GPUs.
+
+icon: logo.png
+
+dashboards:
+ - nvidia-gpu
+
+alertPolicies:
+ - nvidia-gpu
+
+dataSourceIds:
+ - nvidia-gpu
\ No newline at end of file
diff --git a/quickstarts/nvidia-gpu/logo.png b/quickstarts/nvidia-gpu/logo.png
new file mode 100644
index 0000000000..00e777df8c
Binary files /dev/null and b/quickstarts/nvidia-gpu/logo.png differ
diff --git a/quickstarts/observability-as-code/ansible/config.yml b/quickstarts/observability-as-code/ansible/config.yml
index 291e688e68..e8b4e34c0a 100644
--- a/quickstarts/observability-as-code/ansible/config.yml
+++ b/quickstarts/observability-as-code/ansible/config.yml
@@ -10,12 +10,12 @@ description: |
It uses no agents and no additional custom security infrastructure, so it's easy to deploy - and most importantly, it uses a very simple language (YAML, in the form of Ansible Playbooks) that allow you to describe your automation jobs in a way that approaches plain English.
# What does New Relic provide
- New Relic has developed a Ansible playbook for the Ansible agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
+ New Relic has developed a Ansible role for the Ansible agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/), [New Relic Application Performance Monitoring](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/configure-new-relic-agents/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
# How to get started?
- Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Ansible](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-ansible)
+ Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Ansible](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/configure-infrastructure-agent-using-ansible)
summary: |
- New Relic Ansible playbook to deploy the New Relic Infrastructure agent and On Host Integrations throughout your environment.
+ New Relic Ansible role to deploy the New Relic Infrastructure agent, New Relic APM and On Host Integrations throughout your environment.
level: New Relic
authors:
- New Relic
@@ -33,10 +33,13 @@ documentation:
description: |
Open-source software provisioning, configuration management, and
application-deployment tool enabling infrastructure as code.
- url: https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-ansible
+ url: https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/configure-infrastructure-agent-using-ansible
- name: Ansible Galaxy
description: |
Ansible Galaxy page for the New Relic Ansible role
- url: https://galaxy.ansible.com/newrelic/newrelic_agents
+ url: https://galaxy.ansible.com/newrelic/newrelic_install
+ - name: Github repository
+ description: Github repository for the New Relic Role.
+ url: https://github.com/newrelic/ansible-install
icon: logo.svg
-website: https://galaxy.ansible.com/newrelic/newrelic_agents
+website: https://galaxy.ansible.com/newrelic/newrelic_install
diff --git a/quickstarts/observability-as-code/chef/config.yml b/quickstarts/observability-as-code/chef/config.yml
index 6c9940c3d9..2cd5057689 100644
--- a/quickstarts/observability-as-code/chef/config.yml
+++ b/quickstarts/observability-as-code/chef/config.yml
@@ -8,12 +8,12 @@ description: |
The Chef Infra agent is self-updating, self-automating and works well in low bandwidth or remote environments. It also allows Chef to scale up and down as customers demands change. Security keys are managed and rotated regularly using Chef automated cookbooks which allows admins to turn off port access to SSH and WinRM further securing their environments in line with recommendations from industry standards like CIS (Center for Internet Security) benchmarks.
# What does New Relic provide
- New Relic has developed a Chef recipe for the Chef Infra agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
+ New Relic has developed a Chef recipe for the Chef Infra agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/), [New Relic Application Performance Monitoring](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/configure-new-relic-agents/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
# How to get started?
- Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Chef](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-chef)
+ Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Chef](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-infrastructure-agent-using-chef)
summary: |
- New Relic Chef recipe to deploy the New Relic Infrastructure agent and On Host Integrations throughout your environment.
+ New Relic Chef recipe to deploy the New Relic Infrastructure agent, New Relic APM and On Host Integrations throughout your environment.
level: New Relic
authors:
- New Relic
@@ -29,9 +29,12 @@ dataSourceIds:
documentation:
- name: Chef installation docs
description: Chef is a configuration management tool written in Ruby and Erlang.
- url: https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-chef
+ url: https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/configure-infrastructure-agent-using-chef
- name: Chef Supermarket
description: Chef Supermarket page for the New Relic Chef Recipe
- url: https://supermarket.chef.io/cookbooks/newrelic-infra
+ url: https://supermarket.chef.io/cookbooks/newrelic-install
+ - name: Github repository
+ description: Github repository for the New Relic Cookbook.
+ url: https://github.com/newrelic/chef-install
icon: logo.svg
-website: https://supermarket.chef.io/cookbooks/newrelic-infra
+website: https://supermarket.chef.io/cookbooks/newrelic-install
diff --git a/quickstarts/observability-as-code/puppet/config.yml b/quickstarts/observability-as-code/puppet/config.yml
index 4e8cc7ac73..341f93472a 100644
--- a/quickstarts/observability-as-code/puppet/config.yml
+++ b/quickstarts/observability-as-code/puppet/config.yml
@@ -6,12 +6,12 @@ description: |
Puppet is the industry standard for IT automation. Modernize, manage and bring your hybrid infrastructure into compliance through Puppet's powerful continuous automation.
# What does New Relic provide
- New Relic has developed a Puppet module for the Puppet agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
+ New Relic has developed a Puppet module for the Puppet agent to deploy the [New Relic Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/infrastructure-monitoring/get-started/get-started-infrastructure-monitoring/), [New Relic Application Performance Monitoring](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/configure-new-relic-agents/) and [On Host Integrations](https://docs.newrelic.com/docs/infrastructure/host-integrations/get-started/introduction-host-integrations) throughout your environment.
# How to get started?
- Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Puppet](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-puppet)
+ Follow the instructions on New Relic documentation: [Configure the infrastructure agent using Puppet](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/configure-infrastructure-agent-puppet)
summary: |
- New Relic Puppet module to deploy the New Relic Infrastructure agent and On Host Integrations throughout your environment.
+ New Relic Puppet module to deploy the New Relic Infrastructure agent, New Relic APM and On Host Integrations throughout your environment.
level: New Relic
authors:
- New Relic
@@ -29,9 +29,12 @@ documentation:
description: |
Puppet is a configuration management tool used to manage various stages of
the IT infrastructure lifecycle.
- url: https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-puppet
+ url: https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/configure-infrastructure-agent-puppet
- name: Puppet Forge
description: Puppet Forge page for the New Relic Puppet Module
- url: https://forge.puppet.com/modules/newrelic/newrelic_infra
+ url: https://forge.puppet.com/modules/newrelic/newrelic_installer
+ - name: Github repository
+ description: Github repository for the New Relic Provider.
+ url: https://github.com/newrelic/puppet-install
icon: logo.svg
-website: https://forge.puppet.com/modules/newrelic/newrelic_infra
+website: https://forge.puppet.com/modules/newrelic/newrelic_installer
diff --git a/quickstarts/ollama/config.yml b/quickstarts/ollama/config.yml
new file mode 100644
index 0000000000..cd6d216e24
--- /dev/null
+++ b/quickstarts/ollama/config.yml
@@ -0,0 +1,53 @@
+id: 36968ec7-acef-4b9a-9c6a-3eaaaebdc053
+slug: ollama
+description: |
+ ## Why should you monitor your usage of Ollama?
+ Monitor your application powered by Ollama language models to ensure, get visibility to what you send to Ollama, responses received from Ollama, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive Ollama monitoring quickstart
+ Our Ollama quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the Ollama quickstart?
+ New Relic Ollama monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Ollama usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your Ollama usage with New Relic Ollama quickstart.
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+title: Ollama
+documentation:
+ - name: Ollama integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Ollama app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - ollama
+ - large language model
+ - natural language processing
+ - nlp
+ - machine learning
+ - artificial intelligence
+ - ai
+ - ollama ai
+ - cloud native
+ - llm
+ - llm chains
+ - generative ai
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/ollama/logo.png b/quickstarts/ollama/logo.png
new file mode 100644
index 0000000000..8cd2cf1ed8
Binary files /dev/null and b/quickstarts/ollama/logo.png differ
diff --git a/quickstarts/oma-data-gov/config.yml b/quickstarts/oma-data-gov/config.yml
index b4a5c2ad17..6114b2b229 100644
--- a/quickstarts/oma-data-gov/config.yml
+++ b/quickstarts/oma-data-gov/config.yml
@@ -4,7 +4,7 @@ title: OMA Data Ingest Governance
description: |
Data ingest governance is a practice of ensuring optimal value for telemetry data collected by an organization particularly a complex organization with numerous business units and working groups.
summary: |
- The prerequisite step of data governance includes developing an accurate baseline of your telemetry data ingest levels. A good ingest baseline will break your ingest out by sub-account and telemetry type. This is particularly necessary in a complex organization with numerous business units and working groups.
+ The prerequisite step of data governance includes developing an accurate baseline of your telemetry data ingest levels. A good ingest baseline will break your ingest out by sub-account and telemetry type. This is particularly necessary in a complex organization with numerous business units and working groups.
level: New Relic
authors:
- Jim Hagan
diff --git a/quickstarts/oma-qf/config.yml b/quickstarts/oma-qf/config.yml
index 500afce8b9..f1a2a2fde4 100644
--- a/quickstarts/oma-qf/config.yml
+++ b/quickstarts/oma-qf/config.yml
@@ -34,3 +34,4 @@ icon: logo.svg
website: https://www.newrelic.com
dashboards:
- om-quality-foundation
+ - om-qf-retail-user-journey
diff --git a/quickstarts/openai/config.yaml b/quickstarts/openai/config.yaml
index 578cf36da1..0ca5a62c2b 100644
--- a/quickstarts/openai/config.yaml
+++ b/quickstarts/openai/config.yaml
@@ -7,15 +7,15 @@ description: |
## Monitor your GPT-3 and GPT-4 Application Usage in New Relic
With the GPT integration, you'll have the ability to seamlessly monitor OpenAI completion queries and simultaneously log useful statistics in a New Relic customizable dashboard about your requests.
-
+
By adding just two lines of code, users can gain access to key performance metrics such as cost, response time, and sample inputs/outputs. The dashboard also allows users to track total requests, average token/requests, and model names.
-
+
With New Relic's fully customizable dashboard, users can add additional metrics based on their specific business requirements and needs.
-
+
Overall, New Relic's OpenAI integration provides real-time metrics around GPT applications to help businesses optimize usage, reduce costs, and achieve better results.
summary: |
- Seamlessly monitor your usage of OpenAI’s GPT Series APIs using New Relic’s dashboard. You'll get access to real-time metrics that can help you optimize usage, reduce costs, and achieve better results.
+ Seamlessly monitor your usage of OpenAI’s GPT Series APIs using New Relic’s dashboard. You'll get access to real-time metrics that can help you optimize usage, reduce costs, and achieve better results.
icon: openai-logo.svg
@@ -26,7 +26,7 @@ authors:
- Yogev Kriger
documentation:
- - name: Monitor OpenAI
+ - name: Monitor OpenAI
description: |
A lightweight tool to monitor your OpenAI workload.
url: >-
@@ -37,13 +37,10 @@ keywords:
- openai
- ai
- gpt
- - mlops
-
-installPlans:
- - setup-openai
+ - mlops
+ - llm
dataSourceIds:
- - openai
-
-dashboards:
- - openai
+ - llm-application
+alertPolicies:
+ - llm-application
diff --git a/quickstarts/openllm/config.yml b/quickstarts/openllm/config.yml
new file mode 100644
index 0000000000..ada04acba0
--- /dev/null
+++ b/quickstarts/openllm/config.yml
@@ -0,0 +1,56 @@
+id: 5d5e33d3-f66c-49f1-8b8e-024fb115010b
+slug: openllm
+description: |
+ ## Why should you monitor your usage of OpenLLM?
+ Monitor your application powered by OpenLLM language models to ensure, get visibility to what you send to OpenLLM, responses received from OpenLLM, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your LangChain app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive OpenLLM monitoring quickstart
+ Our OpenLLM quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the OpenLLM quickstart?
+ New Relic OpenLLM monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your OpenLLM usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your OpenLLM usage with New Relic OpenLLM quickstart.
+icon: logo.jpeg
+level:
+ - New Relic
+authors:
+ - New Relic
+title: OpenLLM
+documentation:
+ - name: OpenLLM integration documentation
+ description: |
+ Implement monitoring and instrumentation for your OpenLLM app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - openllm
+ - large language model
+ - natural language processing
+ - nlp
+ - machine learning
+ - artificial intelligence
+ - ai
+ - openllm ai
+ - cloud native
+ - llm
+ - llm chains
+ - deep learning
+ - distributed computing
+ - kubernetes
+ - generative ai
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/openllm/logo.jpeg b/quickstarts/openllm/logo.jpeg
new file mode 100644
index 0000000000..5518e1a6f3
Binary files /dev/null and b/quickstarts/openllm/logo.jpeg differ
diff --git a/quickstarts/openstack-controller/config.yml b/quickstarts/openstack-controller/config.yml
new file mode 100644
index 0000000000..5e5807f55b
--- /dev/null
+++ b/quickstarts/openstack-controller/config.yml
@@ -0,0 +1,43 @@
+id: 68fd037d-8185-4604-853c-fb9a652686d3
+slug: openstack-controller
+description: |
+ ## Why monitor Openstack Controller?
+ Monitoring the OpenStack controller helps you maintain the stability, performance, security, and availability of your cloud environment by detecting issues early, responding promptly, and continuously improving your infrastructure to meet the needs of users and applications.
+
+ ## Comprehensive monitoring quickstart for Openstack Controller
+ New Relic comprehensive monitoring solution collects data from all aspects of your OpenStack environment, so you can see exactly what's happening and identify any potential problems before they impact your users.
+
+ ## What’s included in this quickstart?
+ New Relic Openstack Controller monitoring quickstart provides quality out-of-the-box reporting:
+ - Track the performance of your OpenStack services, such as compute, networking and storage
+ - Identify and troubleshoot performance bottlenecks with ease
+ - Get pre-built alerts when there are problems with your OpenStack environment
+ - Correlate data from different data sources to get a holistic view of your environment
+
+
+summary: |
+ Monitor and analyze your Openstack Controller infrastructure with New Relic.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: Openstack Controller
+documentation:
+ - name: Openstack Controller integration documentation
+ description: |
+ Monitor and instrument your OpenStack Controller with New Relic to gain deep insights into your performance.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/openstack-controller-integration/
+keywords:
+ - openstack controller
+ - openstack
+ - nova controller
+ - neutron controller
+ - cinder controller
+ - Keystone controller
+dataSourceIds:
+ - openstack-controller
+dashboards:
+ - openstack-controller
+alertPolicies:
+ - openstack-controller
\ No newline at end of file
diff --git a/quickstarts/openstack-controller/logo.png b/quickstarts/openstack-controller/logo.png
new file mode 100644
index 0000000000..3f69a04377
Binary files /dev/null and b/quickstarts/openstack-controller/logo.png differ
diff --git a/quickstarts/opslevel/config.yml b/quickstarts/opslevel/config.yml
new file mode 100644
index 0000000000..803b928bed
--- /dev/null
+++ b/quickstarts/opslevel/config.yml
@@ -0,0 +1,57 @@
+id: 6eccea7a-7465-4731-a6fc-fc26ecd4b81f
+# quickstarts/opslevel/config.yml
+
+
+slug: opslevel
+title: OpsLevel
+
+description: |
+ ## What is OpsLevel?
+
+ A developer portal for high-performing engineering teams. Give your engineering team one place to *fix, build, and release high-quality code without operational toil*. Improve speed and standards with the [OpsLevel developer portal](https://www.opslevel.com).
+
+ ### OpsLevel quickstart highlights
+
+ Integrate New Relic with OpsLevel to bring New Relic alert statuses into your OpsLevel developer portal.
+
+ With New Relic in OpsLevel you can:
+ * Set yourself up to avoid incidents, performance issues, or gaps in your observability data streams
+ * Give your team real-time visibility of production status across your software ecosystem
+ * Keep your team informed of alerts and notify the correct people to help resolve them
+
+ ### Get started!
+
+ Check out our [Integration Guide](https://docs.opslevel.com/docs/new-relic-integration) to learn more about connecting New Relic and OpsLevel.
+
+ New to OpsLevel? [Try OpsLevel for free.](https://www.opslevel.com/free-trial?utm_source=referral&utm_medium=website&utm_campaign=nr-integration)
+
+summary: |
+ Be prepared for incidents and solve performance issues faster by combining the complete context in OpsLevel with New Relic’s monitoring capabilities.
+
+# Possible values: New Relic | Verified | Community
+# Please consult with pull request reviewers if you think your quickstart should have a support level other than "Community"
+level: Community
+
+authors:
+ - OpsLevel
+
+# These keywords can be mapped to category terms
+# which help to categorize quickstarts.
+# To have your quickstart appear under a certain category,
+# these keywords must include a matching category term,
+# see link in the keywords row of the table below.
+keywords:
+ - newrelic partner
+ - messaging
+ - opslevel
+
+# Relevant documentation for this quickstart
+documentation:
+ - name: Installation and Usage docs
+ url: >-
+ https://docs.opslevel.com/docs/new-relic-integration
+ description: |
+ Documentation to help you get started with the OpsLevel <> New Relic Integration
+
+# An icon or logo for the quickstart
+icon: logo.svg
diff --git a/quickstarts/opslevel/logo.svg b/quickstarts/opslevel/logo.svg
new file mode 100644
index 0000000000..d1107d66ee
--- /dev/null
+++ b/quickstarts/opslevel/logo.svg
@@ -0,0 +1,26 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/palm-2/config.yml b/quickstarts/palm-2/config.yml
new file mode 100644
index 0000000000..bfdc6a15f7
--- /dev/null
+++ b/quickstarts/palm-2/config.yml
@@ -0,0 +1,51 @@
+id: e3b42f08-2a47-4398-80c7-229f28b2fba1
+slug: palm-2
+description: |
+ ## Why should you monitor your usage of PaLM 2?
+ Monitor your application powered by PaLM 2 language models to ensure, get visibility to what you send to PaLM 2, responses received from PaLM 2, latency, usage and errors. By monitoring the usage, you can infer the cost.
+ ### Track the LLM's performance:
+ Monitor the input & output, latency and errors of your LLM provider. Track performance changes with the providers and versions of your LLM. Monitor usage to understand the cost, rate limits, and general performance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your PaLM 2 app's performance and identify areas of improvement.
+ ### Early issue detection:
+ Detect and address issues early to prevent them from affecting model performance.
+
+ ## Comprehensive PaLM 2 monitoring quickstart
+ Our PaLM 2 quickstart provides metrics including error rate, input & output, latency, queries, and lets you integrate with different language models.
+
+ ## What’s included in the PaLM 2 quickstart?
+ New Relic PaLM 2 monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your PaLM 2 usage. These reports include:
+ - Dashboards (average tokens, LLM completion’s details, chain’s details, tool details, top tool names and many more)
+ - Alerts (errors, request per model and response time)
+summary: |
+ Improve the visibility of your PaLM 2 usage with New Relic PaLM 2 quickstart.
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+title: PaLM 2
+documentation:
+ - name: PaLM 2 integration documentation
+ description: |
+ Implement monitoring and instrumentation for your PaLM 2 app to ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain
+keywords:
+ - palm2
+ - palm 2
+ - langchain
+ - mlops
+ - large language model
+ - natural language processing
+ - nlp
+ - machine learning
+ - artificial intelligence
+ - ai
+ - generative ai
+ - NR1_addData
+alertPolicies:
+ - langchain
+dashboards:
+ - langchain
\ No newline at end of file
diff --git a/quickstarts/palm-2/logo.svg b/quickstarts/palm-2/logo.svg
new file mode 100644
index 0000000000..5c345fe1c1
--- /dev/null
+++ b/quickstarts/palm-2/logo.svg
@@ -0,0 +1,67 @@
+
+
+
diff --git a/quickstarts/pgvector/config.yml b/quickstarts/pgvector/config.yml
new file mode 100644
index 0000000000..ca00f01b7f
--- /dev/null
+++ b/quickstarts/pgvector/config.yml
@@ -0,0 +1,49 @@
+id: 19f7bab8-860b-428c-b7d4-ff6a28f438c3
+slug: pgvector
+description: |
+ ## Why should you monitor your usage of PGVector?
+
+ Monitor your vector searches on PGVector to get visibility on what you send to PGVector, responses retrieved from PGVector, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic PGVector quickstart.
+icon: logo.jpeg
+level: New Relic
+authors:
+ - New Relic
+title: PGVector
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - pgvector
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/pgvector/logo.jpeg b/quickstarts/pgvector/logo.jpeg
new file mode 100644
index 0000000000..8ca5860575
Binary files /dev/null and b/quickstarts/pgvector/logo.jpeg differ
diff --git a/quickstarts/postfix/config.yml b/quickstarts/postfix/config.yml
new file mode 100644
index 0000000000..04c1d0af95
--- /dev/null
+++ b/quickstarts/postfix/config.yml
@@ -0,0 +1,41 @@
+id: d880675c-6c3e-4a81-95f5-0206e46cda6c
+slug: postfix
+description: |
+ ## Postfix queue performance monitoring
+
+ Postfix monitoring involves tracking and analyzing metrics related to the performance, health, and security of a Postfix mail server. This includes monitoring the mail queue, message traffic, error logs, and security. It can also be used to set up dashboards and alerts for monitoring Postfix metrics in real-time. Proper monitoring of Postfix can ensure the smooth operation and security of the mail server.
+
+ ### What should you look for in a Postfix dashboard?
+
+ Postfix monitoring dashboards provide real-time statistics on mail queues, message traffic, resource utilization, error logs, and security.
+
+ ### What’s included in the Postfix quickstart?
+
+ Install this quickstart to install preconfigured observability solutions:
+ - A number of high-value alerts are available, including whenever the Postfix service is down, connections are lost, or connections time out.
+ - Informative dashboards (email delivery process, number of messages bounced and deferred, number of incoming connections, and more).
+
+summary: |
+ Monitor your Postfix with New Relic infrastructure agent and Flex configuration. Get real-time insights into email delivery and performance, including message flows, queue sizes, per-day traffic summaries, per-hour traffic records, and server load.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Postfix
+dashboards:
+ - postfix
+alertPolicies:
+ - postfix
+documentation:
+ - name: Postfix
+ description: |
+ Postfix is a well-known mail server that is used to route and deliver email messages across mail servers.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/postfix-monitoring-integration
+dataSourceIds:
+ - postfix
+keywords:
+ - postfix
+ - mail server
+ - infrastructure
+
\ No newline at end of file
diff --git a/quickstarts/postfix/logo.png b/quickstarts/postfix/logo.png
new file mode 100644
index 0000000000..3a61c656a9
Binary files /dev/null and b/quickstarts/postfix/logo.png differ
diff --git a/quickstarts/postgres-embedding/config.yml b/quickstarts/postgres-embedding/config.yml
new file mode 100644
index 0000000000..bb32ff10cc
--- /dev/null
+++ b/quickstarts/postgres-embedding/config.yml
@@ -0,0 +1,57 @@
+id: 7f885669-3254-4f92-9e44-2c4d8d7d0014
+
+slug: postgres-embedding
+description: |
+ ## Why should you monitor your usage of Postgres Embedding?
+ Monitor your vector searches with Postgres Embedding to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+
+ ### Track the query performance of Postgres Embedding
+ Track the behavior of Postgres Embedding. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of Postgres Embedding
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your Postgres Embedding's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+ Postgres Embedding monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Postgres Embedding. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Postgres Embedding's performance and quality with New Relic Postgres Embedding quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Postgres Embedding
+documentation:
+ - name: Postgres Embedding integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Postgres Embedding, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - pg embedding
+ - postgres embedding
+ - vector embedding
+ - postgreSQL
+ - timescaleDB
+ - machine learning
+ - artificial intelligence
+ - AI
+ - ML
+ - NLP
+ - CV
+ - computer vision
+ - image search
+ - video search
+ - text search
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/postgres-embedding/logo.png b/quickstarts/postgres-embedding/logo.png
new file mode 100644
index 0000000000..849946ef43
Binary files /dev/null and b/quickstarts/postgres-embedding/logo.png differ
diff --git a/quickstarts/public-api-performance/config.yml b/quickstarts/public-api-performance/config.yml
deleted file mode 100644
index 85e11e3f6f..0000000000
--- a/quickstarts/public-api-performance/config.yml
+++ /dev/null
@@ -1,32 +0,0 @@
-id: 7f8e7ef2-d94b-47bc-8d85-31471430b673
-slug: public-api-performance
-title: Public API Performance
-description: |
- ## Public API Performance
-
- Explore the performance data New Relic collects about commonly used, public APIs. Use this dashboard to:
-
- * Determine if a public API you use is experiencing a performance issue
- * Compare the performance of your publicly-available APIs against other services
- * Evaluate the API performance of providers when considering which one(s) to choose
-summary: |
- Explore the performance data New Relic collects about commonly used, public APIs.
-level: New Relic
-authors:
- - New Relic
-keywords:
- - public api
- - performance
- - provider
-installPlans:
- - public-api-performance
-dataSourceIds:
- - public-api-performance
-dashboards:
- - public-api-performance
-documentation:
- - name: Public API Performance Dashboard
- url: https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/explore-public-api-performance-dashboard/
- description: See our documentation for more details on the Public API Performance Dashboard.
-icon: logo.svg
-website: https://www.newrelic.com
diff --git a/quickstarts/public-api-performance/logo.svg b/quickstarts/public-api-performance/logo.svg
deleted file mode 100644
index 8dab573e6e..0000000000
--- a/quickstarts/public-api-performance/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/python/aiohttp/config.yml b/quickstarts/python/aiohttp/config.yml
index 6fd2e4f4b3..2f7d4f11e4 100644
--- a/quickstarts/python/aiohttp/config.yml
+++ b/quickstarts/python/aiohttp/config.yml
@@ -2,21 +2,21 @@ id: e7948525-8726-46a5-83fa-04732ad42fd1
slug: aiohttp
title: AIOHTTP
description: |
- ## AIO HTTP complete monitoring quickstart
+ ## AIOHTTP complete monitoring quickstart
- Instantly monitor Python applications with AIO HTTP quickstart. Our [Python](https://docs.newrelic.com/docs/agents/python-agent/) integration lets you quickly identify and resolve potential performance issues with your AIO HTTP server and enhance user experiences.
+ Instantly monitor Python applications with AIOHTTP quickstart. Our [Python](https://docs.newrelic.com/docs/agents/python-agent/) integration lets you quickly identify and resolve potential performance issues with your AIOHTTP server and enhance user experiences.
- ### Monitoring AIO HTTP
+ ### Monitoring AIOHTTP
- Python application developers can extend AIO HTTP performance monitoring to collect, clean, and analyze data to make better data-driven business decisions. Monitoring is vital to ensure uptime and data reliability by keeping an eye on the AIO HTTP server and AIO HTTP client.
+ Python application developers can extend AIOHTTP performance monitoring to collect, clean, and analyze data to make better data-driven business decisions. Monitoring is vital to ensure uptime and data reliability by keeping an eye on the AIOHTTP server and AIOHTTP client.
- New Relic's AIO HTTP quickstart provides dashboards and built-in instrumentation to track AIO HTTP requests, CPU utilization, garbage collection CPU time, memory heap used, most popular transactions, throughput reports, top 5 slowest transactions, and more.
+ New Relic's AIOHTTP quickstart provides dashboards and built-in instrumentation to track AIOHTTP requests, CPU utilization, garbage collection CPU time, memory heap used, most popular transactions, throughput reports, top 5 slowest transactions, and more.
Count on real-time alerts to apdex scores, CPU utilization, and transaction errors. Expand the Python agent's default monitoring and behavior through the agent API or agent config file and target additional activity and functional calls.
- ### New Relic - The complete AIO HTTP dashboard tool
+ ### New Relic - The complete AIOHTTP dashboard tool
- The AIO HTTP dashboard tool ensures total visibility into critical metrics, leveraging dashboards and synthetic checks. With APIs and flexible custom instrumentation options, developers can use multiple building blocks to improve performance and adapt data for your app.
+ The AIOHTTP dashboard tool ensures total visibility into critical metrics, leveraging dashboards and synthetic checks. With APIs and flexible custom instrumentation options, developers can use multiple building blocks to improve performance and adapt data for your app.
#### What's included?
@@ -25,8 +25,8 @@ description: |
Know what's happening in real-time by tracking CPU utilization, throughput reports, and popular transactions with full-stack observability of your entire infrastructure.
- With the AIO HTTP complete monitoring quickstart, you can remediate errors before they impact user experience.
-summary: New Relic's AIO HTTP complete monitoring quickstart offers dashboards, alerts, and custom instrumentation to track the health and performance of your Python application before it impacts user experience.
+ With the AIOHTTP complete monitoring quickstart, you can remediate errors before they impact user experience.
+summary: New Relic's AIOHTTP complete monitoring quickstart offers dashboards, alerts, and custom instrumentation to track the health and performance of your Python application before it impacts user experience.
icon: logo.svg
level: New Relic
authors:
diff --git a/quickstarts/python/python/config.yml b/quickstarts/python/python/config.yml
index 466caf70f6..514abbbd69 100644
--- a/quickstarts/python/python/config.yml
+++ b/quickstarts/python/python/config.yml
@@ -48,12 +48,11 @@ documentation:
description: |
Python is an interpreted, high-level and general-purpose programming
language.
- url: https://docs.newrelic.com/docs/agents/python-agent/getting-started/compatibility-requirements-python-agent
+ url: https://docs.newrelic.com/docs/apm/agents/python-agent/getting-started/introduction-new-relic-python/
keywords:
- apm
- python
- language agent
- - featured
installPlans:
- setup-python-agent
dataSourceIds:
diff --git a/quickstarts/qdrant/config.yml b/quickstarts/qdrant/config.yml
new file mode 100644
index 0000000000..81ee050047
--- /dev/null
+++ b/quickstarts/qdrant/config.yml
@@ -0,0 +1,47 @@
+id: 1223a0ff-689d-4102-ae8b-3e2c3a04c171
+slug: qdrant
+description: |
+ ## Why should you monitor your usage of Qdrant?
+ Monitor your vector searches on Qdrant to get visibility on what you send to Qdrant, responses retrieved from Qdrant, latency, usage and errors.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ## Comprehensive monitoring quickstart for your Qdrant app
+ Our Qdrant quickstart provides metrics including Identify popular queries, sources, and content.
+
+ ## What’s included in this quickstart?
+ New Relic Qdrant monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Qdrant app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Qdrant quickstart
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: Qdrant
+documentation:
+ - name: Qdrant integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - Qdrant
+ - langchain
+ - vector store
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/qdrant/logo.png b/quickstarts/qdrant/logo.png
new file mode 100644
index 0000000000..e1cfe25520
Binary files /dev/null and b/quickstarts/qdrant/logo.png differ
diff --git a/quickstarts/redis-otel/config.yml b/quickstarts/redis-otel/config.yml
new file mode 100644
index 0000000000..02dd9d35a8
--- /dev/null
+++ b/quickstarts/redis-otel/config.yml
@@ -0,0 +1,30 @@
+id: 6d07c47a-6b4d-4369-98c5-3736ec6d2000
+slug: redis-otel
+title: Redis (OpenTelemetry)
+summary: |
+ Monitoring Redis is essential for maintaining fast database operations and a responsive application. Install New Relic Redis for OpenTelemetry quickstart to proactively instrument Redis with the OpenTelemetry Redis receiver.
+description: |
+ ## How to monitor Redis with New Relic?
+ The OpenTelemetry Redis receiver collects metrics from your running Redis instances. These metrics provide insights into operations, memory usage, client connections, and more.
+ A New Relic entity will be created for each Redis instance, allowing you to easily explore, configure alerts, and compare metrics for all your Redis databases in one place.
+ Our monitoring quickstart includes a pre-built dashboard that displays aggregated metrics from all of your Redis instances, with the ability to filter the data for specific analyses.
+ ### Why monitor Redis with New Relic?
+ New Relic Redis for OpenTelemetry quickstart gives you comprehensive visibility into your Redis databases alongside your apps and server infrastructure. Monitoring Redis is vital to obtain real-time performance metrics for databases across your entire environment. This ensures optimal database operations, leading to better application performance and enhanced user experiences.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+dataSourceIds:
+ - redis-otel
+alertPolicies:
+ - redis-otel
+documentation:
+ - name: Redis (OpenTelemetry) installation docs
+ description: |
+ Redis is an in-memory data structure store, used as a database, cache, and message broker. Monitoring it provides insights into its operations and performance.
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-redis
+
+keywords:
+ - open telemetry
+ - redis
+ - infrastructure
diff --git a/quickstarts/redis-otel/logo.svg b/quickstarts/redis-otel/logo.svg
new file mode 100644
index 0000000000..ed312206b9
--- /dev/null
+++ b/quickstarts/redis-otel/logo.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/quickstarts/redmine/config.yml b/quickstarts/redmine/config.yml
index 6741c174c7..7829787502 100644
--- a/quickstarts/redmine/config.yml
+++ b/quickstarts/redmine/config.yml
@@ -5,7 +5,7 @@ description: |
We can monitor your Redmine application in a complex environment and keep you on top of performance with our Ruby agent.
## Why monitor Redmine?
- Redmine is a popular open-source project management and issue tracking tool, but like any software, it can also have some issues. Our quickstart helps you catch those quickly and effortlessly. ## Why monitor your Redmine app?
+ Redmine is a popular open-source project management and issue tracking tool, but like any software, it can also have some issues. Our quickstart helps you catch those quickly and effortlessly.
### Slow performance
Redmine can become slow and unresponsive with a large number of projects, issues, and users, requiring optimization and maintenance to keep it running smoothly.
@@ -49,6 +49,7 @@ keywords:
- redmine
- ruby agent
- ruby
+
installPlans:
- redmine
dataSourceIds:
diff --git a/quickstarts/redpanda/config.yml b/quickstarts/redpanda/config.yml
index ee4f5def2f..0d7da5f602 100644
--- a/quickstarts/redpanda/config.yml
+++ b/quickstarts/redpanda/config.yml
@@ -14,7 +14,7 @@ description: |
Identify high latency in processing to solve for overall platform performance.
### Data loss
- Our node dashboard alerts you immediately in case of failures, to prevent data loss by quick intervention.
+ Our quickstart dashboard alerts you immediately in case of failures, to prevent data loss by quick intervention.
Redpanda observability is essential for ensuring its reliability, availability, and performance, and for preventing and resolving issues.
@@ -35,8 +35,6 @@ documentation:
description: |
New Relic’s instant observability quickstart with Redpanda monitoring helps to detect your metrics which are useful for debugging and measuring system health.
url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/redpanda-integration/
-installPlans:
- - redpanda
dataSourceIds:
- redpanda
keywords:
diff --git a/quickstarts/resmo/config.yml b/quickstarts/resmo/config.yml
new file mode 100644
index 0000000000..78b610d05a
--- /dev/null
+++ b/quickstarts/resmo/config.yml
@@ -0,0 +1,40 @@
+id: 1f7fdf81-5d61-4f6a-9cd4-6c72d73df8e7
+slug: resmo
+description: |
+ ## What is Resmo?
+ Resmo provides a comprehensive solution for continuous cyber asset visibility and security to cloud-native teams. By allowing SQL-based data queries across a range of Cloud and SaaS providers, Resmo enables customers to stay informed of any changes. Resmo consolidates users, vulnerabilities, repositories, and other essential elements to provide valuable insights through user-friendly dashboards and automates compliance checks for frameworks such as CIS benchmarks. This alerts customers to potential security vulnerabilities.
+
+ ### How this integration works
+
+ Once you sign up to Resmo, you can easily integrate your account with New Relic using an API key. Resmo uses an API to do the initial polling and collect existing resources. Then, we receive resource changes and updates in real-time by regular polling.
+
+ ### What does this integration offer
+
+ With this integration you can:
+ - Gather and monitor all your New Relic assets on a single platform.
+ - Query your New Relic dashboards, accounts, alert policies, API keys, and more.
+ - Set up rules to continuously assess your New Relic resources.
+ - Set up and receive rule notifications based on your New Relic resource configurations.
+
+
+summary: |
+ Resmo is a cyber asset visibility and security solution for cloud-native teams, enabling discovery, security, and compliance across Cloud and SaaS platforms.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+ - Resmo
+title: Resmo
+documentation:
+ - name: Resmo installation docs
+ description: Integrate your Resmo account with New Relic using an API key.
+ url: >-
+ https://docs.resmo.com/product/integrations/new-relic-integration
+keywords:
+ - resmo
+ - newrelic partner
+ - assets
+ - rules
+ - notifications
+ - resource configurations
+
diff --git a/quickstarts/resmo/logo.svg b/quickstarts/resmo/logo.svg
new file mode 100644
index 0000000000..a8348d6a2d
--- /dev/null
+++ b/quickstarts/resmo/logo.svg
@@ -0,0 +1,8 @@
+
diff --git a/quickstarts/roku/config.yml b/quickstarts/roku/config.yml
index 906bdcfac0..b84c4d958f 100644
--- a/quickstarts/roku/config.yml
+++ b/quickstarts/roku/config.yml
@@ -29,7 +29,6 @@ keywords:
- tracker
- roku
- brightscript
- - featured
installPlans:
- third-party-roku
- third-party-roku-http-analytics
diff --git a/quickstarts/sendgrid/config.yml b/quickstarts/sendgrid/config.yml
index 67d5525f35..555ef18f2e 100644
--- a/quickstarts/sendgrid/config.yml
+++ b/quickstarts/sendgrid/config.yml
@@ -28,3 +28,4 @@ icon: logo.png
website: https://sendgrid.com/
dashboards:
- sendgrid-dashboard
+
diff --git a/quickstarts/sendmail/config.yml b/quickstarts/sendmail/config.yml
new file mode 100644
index 0000000000..4d2397093f
--- /dev/null
+++ b/quickstarts/sendmail/config.yml
@@ -0,0 +1,36 @@
+id: c4e07f51-b3f4-4cac-8527-fd96a09923da
+slug: sendmail
+description: |
+ ## Sendmail performance monitoring
+ Sendmail performance monitoring involves monitoring the efficiency and effectiveness of the message delivery in Sendmail and identifying any issues or bottlenecks that may affect email delivery on time.
+ Effective Sendmail performance monitoring ensures that the email system operates smoothly, messages are processed efficiently, and potential issues are promptly identified and addressed, leading to reliable and timely delivery of email messages.
+ ### What should you look for in a Sendmail dashboard?
+ There are several important factors and indicators that must be taken seriously when assessing a Sendmail dashboard. These incorporate backlog analysis, delivery success rate, error tracking, and message processing.
+ ### What’s included in the Sendmail quickstart?
+ Install this quickstart to get preconfigured observability solutions:
+ - A number of high-value alerts are available, including total errors logged, message not accepted for delivery (%), Sendmail service down, and high memory (%).
+ - Informative dashboards (number of messages sent, failed, and deferred, number of senders and recipients, connection time out and more).
+summary: |
+ Monitor your Sendmail with New Relic infrastructure agent and Flex configuration. Get real-time insights into email delivery and performance, including message status, mail logs, errors and warnings, and sender and recipient details.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Sendmail
+dashboards:
+ - sendmail
+alertPolicies:
+ - sendmail
+documentation:
+ - name: Sendmail
+ description: |
+ Use our infrastructure agent and Flex configuration to export Sendmail data to New Relic.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/sendmail-monitoring-integration
+dataSourceIds:
+ - sendmail
+keywords:
+ - sendmail
+ - mail server
+ - infrastructure
+
diff --git a/quickstarts/sendmail/logo.png b/quickstarts/sendmail/logo.png
new file mode 100644
index 0000000000..a70f0a1103
Binary files /dev/null and b/quickstarts/sendmail/logo.png differ
diff --git a/quickstarts/shopify/config.yml b/quickstarts/shopify/config.yml
new file mode 100644
index 0000000000..7bcc7d6fbf
--- /dev/null
+++ b/quickstarts/shopify/config.yml
@@ -0,0 +1,44 @@
+id: 022f9ce9-38b4-47f4-94b6-aa543a0c8952
+slug: shopify
+title: Shopify
+description: |
+ ## About Shopify
+
+ Shopify is unified solution that will help you start your business, create a website, sell your product, and even market/manage your business in one place.
+
+ ### About this integration
+
+ This integration provides a quick and easy way to monitor your Shopify web application, by giving you key browsing metrics like throughput, error rate, traces, and page views.
+
+ ### Setup
+
+ To set up this integration, you will just need to add the [New Relic browser agent code](https://onenr.io/0MRNpYqNqQn) into your Shopify application source code. You can find your Shopify source code by following these stesps in your [Shopify Portal](admin.shopify.com):
+
+ 1. Open **Themes** inside of your online store.
+ 2. Click the ellipsis (**...**) next to the Customize option, then select **Edit code**.
+ 3. Under the **layout** section, look for your main file for your theme called **theme.liquid**.
+
+ Once your in the source code, you can paste the New Relic browser agent code and save it.
+
+ ### Visualizing your Shopify application data
+
+ Once the setup is complete, you can see all of your real time User monitoring data in the new entity created in your New Relic account! You can find the entity in [New Relic](https://one.newrelic.com) under the entity name you created in the agent creation flow.
+summary: |
+ Shopify is a solution that simplifies ecommerce applications and solution stack.
+authors:
+ - New Relic
+ - Joseph Counts
+keywords:
+ - traffic
+ - replay
+ - simulate
+ - report
+ - newrelic partner
+dataSourceIds:
+ - shopify
+documentation:
+ - name: New Relic browser agent documentation
+ url: https://docs.newrelic.com/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent/
+ description: You can follow this guide to set up our browser agent with your shopify website.
+icon: logo.jpg
+website: https://shopify.com
diff --git a/quickstarts/shopify/logo.jpg b/quickstarts/shopify/logo.jpg
new file mode 100644
index 0000000000..8b496c30f4
Binary files /dev/null and b/quickstarts/shopify/logo.jpg differ
diff --git a/quickstarts/singlestoredb/config.yml b/quickstarts/singlestoredb/config.yml
new file mode 100644
index 0000000000..378d41e56f
--- /dev/null
+++ b/quickstarts/singlestoredb/config.yml
@@ -0,0 +1,49 @@
+id: 5d8f4722-54fb-4586-92b0-d5a198251486
+slug: singlestoredb
+description: |
+ ## Why should you monitor your usage of SingleStoreDB?
+
+ Monitor your vector searches on SingleStoreDB to get visibility on what you send to SingleStoreDB, responses retrieved from SingleStoreDB, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ SingleStoreDB uses the LangChain Vector Database to connect to New Relic. This quickstart provides a variety of a pre-built dashboard, which will help you gain insights into the health and performance of your AI app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor the performance and quality of your vector searches with New Relic SingleStoreDB quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: SingleStoreDB
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your vector data store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - singlestoredb
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/singlestoredb/logo.svg b/quickstarts/singlestoredb/logo.svg
new file mode 100644
index 0000000000..595b5738ea
--- /dev/null
+++ b/quickstarts/singlestoredb/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/sklearn-vector-store/config.yml b/quickstarts/sklearn-vector-store/config.yml
new file mode 100644
index 0000000000..48b9a1ca75
--- /dev/null
+++ b/quickstarts/sklearn-vector-store/config.yml
@@ -0,0 +1,51 @@
+id: d7f4dbd9-4496-4622-80a3-1c38760a3cdc
+slug: sklearn-vector-store
+description: |
+ ## Why should you monitor your usage of SKLearn Vector Store?
+ Monitor your vector searches on SKLearn Vector Store to get visibility on what you send to SKLearn Vector Store, responses retrieved from SKLearn Vector Store, latency, usage and errors.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+ New Relic SKLearn Vector Store monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your SKLearn Vector Store app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content.
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic SKLearn Vector Store quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: SKLearn Vector Store
+documentation:
+ - name: SKLearn Vector Store Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - SKLearn Vector Store
+ - vector store
+ - vector database
+ - machine learning
+ - artificial intelligence
+ - computer vision
+ - information retrieval
+ - python
+ - scikit-learn
+ - AI
+ - ML
+ - NLP
+ - CV
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/sklearn-vector-store/logo.png b/quickstarts/sklearn-vector-store/logo.png
new file mode 100644
index 0000000000..ced1931f66
Binary files /dev/null and b/quickstarts/sklearn-vector-store/logo.png differ
diff --git a/quickstarts/snowflake/config.yml b/quickstarts/snowflake/config.yml
index 85b1c38b12..8ef4c1d28e 100644
--- a/quickstarts/snowflake/config.yml
+++ b/quickstarts/snowflake/config.yml
@@ -39,8 +39,6 @@ documentation:
url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/snowflake-integration/
keywords:
- snowflake
-installPlans:
- - snowflake
dataSourceIds:
- snowflake
dashboards:
diff --git a/quickstarts/sonarqube/config.yml b/quickstarts/sonarqube/config.yml
new file mode 100644
index 0000000000..051fec10f2
--- /dev/null
+++ b/quickstarts/sonarqube/config.yml
@@ -0,0 +1,46 @@
+id: bb89147b-0d3c-44bf-8037-accbfd8aa99a
+
+slug: sonarqube
+description: |
+ ## Comprehensive monitoring quickstart for SonarQube
+
+ By integrating SonarQube with New Relic, you can get comprehensive information about the quality of your codebase and receive alerts about serious vulnerabilities. You can keep track of your code deployments as well as the complete CI/CD workflow by visualizing and gathering metrics and logs.
+
+ ## Why monitor SonarQube?
+ The open source platform SonarQube is utilized by development teams to ensure the quality of their source code. SonarQube was specifically designed to provide accessible code quality control to all users.
+
+ By leveraging New Relic, you can enhance your understanding of the health and performance of your SonarQube server, regardless of whether it is deployed on-premises or in a containerized environment. Additionally, New Relic enables you to assess the quality and stability of your code throughout the development process, offering valuable insights.
+
+
+ ## What’s included in this quickstart?
+ New Relic SonarQube monitoring quickstart provides quality out-of-the-box reporting:
+ - Code duplication
+ - Coding guidelines
+ - Identify possible bugs due to code complexity
+ - Design and architecture comments
+ - Display and keep track of important code metrics
+ - Gather SonarQube logs and review them to gain knowledge of its condition
+
+summary: |
+ Identify and optimize SonarQube performance with New Relic SonarQube monitoring.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: SonarQube
+documentation:
+ - name: SonarQube integration documentation
+ description: |
+ Monitor the performance metrics of your SonarQube instances in real-time with New Relic SonarQube.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/sonarqube-monitoring-integration/
+keywords:
+ - sonarqube
+ - sonar
+ - sonarqube jmx
+dashboards:
+ - sonarqube
+alertPolicies:
+ - sonarqube
+dataSourceIds:
+ - sonarqube
\ No newline at end of file
diff --git a/quickstarts/sonarqube/logo.png b/quickstarts/sonarqube/logo.png
new file mode 100644
index 0000000000..fdc2c5ed92
Binary files /dev/null and b/quickstarts/sonarqube/logo.png differ
diff --git a/quickstarts/speedscale/config.yml b/quickstarts/speedscale/config.yml
index 5453309092..0a51e0dfeb 100644
--- a/quickstarts/speedscale/config.yml
+++ b/quickstarts/speedscale/config.yml
@@ -20,7 +20,6 @@ keywords:
- simulate
- report
- newrelic partner
- - featured
- NR1_addData
- NR1_sys
installPlans:
diff --git a/quickstarts/squid-prometheus/config.yml b/quickstarts/squid-prometheus/config.yml
new file mode 100644
index 0000000000..d93cdf7ff3
--- /dev/null
+++ b/quickstarts/squid-prometheus/config.yml
@@ -0,0 +1,53 @@
+id: 20bc868d-d0f6-4413-91a6-2afc281a906b
+# Name of the quickstart
+slug: squid-prometheus
+
+# Title of the quickstart
+title: Squid (Prometheus)
+
+# Description of the quickstart
+description: |
+ ## Squid Monitoring
+ Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages.
+
+ ### What’s Included?
+ New Relic + Squid (Prometheus) quickstart - New Relic’s instant observability quickstart provides the metrics reported by Squid Prometheus exporter.
+ Monitor Squid Cache Managers with New Relic to quickly gain visibility into your cache manager, including active cache managers, traffic, hit rate and more.
+
+ ### Value of Squid Quickstarts
+ [Squid monitoring with New Relic](https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-squid/) offers advanced features, including:
+ - Create custom queries and charts of your data integrations.
+ - Filter and analyze metrics in Infrastructure UI.
+ New Relic’s instant observability quickstart helps developers reduce administrative overheads and accelerate time to value. As New Relic is SaaS-based, you also don’t have to worry about maintenance or onboarding.
+summary: |
+ New Relic's Squid Prometheus quickstart provides data from Squid Cache Manager. Install the quickstart to better understand utilization of the cache and monitor performance issues.
+# Support level
+level: New Relic
+
+# Design
+icon: logo.png
+website: http://www.squid-cache.org/
+
+# Authors of the quickstart
+authors:
+ - New Relic
+
+documentation:
+ - name: Squid (Prometheus)
+ description: |
+ Caching proxy for the Web supporting different protocols that reduces bandwidth and improves response times.
+ url: https://docs.newrelic.com/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/collector-configuration-examples/opentelemetry-collector-squid/
+
+installPlans:
+ - squid-prometheus-integration-docs
+
+dataSourceIds:
+ - squid-prometheus-integration-docs
+
+keywords:
+ - infrastructure
+ - cache
+ - prometheus
+
+dashboards:
+ - squid-prometheus
diff --git a/quickstarts/squid-prometheus/logo.png b/quickstarts/squid-prometheus/logo.png
new file mode 100644
index 0000000000..8e1bfda949
Binary files /dev/null and b/quickstarts/squid-prometheus/logo.png differ
diff --git a/quickstarts/starrocks/config.yml b/quickstarts/starrocks/config.yml
new file mode 100644
index 0000000000..64610cc50c
--- /dev/null
+++ b/quickstarts/starrocks/config.yml
@@ -0,0 +1,54 @@
+id: 34fd3401-f511-49f0-a01c-2f1d3a8c7a7a
+slug: starrocks
+description: |
+ ## Why should you monitor your usage of StarRocks?
+
+ Monitor your vector searches on StarRocks to get visibility on what you send to StarRocks, responses retrieved from StarRocks, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ StarRocks uses the LangChain Vector Database to connect to New Relic. This quickstart provides a variety of a pre-built dashboard, which will help you gain insights into the health and performance of your AI app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor the performance and quality of your vector searches with New Relic StarRocks quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: StarRocks
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your vector data store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - starrocks
+ - vector search
+ - vectordb
+ - vector db
+ - starrocks ai
+ - ai
+ - open source analytical database
+ - analytical database
+ - artificial intelligence
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/starrocks/logo.png b/quickstarts/starrocks/logo.png
new file mode 100644
index 0000000000..75c01a99a9
Binary files /dev/null and b/quickstarts/starrocks/logo.png differ
diff --git a/quickstarts/stripe/config.yml b/quickstarts/stripe/config.yml
new file mode 100644
index 0000000000..37bd23d8b5
--- /dev/null
+++ b/quickstarts/stripe/config.yml
@@ -0,0 +1,37 @@
+id: 45a54f55-c921-48a0-bdf8-a324526edbdf
+slug: stripe
+description: |
+ ## Why monitor your Stripe?
+ As an ecommerce store owner, monitoring your Stripe payment gateway is an important way to ensure that your payments are processed smoothly and securely, identify and troubleshoot problems, comply with regulations, and improve your customer experience.
+ ## Comprehensive monitoring quickstart for Stripe
+ Stripe quickstart by New Relic helps you get payment gateway observability for your ecommerce customers. By collecting and analyzing data from Stripe, you can gain insights into your payment activity and identify any potential problems. This can help you improve the performance of your payment gateway and ensure that your customers have a smooth checkout experience.
+ ## What’s included in this quickstart?
+ The Stripe quickstart by New Relic is a pre-configured integration that makes it easy to collect and analyze data from Stripe.
+ This quickstart gives you a complete overview of your payment activity, including:
+ - Transaction data: Insights into each transaction, such as success, cancellation, revenue, and volume
+ - Error data: Detailed insights into errors, such as declined cards and invalid payment information
+ - Alerts: Real-time alerts during critical times, such as payment gateway outages and CPU spikes
+summary: |
+ Stripe quickstart by New Relic helps you monitor your payment gateway and improve the checkout experience for your ecommerce customers.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Stripe
+documentation:
+ - name: Stripe integration documentation
+ description: |
+ Get insights into your Stripe observability data to improve your business.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/stripe-integration/
+keywords:
+ - stripe
+ - node.js
+ - stripe payment
+ - stripe checkout
+dataSourceIds:
+ - stripe
+dashboards:
+ - stripe
+alertPolicies:
+ - stripe
diff --git a/quickstarts/stripe/logo.png b/quickstarts/stripe/logo.png
new file mode 100644
index 0000000000..26b7ce66fb
Binary files /dev/null and b/quickstarts/stripe/logo.png differ
diff --git a/quickstarts/supabase/config.yml b/quickstarts/supabase/config.yml
new file mode 100644
index 0000000000..c61fe26239
--- /dev/null
+++ b/quickstarts/supabase/config.yml
@@ -0,0 +1,49 @@
+id: fecfebf6-4b32-47d6-a637-51617044a712
+slug: supabase
+description: |
+ ## Why should you monitor your usage of Supabase?
+ Monitor your vector searches on Supabase to get visibility on what you send to Supabase, responses retrieved from Supabase, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ## Comprehensive monitoring quickstart for your Supabase app
+ Our Supabase quickstart provides metrics including Identify popular queries, sources, and content.
+
+ ## What’s included in this quickstart?
+ New Relic Supabase monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Supabase app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Supabase quickstart
+icon: logo.png
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: Supabase
+documentation:
+ - name: Supabase integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - Supabase
+ - langchain
+ - vector store
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
diff --git a/quickstarts/supabase/logo.png b/quickstarts/supabase/logo.png
new file mode 100644
index 0000000000..a02ed8676d
Binary files /dev/null and b/quickstarts/supabase/logo.png differ
diff --git a/quickstarts/sybase/config.yml b/quickstarts/sybase/config.yml
index 1da135ca53..3cf1da3c2b 100644
--- a/quickstarts/sybase/config.yml
+++ b/quickstarts/sybase/config.yml
@@ -36,3 +36,4 @@ documentation:
description: Monitor SAP Adaptive Server Enterprise (Sybase)
icon: logo.svg
website: https://www.newrelic.com
+
diff --git a/quickstarts/synthetics/private-locations/config.yml b/quickstarts/synthetics/private-locations/config.yml
index f4db213f23..87798cbe0c 100644
--- a/quickstarts/synthetics/private-locations/config.yml
+++ b/quickstarts/synthetics/private-locations/config.yml
@@ -48,3 +48,4 @@ icon: logo.svg
website: https://www.newrelic.com
dashboards:
- synthetics-private-minions
+
diff --git a/quickstarts/tidbcloud/config.yml b/quickstarts/tidbcloud/config.yml
new file mode 100644
index 0000000000..6c202300cb
--- /dev/null
+++ b/quickstarts/tidbcloud/config.yml
@@ -0,0 +1,48 @@
+id: bb0e7dc3-7484-46ca-841e-86a2d8818fcc
+# Sets the URL name of the quickstart on public I/O (required)
+dataSourceIds:
+ - tidbcloud
+slug: tidbcloud-quickstart
+
+# Displayed in the UI (required)
+title: TiDB Cloud
+
+# Long-form description of the quickstart (required)
+description: |-
+ ## Quickstart for TiDB Cloud monitoring
+ TiDB Cloud is a fully-managed Database-as-a-Service (DBaaS) solution for TiDB, an open-source, distributed SQL database that is designed to handle both online transaction processing (OLTP) and online analytical processing (OLAP) workloads.
+
+ ### New Relic TiDB Cloud quickstart features
+ With monitoring statistics enabled, you can observe key metrics to analyze the performance of your cluster.
+
+ ### TiDBCloud Quickstart instructions
+ Check out [Metrics available to New Relic](https://docs.pingcap.com/tidbcloud/monitor-new-relic-integration#metrics-available-to-new-relic) to learn more about New Relic monitoring for TiDBCloud.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ New Relic's TiDB Cloud quickstart provides performance insights including database time, queries per second, and resource utilization. Install the quickstart to better understand utilization of resources and monitor performance issues.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - PingCAP
+ - lilyjazz
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - database
+
+dashboards:
+ - tidbcloud
+
+# Documentation references
+documentation:
+ - name: Integrate TiDB Cloud with New Relic
+ url: https://docs.pingcap.com/tidbcloud/monitor-new-relic-integration
+ description: You can configure TiDB Cloud to send metric data about your TiDB clusters to New Relic.
+
+# Content / Design
+icon: logo.svg
+website: https://tidbcloud.com/
diff --git a/quickstarts/tidbcloud/logo.svg b/quickstarts/tidbcloud/logo.svg
new file mode 100644
index 0000000000..7010b35021
--- /dev/null
+++ b/quickstarts/tidbcloud/logo.svg
@@ -0,0 +1,25 @@
+
diff --git a/quickstarts/tigris/config.yml b/quickstarts/tigris/config.yml
new file mode 100644
index 0000000000..ae725fc47c
--- /dev/null
+++ b/quickstarts/tigris/config.yml
@@ -0,0 +1,47 @@
+id: b708e579-49a7-471c-9579-c68fcf53083c
+slug: tigris
+description: |
+ ## Why should you monitor your usage of Tigris?
+ Monitor your vector searches on Tigris to get visibility on what you send to Tigris, responses retrieved from Tigris, latency, usage and errors.
+ ### Track the query performance of Tigris
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track the health of Tigris:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your Tigris's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+ New Relic Tigris monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Tigris app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content.
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Tigris quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Tigris
+documentation:
+ - name: Tigris Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - tigris
+ - tigris vector db
+ - vector database
+ - vector search
+ - AI database
+ - machine learning database
+ - big data database
+ - SQL-based vector database
+ - sql based vector database
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/tigris/logo.svg b/quickstarts/tigris/logo.svg
new file mode 100644
index 0000000000..e023e74c05
--- /dev/null
+++ b/quickstarts/tigris/logo.svg
@@ -0,0 +1,9 @@
+
\ No newline at end of file
diff --git a/quickstarts/tvos/config.yml b/quickstarts/tvos/config.yml
index 6e59531212..2d9f5f4548 100644
--- a/quickstarts/tvos/config.yml
+++ b/quickstarts/tvos/config.yml
@@ -27,3 +27,4 @@ dataSourceIds:
- tvos-mobile
keywords:
- mobile
+
diff --git a/quickstarts/typesense/config.yml b/quickstarts/typesense/config.yml
new file mode 100644
index 0000000000..4f328d02ef
--- /dev/null
+++ b/quickstarts/typesense/config.yml
@@ -0,0 +1,49 @@
+id: e9e125ff-2fe7-47b5-8a29-2a43b95136ec
+slug: typesense
+description: |
+ ## Why should you monitor your usage of Typesense?
+ Monitor your vector searches on Typesense to get visibility on what you send to Typesense, responses retrieved from Typesense, latency, usage and errors.
+
+ ### Track the query performance of Typesense
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track the health of Typesense:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into Typesense's performance and identify areas of improvement.
+
+ ## Comprehensive monitoring quickstart for your Typesense app
+ Our Typesense quickstart provides metrics including Identify popular queries, sources, and content.
+
+ ## What’s included in this quickstart?
+ New Relic Typesense monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of Typesense. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Typesense quickstart
+icon: logo.svg
+level:
+ - New Relic
+authors:
+ - New Relic
+ - Ramana Reddy
+title: Typesense
+documentation:
+ - name: Typesense integration documentation
+ description: |
+ Implement monitoring and instrumentation for Typesense, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - Typesense
+ - langchain
+ - vector store
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+alertPolicies:
+ - langchain-vectordb
+dashboards:
+ - langchain-vectordb
diff --git a/quickstarts/typesense/logo.svg b/quickstarts/typesense/logo.svg
new file mode 100644
index 0000000000..e9f46540b8
--- /dev/null
+++ b/quickstarts/typesense/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/vectara/config.yml b/quickstarts/vectara/config.yml
new file mode 100644
index 0000000000..4eb8493544
--- /dev/null
+++ b/quickstarts/vectara/config.yml
@@ -0,0 +1,47 @@
+id: 1b92a44e-44a4-4e46-a563-85003d4362df
+slug: vectara
+description: |
+ ## Why should you monitor your usage of Vectara?
+ Monitor your vector searches with Vectara to gain insights into the data you're sending to it, the responses you're receiving, the latency, usage, and any potential errors.
+ ### Track the query performance of Vectara
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track the health of Vectara
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your Vectara's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+ New Relic Vectara monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of Vectara. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Vectara quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+ - Jyothi Surampudi
+title: Vectara
+documentation:
+ - name: Vectara integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vectara, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - vectara
+ - vector store
+ - machine learning
+ - vector search
+ - artificial intelligence
+ - AI
+ - ML
+ - NLP
+ - data science
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/vectara/logo.svg b/quickstarts/vectara/logo.svg
new file mode 100644
index 0000000000..8cf6daff10
--- /dev/null
+++ b/quickstarts/vectara/logo.svg
@@ -0,0 +1,21 @@
+
diff --git a/quickstarts/velero-prometheus/config.yml b/quickstarts/velero-prometheus/config.yml
index 356824791a..69bd8abb8c 100644
--- a/quickstarts/velero-prometheus/config.yml
+++ b/quickstarts/velero-prometheus/config.yml
@@ -35,6 +35,7 @@ keywords:
- write
- kubernetes
- disaster recovery
+ - featured
installPlans:
- setup-prometheus
dataSourceIds:
diff --git a/quickstarts/vertica/config.yml b/quickstarts/vertica/config.yml
new file mode 100644
index 0000000000..2ae5c18716
--- /dev/null
+++ b/quickstarts/vertica/config.yml
@@ -0,0 +1,48 @@
+id: 09009442-2ff7-499d-b9ac-67d2a9db2352
+
+slug: vertica
+description: |
+ ## Why monitor Vertica?
+ Vertica is a high-performance, scalable data warehouse platform that is used by many organizations to store and analyze large datasets. However, like any complex system, Vertica can experience problems that can impact performance and reliability.
+ Here are the top three reasons why Vertica needs to be monitored:
+ ### Data skew and segmentation:
+ Vertica distributes data across multiple nodes, and each node processes a subset of the data. If the data is not distributed evenly across the nodes, it can cause data skew, which can lead to performance problems. Segmentation is another problem that can occur when the data is not distributed evenly across the nodes. Segmentation can cause queries to take longer to run, as they have to wait for all of the nodes to finish processing their portion of the query.
+ ### Resource utilization:
+ Vertica is a resource-intensive platform, and it is important to monitor resource utilization to ensure that the system is not overloaded. Resources to monitor include CPU, memory, and disk I/O. If any of these resources are maxed out, it can lead to performance problems.
+ ### Query performance:
+ Vertica is designed to handle complex queries on large datasets quickly and efficiently. However, it is important to monitor query performance to ensure that queries are running as expected. If you notice that queries are taking longer to run than usual, it may be a sign of a performance problem.
+
+ ## Comprehensive monitoring quickstart for Vertica
+
+ Vertica Quickstart shows how to monitor a Vertica database and run simple queries to analyze the performance. As modern databases become increasingly complex yet crucial to business operations, it is imperative to continually monitor their performance. Vertica, a high-performance analytics database, provides several performance monitoring methods. You can monitor the activity and health of a Vertica database through log files and system tables.
+
+ ### What’s included in the Vertica quickstart?
+
+ Install this quickstart to get preconfigured observability solutions:
+ - Includes pre-built alert if the disk usage exceeds 90%
+ - Informative dashboards (long running queries, disk usage, user informations, sessions and more).
+
+summary: |
+ Monitor your Vertica with New Relic infrastructure agent and NRI-Flex configuration. Get real-time insights into Vertica database and performance, including long running queries, queries duration, disk space, table information and more.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Vertica
+dashboards:
+ - vertica
+alertPolicies:
+ - vertica
+documentation:
+ - name: Vertica
+ description: |
+ Monitor the performance metrics of your Vertica database in real-time with New Relic Vertica.
+ url: >-
+ https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/vertica-monitoring-integration
+dataSourceIds:
+ - vertica
+keywords:
+ - vertica
+ - database
+ - infrastructure
+ - opentext
diff --git a/quickstarts/vertica/logo.png b/quickstarts/vertica/logo.png
new file mode 100644
index 0000000000..0492545ffb
Binary files /dev/null and b/quickstarts/vertica/logo.png differ
diff --git a/quickstarts/victorops/config.yml b/quickstarts/victorops/config.yml
deleted file mode 100644
index 5eb75af44c..0000000000
--- a/quickstarts/victorops/config.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-id: 3937fc57-4414-4db7-8f23-b313892379ab
-slug: victorops
-description: |
- ## What is VictorOps?
-
- Get notified via VictorOps when incidents are opened, acknowledged, or closed.
- Notifications can include charts about the incident.
-
- ### Get started!
-
- Check out our VictorOps documentation to set up a notification channel and provide fast and consistent ways for the right personnel to be notified about incidents
-
- ### More info
-
- Check out the [documentation](https://docs.newrelic.com/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts) to learn more about New Relic alerting for VictorOps.
-summary: |
- Get notified via VictorOps when incidents are opened, acknowledged, or closed.
- Notifications can include charts about the incident.
-icon: logo.svg
-level: New Relic
-authors:
- - New Relic
-title: VictorOps
-documentation:
- - name: VictorOps installation docs
- description: |
- Send your New Relic alerts to VictorOps
- url: https://docs.newrelic.com/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts
-keywords:
- - victorops
- - on call
- - support
- - site reliability
- - SRE
-installPlans:
- - third-party-victorops
-dataSourceIds:
- - victorops
diff --git a/quickstarts/victorops/logo.svg b/quickstarts/victorops/logo.svg
deleted file mode 100644
index fad94d0fd4..0000000000
--- a/quickstarts/victorops/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/video/video-android/config.yml b/quickstarts/video/video-android/config.yml
index 49f521efc0..3b4b449f75 100644
--- a/quickstarts/video/video-android/config.yml
+++ b/quickstarts/video/video-android/config.yml
@@ -21,3 +21,4 @@ documentation:
url: https://github.com/newrelic/video-agent-android
description: Agent to monitor video applications for Android.
icon: logo.svg
+
diff --git a/quickstarts/vmware/vmware-esxi/config.yml b/quickstarts/vmware/vmware-esxi/config.yml
deleted file mode 100644
index 47b798e1a4..0000000000
--- a/quickstarts/vmware/vmware-esxi/config.yml
+++ /dev/null
@@ -1,21 +0,0 @@
-id: 1b913236-5aab-424c-8135-c1d2a4a03441
-slug: vmware-esxi
-description: Hypervisor built for direct interaction with server hardware and resources.
-summary: Hypervisor built for direct interaction with server hardware and resources.
-icon: logo.svg
-level: New Relic
-authors:
- - New Relic
-title: VMware ESXi
-documentation:
- - name: VMware ESXi installation docs
- description: |
- Hypervisor built for direct interaction with server hardware and
- resources.
- url: https://docs.newrelic.com/docs/integrations/host-integrations/open-source-host-integrations-list/vmware-esxi-open-source-integration
-keywords:
- - infrastructure
-installPlans:
- - third-party-vmware-esxi
-dataSourceIds:
- - vmware-esxi
diff --git a/quickstarts/vmware/vmware-esxi/logo.svg b/quickstarts/vmware/vmware-esxi/logo.svg
deleted file mode 100644
index 0b2ee0e033..0000000000
--- a/quickstarts/vmware/vmware-esxi/logo.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/quickstarts/vmware/vmware-vsphere/config.yml b/quickstarts/vmware/vmware-vsphere/config.yml
new file mode 100644
index 0000000000..1db5d523c7
--- /dev/null
+++ b/quickstarts/vmware/vmware-vsphere/config.yml
@@ -0,0 +1,32 @@
+id: 87bd9d20-a193-4aa8-80f7-a1f5c65278f1
+slug: vmware-vsphere
+title: VMware vSphere
+description: |
+ Enterprise Workload Platform for Traditional and Next Gen Apps
+summary: |
+ Enterprise Workload Platform for Traditional and Next Gen Apps
+level: New Relic
+authors:
+ - New Relic
+ - Zack Mutchler
+ - Marc Netterfield
+keywords:
+ - infrastructure
+ - vmware
+ - vsphere
+ - esxi
+ - vcenter
+installPlans:
+ - vsphere-integration
+dataSourceIds:
+ - vmware-vsphere
+alertPolicies:
+ - vmware-vsphere
+dashboards:
+ - vmware-vsphere
+documentation:
+ - name: VMware vSphere installation docs
+ description: |
+ Enterprise Workload Platform for Traditional and Next Gen Apps
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/vmware-vsphere-monitoring-integration/#install
+icon: logo.svg
diff --git a/quickstarts/vmware/vmware-vsphere/logo.svg b/quickstarts/vmware/vmware-vsphere/logo.svg
new file mode 100644
index 0000000000..87a103e97e
--- /dev/null
+++ b/quickstarts/vmware/vmware-vsphere/logo.svg
@@ -0,0 +1,22 @@
+
+
+
diff --git a/quickstarts/weaviate/config.yml b/quickstarts/weaviate/config.yml
new file mode 100644
index 0000000000..433e4a8753
--- /dev/null
+++ b/quickstarts/weaviate/config.yml
@@ -0,0 +1,43 @@
+id: 7a0892b5-1309-445c-9902-e094aaf5077b
+slug: weaviate
+description: |
+ ## Why should you monitor your usage of Weaviate?
+ Monitor your vector searches on Weaviate to get visibility on what you send to Weaviate, responses retrieved from Weaviate, latency, usage and errors.
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+ ### What’s included in this quickstart?
+ New Relic LangChain monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your LangChain app. These reports include:
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Weaviate quickstart.
+icon: logo.png
+level: New Relic
+authors:
+ - New Relic
+title: Weaviate
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - weaviate
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/weaviate/logo.png b/quickstarts/weaviate/logo.png
new file mode 100644
index 0000000000..0f4e8f5927
Binary files /dev/null and b/quickstarts/weaviate/logo.png differ
diff --git a/quickstarts/windows/windows-certs/config.yml b/quickstarts/windows/windows-certs/config.yml
new file mode 100644
index 0000000000..1c7749230b
--- /dev/null
+++ b/quickstarts/windows/windows-certs/config.yml
@@ -0,0 +1,52 @@
+id: 34776289-28ab-4832-ba67-adbb4357d21d
+# Sets the URL name of the quickstart on public I/O (required)
+slug: windowslocalcerts
+
+# Displayed in the UI (required)
+title: Windows Local Certs
+
+# Long-form description of the quickstart (required)
+description: |
+ The quickstart shares an example of how to get started with getting visibility into the local certificates in your Windows environment. Within this bundle you'll find information on the instrumentation (via Flex on NR Infrastructure Agent), as well as a starter dashboard that will be added to your account.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ Get visibility into the local certificates running on a Windows machine.
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - Nima Adib
+
+icon: logo.png
+
+# Keywords for filtering / searching criteria in the UI
+keywords:
+ - windows
+ - microsoft
+ - server
+ - os
+ - operating system
+ - certificates
+ - powershell
+
+# Reference to install plans located under /install directory
+# Allows us to construct reusable "install plans" and just use their ID in the quickstart config
+dataSourceIds:
+ - windows-certs
+
+# Reference to dashboards to be included in this quickstart
+dashboards:
+ - windows-certs
+
+# Documentation references
+documentation:
+ - name: Get started with this flex integration
+ url: https://github.com/newrelic/nri-flex/tree/master/examples/windows/WindowsExpCertSample
+ description: github link with the example integration set up as well as the documentation and overview.
+
+# Content / Design
+website: https://www.newrelic.com
+
diff --git a/quickstarts/windows/windows-certs/logo.png b/quickstarts/windows/windows-certs/logo.png
new file mode 100644
index 0000000000..675e89e22d
Binary files /dev/null and b/quickstarts/windows/windows-certs/logo.png differ
diff --git a/quickstarts/winservices/config.yml b/quickstarts/winservices/config.yml
index fb7f2e8fc4..c1818f500b 100644
--- a/quickstarts/winservices/config.yml
+++ b/quickstarts/winservices/config.yml
@@ -32,6 +32,7 @@ keywords:
- service
- os
- operating system
+ - featured
authors:
- New Relic
documentation:
diff --git a/quickstarts/wordpress-fullstack/config.yml b/quickstarts/wordpress-fullstack/config.yml
new file mode 100644
index 0000000000..5ca5bf74b4
--- /dev/null
+++ b/quickstarts/wordpress-fullstack/config.yml
@@ -0,0 +1,50 @@
+id: 5e747b2f-ec74-4145-8006-9acbbc64c7db
+slug: wordpress-fullstack
+description: |
+ ## Comprehensive monitoring quickstart for WordPress
+ WordPress is a popular open-source content management system (CMS) used for creating websites, blogs, and web applications. It provides a user-friendly interface and a wide range of customizable themes and plugins, allowing users to build and manage their online content without extensive coding knowledge.
+
+ New Relic WordPress Full Stack quickstart enables performance monitoring of your WordPress application through agents installation and New Relic Flex configuration.
+
+ ### Why monitor WordPress?
+ Websites across various domains extensively utilize WordPress applications. Despite their versatility, these websites can experience slowdowns caused by factors such as slow-loading plugins, database connection problems, or other variables.
+ Our WordPress Full-Stack quickstart offers step-by-step documentation for instrumenting the quickstart and provides a pre-built dashboard to monitor crucial performance metrics, database metrics, and error messages generated on a specific URL. These indicators assist you and your team in identifying and addressing concerns, ultimately enhancing your website's performance.
+
+ ### What’s included in this quickstart?
+ New Relic WordPress Full Stack monitoring agent capture the following metrics:
+ - Easily identify plugins that consume the most time and resources
+ - User usage statistics i.e., user device type and unique visitors
+ - Database metrics like connections per second and more
+ - Browser metrics like page view comparison, time to first byte (TTFB) and more
+ - Transactions and related error messages
+ - WordPress debug logs are also captured
+summary: |
+ Optimize the monitoring of WordPress metrics, plugins, logs, and performance analysis by leveraging the integrated full stack monitoring capabilities offered by New Relic.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: WordPress Full Stack
+documentation:
+ - name: WordPress Full Stack documentation
+ description: |
+ Monitor the performance metrics of your WordPress application and its instances in real-time with New Relic.
+ url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/wordpress-fullstack-integration/
+keywords:
+ - wordpress
+ - php
+ - performance monitoring
+ - CMS
+ - wordpress full stack
+ - browser
+ - full stack
+ - word press
+dataSourceIds:
+ - new-relic-infrastructure-agent
+ - php
+ - mysql
+ - apache
+dashboards:
+ - wordpress-fullstack
+alertPolicies:
+ - wordpress-fullstack
diff --git a/quickstarts/wordpress-fullstack/logo.svg b/quickstarts/wordpress-fullstack/logo.svg
new file mode 100644
index 0000000000..bf1dd42fef
--- /dev/null
+++ b/quickstarts/wordpress-fullstack/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/quickstarts/zilliz/config.yml b/quickstarts/zilliz/config.yml
new file mode 100644
index 0000000000..df5b18eed1
--- /dev/null
+++ b/quickstarts/zilliz/config.yml
@@ -0,0 +1,49 @@
+id: 610b6e73-e4fa-47a6-b797-573230c1f18b
+slug: zilliz
+description: |
+ ## Why should you monitor your usage of Zilliz?
+
+ Monitor your vector searches on Zilliz to get visibility on what you send to Zilliz, responses retrieved from Zilliz, latency, usage and errors.
+
+ ### Track the query performance of your Vector DB
+ Track the behavior of your vector stores. Monitor the latency, queries, the number of documents retrieved, and the content of the documents so that you can evaluate their relevance.
+
+ ### Track your app:
+ By tracking key metrics like latency, throughput, error rates, and input & output, you can gain insights into your app's performance and identify areas of improvement.
+
+
+ ### What’s included in this quickstart?
+
+ New Relic Zilliz monitoring quickstart provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Zilliz app. These reports include:
+
+ - Vector searches
+ - Alerts for errors, search per vector store, and response time
+ - Identify popular queries, sources, and content
+
+summary: |
+ Monitor your Vector search's performance and quality with New Relic Zilliz quickstart.
+icon: logo.svg
+level: New Relic
+authors:
+ - New Relic
+title: Zilliz
+documentation:
+ - name: LangChain Vector Database integration documentation
+ description: |
+ Implement monitoring and instrumentation for your Vector store, and ensure that your observability data is integrated into New Relic for effective performance analysis and insights.
+ url: https://github.com/newrelic/nr-openai-observability
+dataSourceIds:
+ - langchain-vectordb
+keywords:
+ - langchain
+ - vector store
+ - zilliz
+ - vector search
+ - vectordb
+ - vector db
+ - mlops
+ - NR1_addData
+dashboards:
+ - langchain-vectordb
+alertPolicies:
+ - langchain-vectordb
\ No newline at end of file
diff --git a/quickstarts/zilliz/logo.svg b/quickstarts/zilliz/logo.svg
new file mode 100644
index 0000000000..7a57eb4a5f
--- /dev/null
+++ b/quickstarts/zilliz/logo.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/utils/__tests__/create-validate-pr-quickstarts.test.js b/utils/__tests__/create-validate-pr-quickstarts.test.js
index 89c1302225..992f84ac98 100644
--- a/utils/__tests__/create-validate-pr-quickstarts.test.js
+++ b/utils/__tests__/create-validate-pr-quickstarts.test.js
@@ -8,6 +8,7 @@ import * as githubHelpers from '../lib/github-api-helpers';
jest.mock('@actions/core');
jest.spyOn(global.console, 'error').mockImplementation(() => {});
+jest.spyOn(global.console, 'log').mockImplementation(() => {});
jest.mock('../lib/github-api-helpers', () => ({
...jest.requireActual('../lib/github-api-helpers'),
diff --git a/utils/__tests__/dashboard-helper.test.js b/utils/__tests__/dashboard-helper.test.js
index 342595b23b..b5bac98a25 100644
--- a/utils/__tests__/dashboard-helper.test.js
+++ b/utils/__tests__/dashboard-helper.test.js
@@ -3,6 +3,8 @@ import {
checkLine,
createWarningComment,
runHelper,
+ getLines,
+ getWarnings,
} from '../dashboard-helper';
import * as ghHelpers from '../lib/github-api-helpers';
import * as core from '@actions/core';
@@ -20,51 +22,62 @@ jest.mock('../lib/github-api-helpers', () => {
jest.mock('node-fetch');
describe('dashboard-helper', () => {
- describe('checkLine', () => {
+ describe('getWarnings', () => {
test('handles empty string input', () => {
- expect(checkLine('')).toHaveLength(0);
+ expect(getWarnings('')).toHaveLength(0);
});
test('finds guid', () => {
- expect(checkLine(`(entity.guid)`)).toHaveLength(1);
+ expect(getWarnings(`(entity.guid)`)).toHaveLength(1);
});
test('finds entityGuid', () => {
- expect(checkLine(`entityGuid`)).toHaveLength(1);
+ expect(getWarnings({'entityGuid': 1234})).toHaveLength(1);
});
test('finds linkedEntityGuids', () => {
- expect(checkLine(`"linkedEntityGuids": 123456`)).toHaveLength(1);
+ expect(getWarnings({"linkedEntityGuids":123456})).toHaveLength(1);
});
test('does not find null linkedEntityGuids', () => {
- expect(checkLine(`"linkedEntityGuids": null`)).toHaveLength(0);
+ expect(getWarnings({"linkedEntityGuids":null})).toHaveLength(0);
});
test('finds permissions field', () => {
- expect(checkLine(`"permissions": test`)).toHaveLength(1);
+ expect(getWarnings({"permissions": 'test'})).toHaveLength(1);
});
test('finds accountId', () => {
- expect(checkLine(`"accountId": 123456`)).toHaveLength(1);
+ expect(getWarnings({"accountId":123456})).toHaveLength(1);
});
test('does not find accountId equal to zero', () => {
- expect(checkLine(`"accountId": 0`)).toHaveLength(0);
+ expect(getWarnings({"accountId":0})).toHaveLength(0);
});
test('finds accountIds', () => {
- expect(checkLine(`"accountIds": [ 0 ]`)).toHaveLength(1);
+ expect(getWarnings({"accountIds":[ 31415 ]})).toHaveLength(1);
});
test('does not find accountIds equal to []', () => {
- expect(checkLine(`"accountIds": []`)).toHaveLength(0);
- });
+ expect(getWarnings({"accountIds":[]})).toHaveLength(0);
+ });
+
+ test('finds warnings across multiple lines', () => {
+ const multiLine = {
+ "accountIds": [
+ 12345678,
+ 3456,
+ 12,
+ ],
+ }
+ expect(getWarnings(multiLine)).toHaveLength(1);
+ });
});
describe('createWarningComment', () => {
test('creates comment', () => {
- const warnings = ['test string | test file | test line'];
+ const warnings = ['test string | test file'];
const testComment = createWarningComment(warnings);
expect(testComment).toContain(warnings[0]);
expect(testComment).toContain(
@@ -110,7 +123,10 @@ describe('dashboard-helper', () => {
'raw-url/dashboards/cool-dash/cool-dash.json',
{ headers: { authorization: 'token token' } }
);
- expect(core.setOutput).toHaveBeenCalledWith('comment', '### The PR checks have run and found the following warnings:%0A%0A| Warning | Filepath | Line # | %0A| --- | --- | --- | %0A| \"permissions\" field should not be used | dashboards/cool-dash/cool-dash.json | 2 |%0A%0AReference the [Contributing Docs for Dashboards](https://github.com/newrelic/newrelic-quickstarts/blob/main/CONTRIBUTING.md#dashboards) for more information. %0A');
+ expect(core.setOutput).toHaveBeenCalledWith(
+ 'comment',
+ '### The PR checks have run and found the following warnings:\n\n| Warning | Filepath | \n| --- | --- | \n| "permissions" field should not be used | dashboards/cool-dash/cool-dash.json |\n\nReference the [Contributing Docs for Dashboards](https://github.com/newrelic/newrelic-quickstarts/blob/main/CONTRIBUTING.md#dashboards) for more information. \n'
+ );
});
test('handles network error;', async () => {
diff --git a/utils/__tests__/logger.test.ts b/utils/__tests__/logger.test.ts
new file mode 100644
index 0000000000..0df210dcf7
--- /dev/null
+++ b/utils/__tests__/logger.test.ts
@@ -0,0 +1,23 @@
+import logger from '../logger';
+
+jest.spyOn(console, 'log').mockImplementation(jest.fn());
+
+describe('logger', () => {
+ beforeEach(() => {
+ jest.clearAllMocks();
+ });
+
+ test('Defaults to INFO level', () => {
+ process.env.LOG_LEVEL = '';
+
+ logger.info('test');
+ expect(console.log).toHaveBeenCalledTimes(1);
+ });
+
+ test('Does not log at a level higher than set', () => {
+ process.env.LOG_LEVEL = 'INFO';
+
+ logger.debug('test');
+ expect(console.log).toHaveBeenCalledTimes(0);
+ });
+});
diff --git a/utils/__tests__/set-dashboard-required-datasources.test.js b/utils/__tests__/set-dashboard-required-datasources.test.js
index 4d092e7f70..8eef514239 100644
--- a/utils/__tests__/set-dashboard-required-datasources.test.js
+++ b/utils/__tests__/set-dashboard-required-datasources.test.js
@@ -6,6 +6,7 @@ import * as nrGraphQlHelpers from '../lib/nr-graphql-helpers';
import { setDashboardsRequiredDataSources } from '../set-dashboards-required-datasources';
jest.spyOn(global.console, 'error').mockImplementation(() => {});
+jest.spyOn(global.console, 'log').mockImplementation(() => {});
jest.mock('../lib/github-api-helpers', () => ({
...jest.requireActual('../lib/github-api-helpers'),
diff --git a/utils/create-validate-data-sources.ts b/utils/create-validate-data-sources.ts
index df746a9122..423cd78708 100644
--- a/utils/create-validate-data-sources.ts
+++ b/utils/create-validate-data-sources.ts
@@ -14,6 +14,7 @@ import DataSource, { DataSourceMutationResponse } from './lib/DataSource';
import { NerdGraphResponseWithLocalErrors } from './types/nerdgraph';
import type { DataSourceConfig } from './types/DataSourceConfig';
+import logger from './logger';
const DATA_SOURCE_CONFIG_REGEXP = new RegExp(
'data-sources/.+/config.+(yml|yaml)'
@@ -45,7 +46,9 @@ const main = async () => {
process.exit(1);
}
+ logger.info(`Fetching files for pull request ${GITHUB_API_URL}`);
const files = await fetchPaginatedGHResults(GITHUB_API_URL, githubToken);
+ logger.info(`Found ${files.length} files`);
const dataSources = filterOutTestFiles(files)
.filter(isNotRemoved)
@@ -58,6 +61,8 @@ const main = async () => {
let results: (NerdGraphResponseWithLocalErrors & {
name: string;
})[] = [];
+
+ logger.info(`Submitting ${dataSources.length} data sources...`);
// Submit all of the mutations (in chunks of 5)
for (const c of chunk(dataSources, 5)) {
const res = await Promise.all(
@@ -84,6 +89,8 @@ const main = async () => {
if (hasFailed) {
process.exit(1);
}
+
+ logger.info(`Success!`);
};
if (require.main === module) {
diff --git a/utils/create_validate_pr_quickstarts.ts b/utils/create_validate_pr_quickstarts.ts
index 04312227f1..b9d35ee615 100644
--- a/utils/create_validate_pr_quickstarts.ts
+++ b/utils/create_validate_pr_quickstarts.ts
@@ -19,6 +19,7 @@ import {
NerdGraphResponseWithLocalErrors,
NerdGraphError,
} from './types/nerdgraph';
+import logger from './logger';
type ResponseWithErrors =
NerdGraphResponseWithLocalErrors & {
@@ -33,8 +34,8 @@ const installPlanErrorExists = (error: Error | NerdGraphError): boolean =>
const dataSourceErrorExists = (error: Error | NerdGraphError): boolean =>
'extensions' in error &&
- error?.extensions?.argumentPath.includes('dataSourceIds') &&
- error?.message?.includes('contains a data source that does not exist');
+ error?.extensions?.argumentPath.includes('dataSourceIds') &&
+ error?.message?.includes('contains a data source that does not exist');
export const countAndOutputErrors = (
graphqlResponses: ResponseWithErrors[]
@@ -72,9 +73,12 @@ export const createValidateQuickstarts = async (
return false;
}
+ logger.info(`Fetching files for pull request ${ghUrl}`);
// Get all files from PR
const files = await fetchPaginatedGHResults(ghUrl, ghToken);
+ logger.info(`Found ${files.length} files`);
+
// Get all quickstart mutation variables
const quickstarts = filterOutTestFiles(files)
.filter(isNotRemoved)
@@ -121,6 +125,7 @@ export const createValidateQuickstarts = async (
// Class implementations may throw an error
const quickstartErrors: string[] = [];
+ logger.info(`Submitting ${quickstarts.length} quickstarts...`);
for (const c of chunk(quickstarts, 5)) {
try {
const res = await Promise.all(
@@ -162,6 +167,8 @@ const main = async () => {
if (hasFailed) {
process.exit(1);
}
+
+ logger.info(`Success!`);
};
/**
diff --git a/utils/dashboard-helper.ts b/utils/dashboard-helper.ts
index 6cb0663824..5c9b521355 100644
--- a/utils/dashboard-helper.ts
+++ b/utils/dashboard-helper.ts
@@ -13,7 +13,7 @@ const regexAndWarning: [RegExp, string][] = [
[/\"permissions\": /, `\"permissions\" field should not be used`],
[/\"accountId\": (?:(?!0))/, `\"accountId\" must be zero`],
[
- /\"accountIds\"\s*:\s\[(?!\s*])([^\]\[]+)\]/,
+ /\"accountIds\": \"\[(?!\s*])([^\]\[]+)\]\"/,
`\"accountIds\" must be set to []`,
],
];
@@ -28,13 +28,34 @@ export const checkLine = (line: string) => {
return warningsFound;
};
-const encodedNewline = '%0A';
+export const getWarnings = (dashboardJson: any) => {
+ const dashLines = JSON.stringify(dashboardJson, (k, v) => {
+ if (Array.isArray(v)) {
+ return JSON.stringify(v)
+ }
+ return v
+ }, 2).split('\n');
+ const warnings: string[] = [];
+
+ dashLines.forEach((line) => {
+ const output = checkLine(line);
+ if (output.length > 0) {
+ output.forEach((warning) =>
+ warnings.push(warning)
+ );
+ }
+ });
+ return warnings;
+}
+
+const encodedNewline = '\n';
+
export const createWarningComment = (warnings: string[]) => {
const commentMessage = [
`### The PR checks have run and found the following warnings:${encodedNewline}`,
];
- const tableHeader = `| Warning | Filepath | Line # | ${encodedNewline}| --- | --- | --- | `;
+ const tableHeader = `| Warning | Filepath | ${encodedNewline}| --- | --- | `;
commentMessage.push(tableHeader);
warnings.forEach((w) => commentMessage.push(w));
@@ -61,7 +82,7 @@ export const runHelper = async (
return false;
}
- const warnings: string[] = [];
+ const warningMessages: string[] = [];
const files = await fetchPaginatedGHResults(new URL(prUrl).href, token);
@@ -80,25 +101,19 @@ export const runHelper = async (
}
const responseJSON = await response.json();
- const dashLines = JSON.stringify(responseJSON, null, 2).split('\n');
-
- dashLines.forEach((line, lineNumber) => {
- const output = checkLine(line);
- if (output.length > 0) {
- output.forEach((o) =>
- warnings.push(`| ${o} | ${dash.filename} | ${lineNumber + 1} |`)
- );
- }
- });
+ const warnings = getWarnings(responseJSON);
+ warnings.forEach((o) =>
+ warningMessages.push(`| ${o} | ${dash.filename} |`)
+ );
} catch (error: any) {
console.error('Error:', error.message);
return false;
}
}
- if (warnings.length > 0) {
- console.log('Found warnings:', warnings);
- const warningComment = createWarningComment(warnings);
+ if (warningMessages.length > 0) {
+ console.log('Found warnings:', warningMessages);
+ const warningComment = createWarningComment(warningMessages);
core.setOutput('comment', warningComment);
}
diff --git a/utils/generate-uuids.ts b/utils/generate-uuids.ts
index 1102bb93b5..5181c225c2 100644
--- a/utils/generate-uuids.ts
+++ b/utils/generate-uuids.ts
@@ -3,11 +3,13 @@ import * as fs from 'fs';
import { v4 as uuidv4 } from 'uuid';
import Quickstart from './lib/Quickstart';
+import logger from './logger';
const main = (quickstarts: Quickstart[]): void => {
for (const quickstart of quickstarts) {
if (!quickstart.config.id) {
- console.log(`Generated ID for ${quickstart.config.title}`);
+ logger.info(`Generating ID for ${quickstart.config.title}...`);
+
const newId: string = uuidv4();
const rawConfig: string = fs.readFileSync(
quickstart.getConfigFilePath(),
@@ -18,6 +20,7 @@ const main = (quickstarts: Quickstart[]): void => {
fs.writeFileSync(quickstart.getConfigFilePath(), configWithId, {
encoding: 'utf8',
});
+ logger.info(`Generated ID for ${quickstart.config.title}`);
}
}
};
diff --git a/utils/lib/Alert.ts b/utils/lib/Alert.ts
index 628e3a0921..8c20c29325 100644
--- a/utils/lib/Alert.ts
+++ b/utils/lib/Alert.ts
@@ -5,6 +5,7 @@ import * as glob from 'glob';
import Component from './Component';
+import logger from '../logger';
import type {
AlertType,
QuickstartAlertInput,
@@ -152,29 +153,36 @@ class Alert extends Component {
| { alertPolicy: AlertPolicyDataSource }
| { alertPolicy: null; errors: ErrorOrNerdGraphError[] }
> {
+ const policyName = `${quickstart.name} alert policy`;
+
+ logger.info(`Request data sources for ${policyName}`);
const { data, errors } = await fetchNRGraphqlResults<
AlertPolicyRequiredDataSourcesQueryVariables,
AlertPolicyRequiredDataSourcesQueryResults
>({
queryString: ALERT_POLICY_REQUIRED_DATA_SOURCES_QUERY,
- variables: { query: `${quickstart.name} alert policy` },
+ variables: { query: policyName },
});
+ logger.debug(`Results for ${policyName}`, { data, errors });
const results = data?.actor?.nr1Catalog?.search?.results;
const hasFailed = quickstart.dataSourceIds.length > 1;
if (errors && errors.length > 0) {
+ logger.debug(`Errors requesting data sources for ${policyName}`, {
+ errors,
+ });
return { alertPolicy: null, errors };
}
if (results === undefined || results.length === 0) {
- console.log(`No alert policy for quickstart ${quickstart.name} exists`);
+ logger.info(`No alert policy for quickstart ${quickstart.name} exists`);
return { alertPolicy: null, errors: [] };
}
if (hasFailed) {
- console.log(
+ logger.info(
`Multiple Quickstart data sources detected for Quickstart: ${quickstart.name} with AlertPolicy: ${results[0].id} must update manually`
);
@@ -214,6 +222,10 @@ class Alert extends Component {
templateId: string,
dataSourceIds: string[]
) {
+ logger.info(`Submitting mutation for alert policy ${templateId}`, {
+ templateId,
+ dataSourceIds,
+ });
const result = await fetchNRGraphqlResults<
AlertPolicySetRequiredDataSourcesMutationVariables,
AlertPolicySetRequiredDataSourcesMutationResults
@@ -221,6 +233,8 @@ class Alert extends Component {
queryString: ALERT_POLICY_SET_REQUIRED_DATA_SOURCES_MUTATION,
variables: { templateId, dataSourceIds },
});
+ logger.info(`Submitted mutation for alert policy ${templateId}`);
+ logger.debug(`Results for alert policy mutation`, { ...result });
return result;
}
diff --git a/utils/lib/Dashboard.ts b/utils/lib/Dashboard.ts
index 78213df7e0..71b318ae68 100644
--- a/utils/lib/Dashboard.ts
+++ b/utils/lib/Dashboard.ts
@@ -6,6 +6,7 @@ import type { QuickstartDashboardInput } from '../types/QuickstartMutationVariab
import type { NerdGraphResponseWithLocalErrors } from '../types/nerdgraph';
import Component from './Component';
+import logger from '../logger';
import {
GITHUB_RAW_BASE_URL,
DASHBOARD_REQUIRED_DATA_SOURCES_QUERY,
@@ -160,6 +161,7 @@ class Dashboard extends Component {
static async getRequiredDataSources(
templateId: string
): Promise<{ ids: string[]; errors?: ErrorOrNerdGraphError[] }> {
+ logger.info(`Requesting data sources for ${templateId}`);
const { data, errors } = await fetchNRGraphqlResults<
DashboardRequiredDataSourcesQueryVariables,
DashboardRequiredDataSourcesQueryResults
@@ -167,6 +169,7 @@ class Dashboard extends Component {
queryString: DASHBOARD_REQUIRED_DATA_SOURCES_QUERY,
variables: { id: templateId },
});
+ logger.debug(`Results for ${templateId}`, { data, errors });
const ids =
data?.actor?.nr1Catalog?.dashboardTemplate?.metadata?.requiredDataSources?.map(
@@ -196,6 +199,10 @@ class Dashboard extends Component {
...new Set([...currDataSourceIds, ...newDataSourceIds]),
];
+ logger.info(`Submitting mutation for dashboard ${templateId}`, {
+ templateId,
+ newDataSourceIds,
+ });
const result = await fetchNRGraphqlResults<
DashboardSetRequiredDataSourcesMutationVariables,
DashboardSetRequiredDataSourcesMutationResults
@@ -203,6 +210,11 @@ class Dashboard extends Component {
queryString: DASHBOARD_SET_REQUIRED_DATA_SOURCES_MUTATION,
variables: { templateId, dataSourceIds },
});
+ logger.info(`Submitted mutation for dashboard ${templateId}`);
+ logger.debug(`Results for dashboard ${templateId}`, {
+ data: result.data,
+ errors: result.errors,
+ });
return result;
}
diff --git a/utils/lib/DataSource.ts b/utils/lib/DataSource.ts
index 02cfdc1606..fdbbad82c3 100644
--- a/utils/lib/DataSource.ts
+++ b/utils/lib/DataSource.ts
@@ -5,6 +5,7 @@ import * as yaml from 'js-yaml';
import Component from './Component';
import { DATA_SOURCE_MUTATION, GITHUB_RAW_BASE_URL } from '../constants';
+import logger from '../logger';
import { fetchNRGraphqlResults } from './nr-graphql-helpers';
@@ -114,6 +115,7 @@ class DataSource extends Component {
);
}
+ logger.info(`Submitting mutation for ${this.config.id}`, { dryRun });
const { data, errors } = await fetchNRGraphqlResults<
DataSourceMutationVariable,
DataSourceMutationResponse
@@ -121,6 +123,8 @@ class DataSource extends Component {
queryString: DATA_SOURCE_MUTATION,
variables: this._getComponentMutationVariables(dryRun),
});
+ logger.info(`Submitted mutation for ${this.config.id}`, { dryRun });
+ logger.debug(`Submission results for ${this.config.id}`, { data, errors });
// filePath may need to be changed for this rework
return { data, errors, name: this.identifier };
diff --git a/utils/lib/Quickstart.ts b/utils/lib/Quickstart.ts
index 576fa1bde5..546f4bf4cc 100644
--- a/utils/lib/Quickstart.ts
+++ b/utils/lib/Quickstart.ts
@@ -7,6 +7,7 @@ import Alert from './Alert';
import Dashboard from './Dashboard';
import DataSource from './DataSource';
import Component from './Component';
+import logger from '../logger';
import {
MOCK_UUID,
GITHUB_RAW_BASE_URL,
@@ -44,14 +45,14 @@ type Components = InstanceType;
enum ConfigKey {
AlertPolicies = 'alertPolicies',
- Dashboards = 'dashboards',
-};
+ Dashboards = 'dashboards',
+}
interface ConfigToMutationMap {
configKey: ConfigKey;
mutationKey: string;
constructor: ComponentType;
-};
+}
const ConfigToMutation: ConfigToMutationMap[] = [
{
@@ -172,7 +173,7 @@ class Quickstart {
description: doc.description,
})),
icon: icon && this._constructIconUrl(icon),
- keywords: keywords,
+ keywords: keywords ?? [],
sourceUrl: Component.getAssetSourceUrl(
Component.removeBasePath(path.dirname(this.configPath), this.basePath)
),
@@ -200,6 +201,7 @@ class Quickstart {
}
public async submitMutation(dryRun = true) {
+ logger.info(`Submitting mutation for ${this.identifier}`, { dryRun });
const { data, errors } = await fetchNRGraphqlResults<
QuickstartMutationVariable,
QuickstartMutationResponse
@@ -207,6 +209,11 @@ class Quickstart {
queryString: QUICKSTART_MUTATION,
variables: await this.getMutationVariables(dryRun),
});
+ logger.info(`Submitted mutation for ${this.identifier}`, { dryRun });
+ logger.debug(`Submission results for ${this.identifier}`, {
+ data,
+ errors,
+ });
// filePath may need to be changed for this rework
return { data, errors, name: this.identifier };
diff --git a/utils/lib/__tests__/Quickstart.test.js b/utils/lib/__tests__/Quickstart.test.js
index 18514ff15c..21c856e7ea 100644
--- a/utils/lib/__tests__/Quickstart.test.js
+++ b/utils/lib/__tests__/Quickstart.test.js
@@ -155,6 +155,16 @@ describe('Quickstart', () => {
expect(variables.quickstartMetadata.installPlanStepIds).toHaveLength(1);
expect(variables.quickstartMetadata.dataSourceIds).toHaveLength(1);
});
+
+ test('Returns keywords as empty array if no keywords are provided', async () => {
+ const qs = new Quickstart(
+ 'quickstarts/mock-quickstart-11/config.yml',
+ MOCK_FILES_BASEPATH
+ );
+ const variables = await qs.getMutationVariables(true);
+
+ expect(variables.quickstartMetadata.keywords).toEqual([]);
+ });
});
describe('validate', () => {
@@ -187,7 +197,7 @@ describe('Quickstart', () => {
test('Returns all quickstarts in directory', () => {
const quickstarts = Quickstart.getAll(MOCK_FILES_BASEPATH);
- expect(quickstarts).toHaveLength(10);
+ expect(quickstarts).toHaveLength(11);
});
test('Handles no quickstarts in directory', () => {
diff --git a/utils/lib/github-api-helpers.ts b/utils/lib/github-api-helpers.ts
index cd55847693..089d91d398 100644
--- a/utils/lib/github-api-helpers.ts
+++ b/utils/lib/github-api-helpers.ts
@@ -4,6 +4,7 @@ import {
QUICKSTART_CONFIG_REGEXP,
DATA_SOURCE_CONFIG_REGEXP,
} from '../constants';
+import logger from '../logger';
const INSTALL_CONFIG_REGEXP = new RegExp('install/.+/install.+(yml|yaml)');
const MOCK_FILES_REGEXP = new RegExp('mock_files/.+');
const TEMPLATE_REGEXP = new RegExp('_template/.+');
@@ -51,23 +52,31 @@ export const fetchPaginatedGHResults = async (
url: string,
token: string
): Promise => {
+ logger.debug(`Running fetch against ${url}`, { url });
let files: GithubAPIPullRequestFile[] = [];
let nextPageLink: string | null = url;
try {
while (nextPageLink) {
+ logger.debug(`Fetching ${nextPageLink}`, { url: nextPageLink });
const resp = await fetch(nextPageLink, {
headers: { authorization: `token ${token}` },
});
+ // TODO: this should happen after the resp.ok check
const responseJson = await resp.json();
if (!resp.ok) {
+ logger.error(`Error from Github API`, {
+ url: nextPageLink,
+ status: resp.statusText,
+ code: resp.status,
+ });
throw new Error(`Github API returned: ${responseJson.message}`);
}
nextPageLink = getNextLink(resp.headers.get('Link'));
files = [...files, ...responseJson];
}
} catch (error) {
- console.error('Error:', error);
+ logger.error('Error:', { error });
process.exit(1);
}
diff --git a/utils/lib/nr-graphql-helpers.ts b/utils/lib/nr-graphql-helpers.ts
index 8c813f14c1..c5a2485399 100644
--- a/utils/lib/nr-graphql-helpers.ts
+++ b/utils/lib/nr-graphql-helpers.ts
@@ -16,6 +16,7 @@ import {
} from '../constants';
import { Policy } from 'cockatiel';
import fetch, { Response } from 'node-fetch';
+import logger from '../logger';
const NR_API_URL = process.env.NR_API_URL || '';
const NR_API_TOKEN = process.env.NR_API_TOKEN || '';
@@ -62,6 +63,8 @@ export const fetchNRGraphqlResults = async (
try {
const body = buildRequestBody(queryBody);
+ logger.debug(`Running NerdGraph request...`, { url: NR_API_URL, body });
+
const res = await retry.execute(() =>
fetch(NR_API_URL, {
method: 'POST',
@@ -73,19 +76,34 @@ export const fetchNRGraphqlResults = async (
})
);
+ logger.debug(`Received status code`, {
+ status: res.statusText,
+ code: res.status,
+ });
+
if (!res.ok) {
graphqlErrors.push(
new Error(`Received status code ${res.status} from the API`)
);
+
+ logger.error(`Bad response`, {
+ status: res.statusText,
+ code: res.status,
+ });
} else {
const { data, errors } = await res.json();
results = data;
if (errors) {
graphqlErrors = [...graphqlErrors, ...errors];
+
+ // only debug logging here, since we expect validation errors
+ // coming back from nerdgraph
+ logger.debug(`Received errors from NerdGraph`, { errors });
}
}
} catch (error) {
graphqlErrors.push(error as Error);
+ logger.error(`Request errored out`, { error: error });
}
return { data: results, errors: graphqlErrors };
@@ -175,6 +193,9 @@ type CategoryTermsNRGraphqlResults = {
export const getCategoryTermsFromKeywords = async (
configKeywords: string[] | undefined = []
): Promise => {
+ logger.debug(`Fetching categories...`);
+
+ // TODO: handles errors!!
const { data } = await fetchNRGraphqlResults<
{},
CategoryTermsNRGraphqlResults
@@ -182,6 +203,7 @@ export const getCategoryTermsFromKeywords = async (
queryString: CATEGORIES_QUERY,
variables: {},
});
+ logger.debug(`Category result`, { data });
const { categories } = data.actor.nr1Catalog;
@@ -216,10 +238,13 @@ type GetPublishedDataSourceIdsResponse = {
export const getPublishedDataSourceIds =
async (): Promise => {
+ logger.debug(`Fetching all data source Ids`);
+
const { data, errors } = await fetchNRGraphqlResults<
{},
CoreDataSourceSearchResults
>({ queryString: CORE_DATA_SOURCES_QUERY, variables: {} });
+ logger.debug(`Data source Ids result`, { data, errors });
const results = data?.actor?.nr1Catalog?.search?.results ?? [];
@@ -241,6 +266,8 @@ export type GetPublishedComponentIdsResult = {
export const getPublishedComponentIds = async (
quickstartId: string
): Promise => {
+ logger.debug(`Fetching quickstart components for ${quickstartId}`);
+
const { data, errors } = await fetchNRGraphqlResults<
{ id: string },
QuickstartComponentsIdsResponse
@@ -248,6 +275,7 @@ export const getPublishedComponentIds = async (
queryString: QUICKSTART_COMPONENTS_IDS_QUERY,
variables: { id: quickstartId },
});
+ logger.debug(`Quickstart components result`, { data, errors });
const {
metadata: { dataSources, quickstartComponents },
diff --git a/utils/logger.ts b/utils/logger.ts
new file mode 100644
index 0000000000..fbdb901ccc
--- /dev/null
+++ b/utils/logger.ts
@@ -0,0 +1,111 @@
+enum LoggingLevel {
+ ERROR,
+ INFO,
+ DEBUG,
+}
+
+type logFn = (message: string, attributes?: Record) => void;
+
+/*
+ * Logs at the `DEBUG` level
+ */
+export const debug: logFn = (message, attributes) => {
+ if (!shouldLog(LoggingLevel.DEBUG)) {
+ return;
+ }
+
+ return log(message, { ...attributes, LEVEL: LoggingLevel.DEBUG });
+};
+
+/*
+ * Logs at the `INFO` level
+ */
+export const info: logFn = (message, attributes) => {
+ if (!shouldLog(LoggingLevel.INFO)) {
+ return;
+ }
+
+ return log(message, { ...attributes, LEVEL: LoggingLevel.INFO });
+};
+
+/*
+ * The lowest level of logging, `ERROR`, this will always be logged if called
+ */
+export const error: logFn = (message, attributes) => {
+ if (!shouldLog(LoggingLevel.ERROR)) {
+ return;
+ }
+
+ return log(message, { ...attributes, LEVEL: LoggingLevel.ERROR });
+};
+
+/*
+ * Outputs the log, currently this is just to the console
+ * but could be extended.
+ */
+const log: logFn = (message, attributes) => {
+ const datetime = new Date(Date.now());
+
+ logToConsole(message, datetime, attributes);
+};
+
+/*
+ * Formats and logs to the console
+ */
+const logToConsole = (
+ message: string,
+ datetime: Date,
+ attributes?: Record
+) => {
+ const niceDate = datetime.toUTCString();
+ const separator = '-';
+
+ if (attributes) {
+ console.log(niceDate, separator, message, JSON.stringify(attributes));
+ } else {
+ console.log(niceDate, separator, message);
+ }
+};
+
+/*
+ * Determines if a particular log level should be logged based on the
+ * set log level.
+ */
+const shouldLog = (level: LoggingLevel) => {
+ if (level <= readLogLevel()) {
+ return true;
+ }
+ return false;
+};
+
+/*
+ * Reads the log level from the `LOG_LEVEL` environment variable
+ * defaults to INFO level
+ */
+const readLogLevel = (): LoggingLevel => {
+ const logLevel = process.env.LOG_LEVEL;
+
+ switch (logLevel) {
+ case 'ERROR': {
+ // 0
+ return LoggingLevel.ERROR;
+ }
+ case 'INFO': {
+ // 1
+ return LoggingLevel.INFO;
+ }
+ case 'DEBUG': {
+ //2
+ return LoggingLevel.DEBUG;
+ }
+ default: {
+ return LoggingLevel.INFO;
+ }
+ }
+};
+
+export default {
+ debug,
+ error,
+ info,
+};
diff --git a/utils/mock_files/quickstarts/mock-quickstart-11/config.yml b/utils/mock_files/quickstarts/mock-quickstart-11/config.yml
new file mode 100644
index 0000000000..56fa840563
--- /dev/null
+++ b/utils/mock_files/quickstarts/mock-quickstart-11/config.yml
@@ -0,0 +1,39 @@
+# Name of the quickstart (required)
+slug: template-quickstart
+
+# Displayed in the UI (required)
+title: Template Quickstart
+
+# Long-form description of the quickstart (required)
+description: |
+ The template quickstart allows you to get visibility into the performance and available of your example service and dependencies. Use this quickstart together with the mock up integrations.
+
+# Displayed in search results and recommendations. Summarizes a quickstarts functionality.
+summary: |
+ A short form description for this quickstart
+
+# Support level: New Relic | Verified | Community (required)
+level: Community
+
+# Authors of the quickstart (required)
+authors:
+ - John Smith
+
+# No keywords
+
+# Reference to install plans located under /install directory
+# Allows us to construct reusable "install plans" and just use their ID in the quickstart config
+installPlans:
+ - mock-install-1
+
+dataSourceIds:
+ - test-data-source
+
+documentation:
+ - name: Installation Docs
+ url: docs.newrelic.com
+ description: Description about this doc reference
+
+# Content / Design
+icon: logo.png
+website: https://www.newrelic.com
\ No newline at end of file
diff --git a/utils/package.json b/utils/package.json
index 8d7d4006db..4cf5d5a45a 100644
--- a/utils/package.json
+++ b/utils/package.json
@@ -52,6 +52,5 @@
"ts-node": "^10.7.0",
"typescript": "^4.6.4",
"uuid": "^8.3.2"
- },
- "devDependencies": {}
+ }
}
diff --git a/utils/preview.ts b/utils/preview.ts
index a8b9fdda9e..2f28310b69 100644
--- a/utils/preview.ts
+++ b/utils/preview.ts
@@ -16,8 +16,7 @@ const PORT = process.env.PORT || '3000';
const PARENT_DIRECTORY = path.resolve(__dirname, '../quickstarts');
const DASHBOARDS_DIRECTORY = path.resolve(__dirname, '../dashboards');
const ALERTS_DIRECTORY = path.resolve(__dirname, '../alert-policies');
-const BASE_PREVIEW_LINK =
- 'https://newrelic.com/instant-observability/preview?local=true';
+const BASE_PREVIEW_LINK = 'http://localhost:8000/preview?local=true';
const app = express();
diff --git a/utils/set-alert-policy-required-datasources.ts b/utils/set-alert-policy-required-datasources.ts
index a127c9f267..f43132791f 100644
--- a/utils/set-alert-policy-required-datasources.ts
+++ b/utils/set-alert-policy-required-datasources.ts
@@ -8,6 +8,7 @@ import {
import Quickstart from './lib/Quickstart';
import Alert, { SubmitSetRequiredDataSourcesMutationResult } from './lib/Alert';
import { chunk, translateNGErrors } from './lib/nr-graphql-helpers';
+import logger from './logger';
type QuickstartResult = {
name: string;
@@ -28,7 +29,9 @@ const getQuickstartNameAndDataSources = async (
return { hasFailed: true, results: [] };
}
+ logger.info(`Fetching files for pull request ${ghUrl}`);
const files = await fetchPaginatedGHResults(ghUrl, ghToken);
+ logger.info(`Found ${files.length} files`);
const quickstartNames = filterQuickstartConfigFiles(files)
.filter(isNotRemoved)
@@ -126,6 +129,8 @@ const main = async () => {
if (hasFailed) {
process.exit(1);
}
+
+ logger.info('Success!');
};
/**
diff --git a/utils/set-dashboards-required-datasources.ts b/utils/set-dashboards-required-datasources.ts
index 8915f2d2d5..489d539f85 100644
--- a/utils/set-dashboards-required-datasources.ts
+++ b/utils/set-dashboards-required-datasources.ts
@@ -15,6 +15,7 @@ import Dashboard, {
} from './lib/Dashboard';
import { CUSTOM_EVENT, recordNerdGraphResponse } from './newrelic/customEvent';
import { passedProcessArguments } from './lib/helpers';
+import logger from './logger';
const getQuickstartIds = async (
ghUrl?: string,
@@ -30,7 +31,9 @@ const getQuickstartIds = async (
return { hasFailed: true, results: [] };
}
+ logger.info(`Fetching files for pull request ${ghUrl}`);
const files = await fetchPaginatedGHResults(ghUrl, ghToken);
+ logger.info(`Found ${files.length} files`);
const filteredQuickstarts = filterQuickstartConfigFiles(files)
.filter(isNotRemoved)
@@ -171,6 +174,8 @@ const main = async () => {
if (hasFailed) {
process.exit(1);
}
+
+ logger.info('Success!');
};
/**
diff --git a/utils/yarn.lock b/utils/yarn.lock
index 4cc6ad1311..66bb8676be 100644
--- a/utils/yarn.lock
+++ b/utils/yarn.lock
@@ -32,6 +32,14 @@
dependencies:
"@babel/highlight" "^7.16.7"
+"@babel/code-frame@^7.22.13", "@babel/code-frame@^7.23.5":
+ version "7.23.5"
+ resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.23.5.tgz#9009b69a8c602293476ad598ff53e4562e15c244"
+ integrity sha512-CgH3s1a96LipHCmSUmYFPwY7MNx8C3avkq7i4Wl3cfa662ldtUe4VM1TPXX70pfmrlWTb6jLqTYrZyT2ZTJBgA==
+ dependencies:
+ "@babel/highlight" "^7.23.4"
+ chalk "^2.4.2"
+
"@babel/compat-data@^7.17.10":
version "7.17.10"
resolved "https://registry.yarnpkg.com/@babel/compat-data/-/compat-data-7.17.10.tgz#711dc726a492dfc8be8220028b1b92482362baab"
@@ -67,6 +75,16 @@
"@jridgewell/gen-mapping" "^0.3.0"
jsesc "^2.5.1"
+"@babel/generator@^7.23.6":
+ version "7.23.6"
+ resolved "https://registry.yarnpkg.com/@babel/generator/-/generator-7.23.6.tgz#9e1fca4811c77a10580d17d26b57b036133f3c2e"
+ integrity sha512-qrSfCYxYQB5owCmGLbl8XRpX1ytXlpueOb0N0UmQwA073KZxejgQTzAmJezxvpwQD9uGtK2shHdi55QT+MbjIw==
+ dependencies:
+ "@babel/types" "^7.23.6"
+ "@jridgewell/gen-mapping" "^0.3.2"
+ "@jridgewell/trace-mapping" "^0.3.17"
+ jsesc "^2.5.1"
+
"@babel/helper-compilation-targets@^7.17.10":
version "7.17.10"
resolved "https://registry.yarnpkg.com/@babel/helper-compilation-targets/-/helper-compilation-targets-7.17.10.tgz#09c63106d47af93cf31803db6bc49fef354e2ebe"
@@ -84,20 +102,25 @@
dependencies:
"@babel/types" "^7.16.7"
-"@babel/helper-function-name@^7.17.9":
- version "7.17.9"
- resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.17.9.tgz#136fcd54bc1da82fcb47565cf16fd8e444b1ff12"
- integrity sha512-7cRisGlVtiVqZ0MW0/yFB4atgpGLWEHUVYnb448hZK4x+vih0YO5UoS11XIYtZYqHd0dIPMdUSv8q5K4LdMnIg==
+"@babel/helper-environment-visitor@^7.22.20":
+ version "7.22.20"
+ resolved "https://registry.yarnpkg.com/@babel/helper-environment-visitor/-/helper-environment-visitor-7.22.20.tgz#96159db61d34a29dba454c959f5ae4a649ba9167"
+ integrity sha512-zfedSIzFhat/gFhWfHtgWvlec0nqB9YEIVrpuwjruLlXfUSnA8cJB0miHKwqDnQ7d32aKo2xt88/xZptwxbfhA==
+
+"@babel/helper-function-name@^7.23.0":
+ version "7.23.0"
+ resolved "https://registry.yarnpkg.com/@babel/helper-function-name/-/helper-function-name-7.23.0.tgz#1f9a3cdbd5b2698a670c30d2735f9af95ed52759"
+ integrity sha512-OErEqsrxjZTJciZ4Oo+eoZqeW9UIiOcuYKRJA4ZAgV9myA+pOXhhmpfNCKjEH/auVfEYVFJ6y1Tc4r0eIApqiw==
dependencies:
- "@babel/template" "^7.16.7"
- "@babel/types" "^7.17.0"
+ "@babel/template" "^7.22.15"
+ "@babel/types" "^7.23.0"
-"@babel/helper-hoist-variables@^7.16.7":
- version "7.16.7"
- resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.16.7.tgz#86bcb19a77a509c7b77d0e22323ef588fa58c246"
- integrity sha512-m04d/0Op34H5v7pbZw6pSKP7weA6lsMvfiIAMeIvkY/R4xQtBSMFEigu9QTZ2qB/9l22vsxtM8a+Q8CzD255fg==
+"@babel/helper-hoist-variables@^7.22.5":
+ version "7.22.5"
+ resolved "https://registry.yarnpkg.com/@babel/helper-hoist-variables/-/helper-hoist-variables-7.22.5.tgz#c01a007dac05c085914e8fb652b339db50d823bb"
+ integrity sha512-wGjk9QZVzvknA6yKIUURb8zY3grXCcOZt+/7Wcy8O2uctxhplmUPkOdlgoNhmdVee2c92JXbf1xpMtVNbfoxRw==
dependencies:
- "@babel/types" "^7.16.7"
+ "@babel/types" "^7.22.5"
"@babel/helper-module-imports@^7.16.7":
version "7.16.7"
@@ -139,11 +162,28 @@
dependencies:
"@babel/types" "^7.16.7"
+"@babel/helper-split-export-declaration@^7.22.6":
+ version "7.22.6"
+ resolved "https://registry.yarnpkg.com/@babel/helper-split-export-declaration/-/helper-split-export-declaration-7.22.6.tgz#322c61b7310c0997fe4c323955667f18fcefb91c"
+ integrity sha512-AsUnxuLhRYsisFiaJwvp1QF+I3KjD5FOxut14q/GzovUe6orHLesW2C7d754kRm53h5gqrz6sFl6sxc4BVtE/g==
+ dependencies:
+ "@babel/types" "^7.22.5"
+
+"@babel/helper-string-parser@^7.23.4":
+ version "7.23.4"
+ resolved "https://registry.yarnpkg.com/@babel/helper-string-parser/-/helper-string-parser-7.23.4.tgz#9478c707febcbbe1ddb38a3d91a2e054ae622d83"
+ integrity sha512-803gmbQdqwdf4olxrX4AJyFBV/RTr3rSmOj0rKwesmzlfhYNDEs+/iOcznzpNWlJlIlTJC2QfPFcHB6DlzdVLQ==
+
"@babel/helper-validator-identifier@^7.16.7":
version "7.16.7"
resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.16.7.tgz#e8c602438c4a8195751243da9031d1607d247cad"
integrity sha512-hsEnFemeiW4D08A5gUAZxLBTXpZ39P+a+DGDsHw1yxqyQ/jzFEnxf5uTEGp+3bzAbNOxU1paTgYS4ECU/IgfDw==
+"@babel/helper-validator-identifier@^7.22.20":
+ version "7.22.20"
+ resolved "https://registry.yarnpkg.com/@babel/helper-validator-identifier/-/helper-validator-identifier-7.22.20.tgz#c4ae002c61d2879e724581d96665583dbc1dc0e0"
+ integrity sha512-Y4OZ+ytlatR8AI+8KZfKuL5urKp7qey08ha31L8b3BwewJAoJamTzyvxPR/5D+KkdJCGPq/+8TukHBlY10FX9A==
+
"@babel/helper-validator-option@^7.16.7":
version "7.16.7"
resolved "https://registry.yarnpkg.com/@babel/helper-validator-option/-/helper-validator-option-7.16.7.tgz#b203ce62ce5fe153899b617c08957de860de4d23"
@@ -167,11 +207,25 @@
chalk "^2.0.0"
js-tokens "^4.0.0"
+"@babel/highlight@^7.23.4":
+ version "7.23.4"
+ resolved "https://registry.yarnpkg.com/@babel/highlight/-/highlight-7.23.4.tgz#edaadf4d8232e1a961432db785091207ead0621b"
+ integrity sha512-acGdbYSfp2WheJoJm/EBBBLh/ID8KDc64ISZ9DYtBmC8/Q204PZJLHyzeB5qMzJ5trcOkybd78M4x2KWsUq++A==
+ dependencies:
+ "@babel/helper-validator-identifier" "^7.22.20"
+ chalk "^2.4.2"
+ js-tokens "^4.0.0"
+
"@babel/parser@^7.1.0", "@babel/parser@^7.14.7", "@babel/parser@^7.16.7", "@babel/parser@^7.18.0":
version "7.18.0"
resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.18.0.tgz#10a8d4e656bc01128d299a787aa006ce1a91e112"
integrity sha512-AqDccGC+m5O/iUStSJy3DGRIUFu7WbY/CppZYwrEUB4N0tZlnI8CSTsgL7v5fHVFmUbRv2sd+yy27o8Ydt4MGg==
+"@babel/parser@^7.22.15", "@babel/parser@^7.23.6":
+ version "7.23.6"
+ resolved "https://registry.yarnpkg.com/@babel/parser/-/parser-7.23.6.tgz#ba1c9e512bda72a47e285ae42aff9d2a635a9e3b"
+ integrity sha512-Z2uID7YJ7oNvAI20O9X0bblw7Qqs8Q2hFy0R9tAfnfLkp5MW0UH9eUvnDSnFwKZ0AvgS1ucqR4KzvVHgnke1VQ==
+
"@babel/plugin-syntax-async-generators@^7.8.4":
version "7.8.4"
resolved "https://registry.yarnpkg.com/@babel/plugin-syntax-async-generators/-/plugin-syntax-async-generators-7.8.4.tgz#a983fb1aeb2ec3f6ed042a210f640e90e786fe0d"
@@ -272,20 +326,29 @@
"@babel/parser" "^7.16.7"
"@babel/types" "^7.16.7"
-"@babel/traverse@^7.18.0", "@babel/traverse@^7.7.2":
- version "7.18.0"
- resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.18.0.tgz#0e5ec6db098660b2372dd63d096bf484e32d27ba"
- integrity sha512-oNOO4vaoIQoGjDQ84LgtF/IAlxlyqL4TUuoQ7xLkQETFaHkY1F7yazhB4Kt3VcZGL0ZF/jhrEpnXqUb0M7V3sw==
+"@babel/template@^7.22.15":
+ version "7.22.15"
+ resolved "https://registry.yarnpkg.com/@babel/template/-/template-7.22.15.tgz#09576efc3830f0430f4548ef971dde1350ef2f38"
+ integrity sha512-QPErUVm4uyJa60rkI73qneDacvdvzxshT3kksGqlGWYdOTIUOwJ7RDUL8sGqslY1uXWSL6xMFKEXDS3ox2uF0w==
dependencies:
- "@babel/code-frame" "^7.16.7"
- "@babel/generator" "^7.18.0"
- "@babel/helper-environment-visitor" "^7.16.7"
- "@babel/helper-function-name" "^7.17.9"
- "@babel/helper-hoist-variables" "^7.16.7"
- "@babel/helper-split-export-declaration" "^7.16.7"
- "@babel/parser" "^7.18.0"
- "@babel/types" "^7.18.0"
- debug "^4.1.0"
+ "@babel/code-frame" "^7.22.13"
+ "@babel/parser" "^7.22.15"
+ "@babel/types" "^7.22.15"
+
+"@babel/traverse@^7.18.0", "@babel/traverse@^7.7.2":
+ version "7.23.6"
+ resolved "https://registry.yarnpkg.com/@babel/traverse/-/traverse-7.23.6.tgz#b53526a2367a0dd6edc423637f3d2d0f2521abc5"
+ integrity sha512-czastdK1e8YByZqezMPFiZ8ahwVMh/ESl9vPgvgdB9AmFMGP5jfpFax74AQgl5zj4XHzqeYAg2l8PuUeRS1MgQ==
+ dependencies:
+ "@babel/code-frame" "^7.23.5"
+ "@babel/generator" "^7.23.6"
+ "@babel/helper-environment-visitor" "^7.22.20"
+ "@babel/helper-function-name" "^7.23.0"
+ "@babel/helper-hoist-variables" "^7.22.5"
+ "@babel/helper-split-export-declaration" "^7.22.6"
+ "@babel/parser" "^7.23.6"
+ "@babel/types" "^7.23.6"
+ debug "^4.3.1"
globals "^11.1.0"
"@babel/types@^7.0.0", "@babel/types@^7.16.7", "@babel/types@^7.17.0", "@babel/types@^7.18.0", "@babel/types@^7.3.0", "@babel/types@^7.3.3":
@@ -296,6 +359,15 @@
"@babel/helper-validator-identifier" "^7.16.7"
to-fast-properties "^2.0.0"
+"@babel/types@^7.22.15", "@babel/types@^7.22.5", "@babel/types@^7.23.0", "@babel/types@^7.23.6":
+ version "7.23.6"
+ resolved "https://registry.yarnpkg.com/@babel/types/-/types-7.23.6.tgz#be33fdb151e1f5a56877d704492c240fc71c7ccd"
+ integrity sha512-+uarb83brBzPKN38NX1MkB6vb6+mwvR6amUulqAE7ccQw1pEl+bCia9TbdG1lsnFP7lZySvUn37CHyXQdfTwzg==
+ dependencies:
+ "@babel/helper-string-parser" "^7.23.4"
+ "@babel/helper-validator-identifier" "^7.22.20"
+ to-fast-properties "^2.0.0"
+
"@bcoe/v8-coverage@^0.2.3":
version "0.2.3"
resolved "https://registry.yarnpkg.com/@bcoe/v8-coverage/-/v8-coverage-0.2.3.tgz#75a2e8b51cb758a7553d6804a5932d7aace75c39"
@@ -510,21 +582,45 @@
"@jridgewell/sourcemap-codec" "^1.4.10"
"@jridgewell/trace-mapping" "^0.3.9"
+"@jridgewell/gen-mapping@^0.3.2":
+ version "0.3.3"
+ resolved "https://registry.yarnpkg.com/@jridgewell/gen-mapping/-/gen-mapping-0.3.3.tgz#7e02e6eb5df901aaedb08514203b096614024098"
+ integrity sha512-HLhSWOLRi875zjjMG/r+Nv0oCW8umGb0BgEhyX3dDX3egwZtB8PqLnjz3yedt8R5StBrzcg4aBpnh8UA9D1BoQ==
+ dependencies:
+ "@jridgewell/set-array" "^1.0.1"
+ "@jridgewell/sourcemap-codec" "^1.4.10"
+ "@jridgewell/trace-mapping" "^0.3.9"
+
"@jridgewell/resolve-uri@^3.0.3":
version "3.0.7"
resolved "https://registry.yarnpkg.com/@jridgewell/resolve-uri/-/resolve-uri-3.0.7.tgz#30cd49820a962aff48c8fffc5cd760151fca61fe"
integrity sha512-8cXDaBBHOr2pQ7j77Y6Vp5VDT2sIqWyWQ56TjEq4ih/a4iST3dItRe8Q9fp0rrIl9DoKhWQtUQz/YpOxLkXbNA==
+"@jridgewell/resolve-uri@^3.1.0":
+ version "3.1.1"
+ resolved "https://registry.yarnpkg.com/@jridgewell/resolve-uri/-/resolve-uri-3.1.1.tgz#c08679063f279615a3326583ba3a90d1d82cc721"
+ integrity sha512-dSYZh7HhCDtCKm4QakX0xFpsRDqjjtZf/kjI/v3T3Nwt5r8/qz/M19F9ySyOqU94SXBmeG9ttTul+YnR4LOxFA==
+
"@jridgewell/set-array@^1.0.0":
version "1.1.1"
resolved "https://registry.yarnpkg.com/@jridgewell/set-array/-/set-array-1.1.1.tgz#36a6acc93987adcf0ba50c66908bd0b70de8afea"
integrity sha512-Ct5MqZkLGEXTVmQYbGtx9SVqD2fqwvdubdps5D3djjAkgkKwT918VNOz65pEHFaYTeWcukmJmH5SwsA9Tn2ObQ==
+"@jridgewell/set-array@^1.0.1":
+ version "1.1.2"
+ resolved "https://registry.yarnpkg.com/@jridgewell/set-array/-/set-array-1.1.2.tgz#7c6cf998d6d20b914c0a55a91ae928ff25965e72"
+ integrity sha512-xnkseuNADM0gt2bs+BvhO0p78Mk762YnZdsuzFV018NoG1Sj1SCQvpSqa7XUaTam5vAGasABV9qXASMKnFMwMw==
+
"@jridgewell/sourcemap-codec@^1.4.10":
version "1.4.13"
resolved "https://registry.yarnpkg.com/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.13.tgz#b6461fb0c2964356c469e115f504c95ad97ab88c"
integrity sha512-GryiOJmNcWbovBxTfZSF71V/mXbgcV3MewDe3kIMCLyIh5e7SKAeUZs+rMnJ8jkMolZ/4/VsdBmMrw3l+VdZ3w==
+"@jridgewell/sourcemap-codec@^1.4.14":
+ version "1.4.15"
+ resolved "https://registry.yarnpkg.com/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.15.tgz#d7c6e6755c78567a951e04ab52ef0fd26de59f32"
+ integrity sha512-eF2rxCRulEKXHTRiDrDy6erMYWqNw4LPdQ8UQA4huuxaQsVeRPFl2oM8oDGxMFhJUWZf9McpLtJasDDZb/Bpeg==
+
"@jridgewell/trace-mapping@0.3.9":
version "0.3.9"
resolved "https://registry.yarnpkg.com/@jridgewell/trace-mapping/-/trace-mapping-0.3.9.tgz#6534fd5933a53ba7cbf3a17615e273a0d1273ff9"
@@ -533,6 +629,14 @@
"@jridgewell/resolve-uri" "^3.0.3"
"@jridgewell/sourcemap-codec" "^1.4.10"
+"@jridgewell/trace-mapping@^0.3.17":
+ version "0.3.20"
+ resolved "https://registry.yarnpkg.com/@jridgewell/trace-mapping/-/trace-mapping-0.3.20.tgz#72e45707cf240fa6b081d0366f8265b0cd10197f"
+ integrity sha512-R8LcPeWZol2zR8mmH3JeKQ6QRCFb7XgUhV9ZlGhHLGyg4wpPiPZNQOOWhFZhxKw8u//yTbNGI42Bx/3paXEQ+Q==
+ dependencies:
+ "@jridgewell/resolve-uri" "^3.1.0"
+ "@jridgewell/sourcemap-codec" "^1.4.14"
+
"@jridgewell/trace-mapping@^0.3.9":
version "0.3.13"
resolved "https://registry.yarnpkg.com/@jridgewell/trace-mapping/-/trace-mapping-0.3.13.tgz#dcfe3e95f224c8fe97a87a5235defec999aa92ea"
@@ -1075,7 +1179,7 @@ caniuse-lite@^1.0.30001332:
resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30001341.tgz#59590c8ffa8b5939cf4161f00827b8873ad72498"
integrity sha512-2SodVrFFtvGENGCv0ChVJIDQ0KPaS1cg7/qtfMaICgeMolDdo/Z2OD32F0Aq9yl6F4YFwGPBS5AaPqNYiW4PoA==
-chalk@^2.0.0:
+chalk@^2.0.0, chalk@^2.4.2:
version "2.4.2"
resolved "https://registry.yarnpkg.com/chalk/-/chalk-2.4.2.tgz#cd42541677a54333cf541a49108c1432b44c9424"
integrity sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==
@@ -1251,7 +1355,7 @@ debug@2.6.9:
dependencies:
ms "2.0.0"
-debug@4, debug@^4.1.0, debug@^4.1.1:
+debug@4, debug@^4.1.0, debug@^4.1.1, debug@^4.3.1:
version "4.3.4"
resolved "https://registry.yarnpkg.com/debug/-/debug-4.3.4.tgz#1319f6579357f2338d3337d2cdd4914bb5dcc865"
integrity sha512-PRWFHuSU3eDtQJPvnNY7Jcket1j0t5OuOsFzPPzsekD52Zl8qUfFIPEiswXqIvHWGVHOgX+7G/vCNNhehwxfkQ==
@@ -2290,9 +2394,9 @@ json-schema-traverse@^1.0.0:
integrity sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==
json5@2.x, json5@^2.2.1:
- version "2.2.1"
- resolved "https://registry.yarnpkg.com/json5/-/json5-2.2.1.tgz#655d50ed1e6f95ad1a3caababd2b0efda10b395c"
- integrity sha512-1hqLFMSrGHRHxav9q9gNjJ5EXznIxGVO09xQRrwplcS8qs28pZ8s8hupZAmqDwZUmVZ2Qb2jnyPOWcDH8m8dlA==
+ version "2.2.3"
+ resolved "https://registry.yarnpkg.com/json5/-/json5-2.2.3.tgz#78cd6f1a19bdc12b73db5ad0c61efd66c1e29283"
+ integrity sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==
kleur@^3.0.3:
version "3.0.3"