diff --git a/alert-policies/amazon-sagemaker/HighModelInvocationErrors.yml b/alert-policies/amazon-sagemaker/HighModelInvocationErrors.yml index bbfc1a922e..d15d79253e 100644 --- a/alert-policies/amazon-sagemaker/HighModelInvocationErrors.yml +++ b/alert-policies/amazon-sagemaker/HighModelInvocationErrors.yml @@ -5,7 +5,7 @@ description: |+ type: STATIC nrql: - query: "SELECT count(`aws.sagemaker.InvocationModelErrors`) as 'Query' FROM Metric" + query: "SELECT sum(`aws.sagemaker.InvocationModelErrors`) as 'Query' FROM Metric" # Function used to aggregate the NRQL query value(s) for comparison to the terms.threshold (Default: SINGLE_VALUE) valueFunction: SINGLE_VALUE @@ -24,4 +24,4 @@ terms: # Duration after which a violation automatically closes # Time in seconds; 300 - 2592000 (Default: 86400 [1 day]) -violationTimeLimitSeconds: 86400 \ No newline at end of file +violationTimeLimitSeconds: 86400 diff --git a/alert-policies/nvidia-gpu/HighMemoryUtilization.yml b/alert-policies/nvidia-gpu/HighMemoryUtilization.yml new file mode 100644 index 0000000000..e003127f7e --- /dev/null +++ b/alert-policies/nvidia-gpu/HighMemoryUtilization.yml @@ -0,0 +1,27 @@ +name: High GPU Memory Utilization + +description: |+ + This alert is triggered when the Nvidia GPU memory utilization is above 90%. + +type: STATIC +nrql: + query: "SELECT latest(utilization.memory.percent) FROM NvidiaGpuSample" + +# Function used to aggregate the NRQL query value(s) for comparison to the terms.threshold (Default: SINGLE_VALUE) +valueFunction: SINGLE_VALUE + +# List of Critical and Warning thresholds for the condition +terms: + - priority: CRITICAL + # Operator used to compare against the threshold. + operator: ABOVE + # Value that triggers a violation + threshold: 90 + # Time in seconds; 120 - 3600 + thresholdDuration: 300 + # How many data points must be in violation for the duration + thresholdOccurrences: ALL + +# Duration after which a violation automatically closes +# Time in seconds; 300 - 2592000 (Default: 86400 [1 day]) +violationTimeLimitSeconds: 86400 diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard01.jpg b/dashboards/datazoom-dashboard/datazoom_dashboard01.jpg new file mode 100644 index 0000000000..c592d706ce Binary files /dev/null and b/dashboards/datazoom-dashboard/datazoom_dashboard01.jpg differ diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard01.png b/dashboards/datazoom-dashboard/datazoom_dashboard01.png deleted file mode 100644 index fc23369fc4..0000000000 Binary files a/dashboards/datazoom-dashboard/datazoom_dashboard01.png and /dev/null differ diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard02.jpg b/dashboards/datazoom-dashboard/datazoom_dashboard02.jpg new file mode 100644 index 0000000000..8b5faeb218 Binary files /dev/null and b/dashboards/datazoom-dashboard/datazoom_dashboard02.jpg differ diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard02.png b/dashboards/datazoom-dashboard/datazoom_dashboard02.png deleted file mode 100644 index 42baf23df5..0000000000 Binary files a/dashboards/datazoom-dashboard/datazoom_dashboard02.png and /dev/null differ diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard03.jpg b/dashboards/datazoom-dashboard/datazoom_dashboard03.jpg new file mode 100644 index 0000000000..f72f516fa4 Binary files /dev/null and b/dashboards/datazoom-dashboard/datazoom_dashboard03.jpg differ diff --git a/dashboards/datazoom-dashboard/datazoom_dashboard04.jpg b/dashboards/datazoom-dashboard/datazoom_dashboard04.jpg new file mode 100644 index 0000000000..6211bae761 Binary files /dev/null and b/dashboards/datazoom-dashboard/datazoom_dashboard04.jpg differ diff --git a/dashboards/mexn/mexn01.png b/dashboards/mexn/mexn001.png similarity index 100% rename from dashboards/mexn/mexn01.png rename to dashboards/mexn/mexn001.png diff --git a/dashboards/mexn/mexn02.png b/dashboards/mexn/mexn002.png similarity index 100% rename from dashboards/mexn/mexn02.png rename to dashboards/mexn/mexn002.png diff --git a/dashboards/mexn/mexn03.png b/dashboards/mexn/mexn003.png similarity index 100% rename from dashboards/mexn/mexn03.png rename to dashboards/mexn/mexn003.png diff --git a/dashboards/mexn/mexn04.png b/dashboards/mexn/mexn004.png similarity index 100% rename from dashboards/mexn/mexn04.png rename to dashboards/mexn/mexn004.png diff --git a/dashboards/mexn/mexn05.png b/dashboards/mexn/mexn005.png similarity index 100% rename from dashboards/mexn/mexn05.png rename to dashboards/mexn/mexn005.png diff --git a/dashboards/mexn/mexn06.png b/dashboards/mexn/mexn006.png similarity index 100% rename from dashboards/mexn/mexn06.png rename to dashboards/mexn/mexn006.png diff --git a/dashboards/mexn/mexn07.png b/dashboards/mexn/mexn007.png similarity index 100% rename from dashboards/mexn/mexn07.png rename to dashboards/mexn/mexn007.png diff --git a/dashboards/mexn/mexn08.png b/dashboards/mexn/mexn008.png similarity index 100% rename from dashboards/mexn/mexn08.png rename to dashboards/mexn/mexn008.png diff --git a/dashboards/mexn/mexn09.png b/dashboards/mexn/mexn009.png similarity index 100% rename from dashboards/mexn/mexn09.png rename to dashboards/mexn/mexn009.png diff --git a/dashboards/mexn/mexn10.png b/dashboards/mexn/mexn010.png similarity index 100% rename from dashboards/mexn/mexn10.png rename to dashboards/mexn/mexn010.png diff --git a/dashboards/nvidia-gpu/nvidia-gpu.json b/dashboards/nvidia-gpu/nvidia-gpu.json new file mode 100644 index 0000000000..1960651000 --- /dev/null +++ b/dashboards/nvidia-gpu/nvidia-gpu.json @@ -0,0 +1,190 @@ +{ + "name": "Nvidia GPU Monitoring", + "description": null, + "pages": [ + { + "name": "Nvidia GPU Monitoring", + "description": null, + "widgets": [ + { + "visualization": { + "id": "viz.markdown" + }, + "layout": { + "column": 1, + "row": 1, + "height": 1, + "width": 4 + }, + "title": "", + "rawConfiguration": { + "text": "[![NVIDIA SMI](https://logos-download.com/wp-content/uploads/2016/10/Nvidia_logo.png)](https://developer.nvidia.com/nvidia-system-management-interface)\n" + } + }, + { + "visualization": { + "id": "viz.billboard" + }, + "layout": { + "column": 5, + "row": 1, + "height": 3, + "width": 2 + }, + "title": "Current Clock Speeds", + "rawConfiguration": { + "dataFormatters": [], + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(clocks.current.memory.MHz) as 'Memory MHz', latest(clocks.current.graphics.MHz) as 'Graphics MHz', latest(clocks.current.video.MHz) as 'Video MHz', latest(clocks.current.sm.MHz) as 'SM MHz' " + } + ], + "thresholds": [] + } + }, + { + "visualization": { + "id": "viz.line" + }, + "layout": { + "column": 7, + "row": 1, + "height": 3, + "width": 6 + }, + "title": "Current Clock MHz", + "rawConfiguration": { + "legend": { + "enabled": true + }, + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(clocks.current.memory.MHz) as 'Memory MHz', latest(clocks.current.graphics.MHz) as 'Graphics MHz', latest(clocks.current.video.MHz) as 'Video MHz', latest(clocks.current.sm.MHz) as 'SM MHz' TIMESERIES" + } + ], + "yAxisLeft": { + "zero": true + } + } + }, + { + "visualization": { + "id": "viz.bar" + }, + "layout": { + "column": 1, + "row": 2, + "height": 2, + "width": 4 + }, + "title": "Select GPU", + "rawConfiguration": { + "facet": { + "showOtherSeries": false + }, + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(name) FACET pci.device_id, hostname " + } + ] + } + }, + { + "visualization": { + "id": "viz.billboard" + }, + "layout": { + "column": 1, + "row": 4, + "height": 3, + "width": 2 + }, + "title": "Temps", + "rawConfiguration": { + "dataFormatters": [], + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(temperature.gpu) as 'GPU Temp', latest(temperature.memory) as 'Memory Temp', latest(fan.speed.percent) as 'Fan speed %'" + } + ], + "thresholds": [] + } + }, + { + "visualization": { + "id": "viz.billboard" + }, + "layout": { + "column": 3, + "row": 4, + "height": 3, + "width": 2 + }, + "title": "Power Usage", + "rawConfiguration": { + "dataFormatters": [], + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(power.draw.watts) as 'Power Draw Watts', latest(`power.limit.watts`) as 'Power Limit Watts', latest(power.draw.watts)/latest(`power.limit.watts`) * 100 as 'Power usage %'" + } + ], + "thresholds": [] + } + }, + { + "visualization": { + "id": "viz.billboard" + }, + "layout": { + "column": 5, + "row": 4, + "height": 3, + "width": 2 + }, + "title": "Memory Usage", + "rawConfiguration": { + "dataFormatters": [], + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(memory.free.MiB) as 'Memory Free MiB', latest(memory.used.MiB) as 'Memory Used MiB', latest(memory.total.MiB) as 'Memory Total MiB'" + } + ], + "thresholds": [] + } + }, + { + "visualization": { + "id": "viz.line" + }, + "layout": { + "column": 7, + "row": 4, + "height": 3, + "width": 6 + }, + "title": "Utilization", + "rawConfiguration": { + "legend": { + "enabled": true + }, + "nrqlQueries": [ + { + "accountId": 123, + "query": "FROM NvidiaGpuSample SELECT latest(memory.used.MiB/memory.total.MiB) * 100 as 'Memory Used %', latest(utilization.gpu.percent) as 'GPU Utilization %', latest(power.draw.watts)/latest(`power.limit.watts`)*100 as 'Power Usage %', latest(fan.speed.percent) as 'Fan Speed %' TIMESERIES" + } + ], + "yAxisLeft": { + "zero": true + } + } + } + ] + } + ] + } \ No newline at end of file diff --git a/dashboards/nvidia-gpu/nvidia-gpu.png b/dashboards/nvidia-gpu/nvidia-gpu.png new file mode 100644 index 0000000000..0eb50a6864 Binary files /dev/null and b/dashboards/nvidia-gpu/nvidia-gpu.png differ diff --git a/data-sources/dojo/config.yml b/data-sources/dojo/config.yml index 16343a3af2..8beb898d7f 100644 --- a/data-sources/dojo/config.yml +++ b/data-sources/dojo/config.yml @@ -4,6 +4,9 @@ description: | With New Relic, monitor your Dojo solution to get full visibility into the core web vitals performance of your application or website. install: primary: - link: - url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/dojo-io-integration/ + nerdlet: + nerdletId: marketplace.install-data-source + nerdletState: + dataSourceId: dojo + requiresAccount: false icon: logo.png diff --git a/data-sources/flutter-web/config.yml b/data-sources/flutter-web/config.yml index 12a88eedc6..fef3f14640 100644 --- a/data-sources/flutter-web/config.yml +++ b/data-sources/flutter-web/config.yml @@ -5,9 +5,11 @@ description: | icon: logo.png install: primary: - link: - url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/browser-monitoring-integrations/flutter-web-integration/ - + nerdlet: + nerdletId: marketplace.install-data-source + nerdletState: + dataSourceId: flutter-web + requiresAccount: false keywords: - flutter - flutter web application diff --git a/data-sources/jfrog-platform/config.yml b/data-sources/jfrog-platform/config.yml index e408be9708..d3bffb1bd1 100644 --- a/data-sources/jfrog-platform/config.yml +++ b/data-sources/jfrog-platform/config.yml @@ -4,5 +4,5 @@ description: Observe JFrog Platform and gain insights using New Relic Observabil install: primary: link: - url: https://github.com/jfrog/log-analytics-newrelic + url: https://jfrog.com/help/r/jfrog-platform-administration-documentation/new-relic icon: icon.svg diff --git a/data-sources/jira-errors-inbox/config.yml b/data-sources/jira-errors-inbox/config.yml index 8fef35fa18..15bd34201d 100644 --- a/data-sources/jira-errors-inbox/config.yml +++ b/data-sources/jira-errors-inbox/config.yml @@ -3,6 +3,9 @@ displayName: Atlassian Jira for Errors Inbox description: Integrated errors inbox with Atlassian Jira (cloud) to easily create tickets for your errors. install: primary: - link: - url: https://docs.newrelic.com/docs/errors-inbox/errors-inbox/#jira + nerdlet: + nerdletId: marketplace.install-data-source + nerdletState: + dataSourceId: jira-errors-inbox + requiresAccount: false icon: logo.svg diff --git a/data-sources/nextcloud/config.yml b/data-sources/nextcloud/config.yml index 580eb62f3a..560be37e65 100644 --- a/data-sources/nextcloud/config.yml +++ b/data-sources/nextcloud/config.yml @@ -4,6 +4,9 @@ description: | Use our infrastructure agent and the Prometheus open metric integration to monitor the performance of the processes on your Nextcloud server. install: primary: - link: - url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/nextcloud-integration/ + nerdlet: + nerdletId: marketplace.install-data-source + nerdletState: + dataSourceId: nextcloud + requiresAccount: false icon: logo.png diff --git a/data-sources/nvidia-gpu/config.yml b/data-sources/nvidia-gpu/config.yml new file mode 100644 index 0000000000..c837e167f7 --- /dev/null +++ b/data-sources/nvidia-gpu/config.yml @@ -0,0 +1,19 @@ +id: nvidia-gpu +displayName: Nvidia GPUs +description: | + Monitor Nvidia GPUs based on the Nvidia SMI utility. + +install: + primary: + link: + url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/nvidia-gpu-integration/ + +icon: logo.png + +keywords: + - infrastructure + - nvidia + - gpu + +categoryTerms: + - infrastructure \ No newline at end of file diff --git a/data-sources/nvidia-gpu/logo.png b/data-sources/nvidia-gpu/logo.png new file mode 100644 index 0000000000..00e777df8c Binary files /dev/null and b/data-sources/nvidia-gpu/logo.png differ diff --git a/data-sources/shopify/config.yml b/data-sources/shopify/config.yml new file mode 100644 index 0000000000..05b6fabba1 --- /dev/null +++ b/data-sources/shopify/config.yml @@ -0,0 +1,17 @@ +id: shopify +displayName: Shopify +description: | + Shopify is a website building tool. You can use New Relic's browser agent to monitor your websites created in Shopify. +icon: logo.png +install: + primary: + link: + url: https://docs.newrelic.com/docs/browser/browser-monitoring/installation/install-browser-monitoring-agent/ +keywords: + - traffic + - browser + - agent + - web app + - newrelic partner +categoryTerms: + - newrelic partner diff --git a/data-sources/shopify/logo.png b/data-sources/shopify/logo.png new file mode 100644 index 0000000000..7cd4ecd1d1 Binary files /dev/null and b/data-sources/shopify/logo.png differ 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/flutter-web/install.yml b/install/flutter-web/install.yml deleted file mode 100644 index b1784103ec..0000000000 --- a/install/flutter-web/install.yml +++ /dev/null @@ -1,15 +0,0 @@ -id: flutter-web -name: Flutter Web -title: Flutter Web monitoring -description: | - New Relic’s instant observability quickstart with Flutter Web monitoring can be used to analyze performance bottlenecks in the production environment. Visually monitor your web user experience across the world along with your application performance via the dashboard. - -target: - type: integration - destination: host - os: - - linux -install: - mode: link - destination: - url: https://docs.newrelic.com/docs/infrastructure/host-integrations/host-integrations-list/browser-monitoring-integrations/flutter-web-integration/ 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/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/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 @@ + + + docarray-logo_text-light + + + + + + + + + + + + + + + + + \ 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 @@ + + + docarray-logo_text-light + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/quickstarts/docarray/config.yml b/quickstarts/docarray/config.yml deleted file mode 100644 index 25f14aca7a..0000000000 --- a/quickstarts/docarray/config.yml +++ /dev/null @@ -1,58 +0,0 @@ -id: c264449d-e7a1-4497-9b73-df1bdfe79f82 - -slug: docarray-inmemorysearch -description: | - ## Why should you monitor your usage of Doc Array InMemorySearch? - - Monitor your vector searches on Doc Array InMemorySearch to get visibility on what you send to Doc Array InMemorySearch, responses retrieved from Doc Array InMemorySearch, 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 Doc Array InMemorySearch quickstart. -icon: logo.png -level: New Relic -authors: - - New Relic -title: Doc Array InMemorySearch -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: - - 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/logo.png b/quickstarts/docarray/logo.png deleted file mode 100644 index e21fc630bf..0000000000 Binary files a/quickstarts/docarray/logo.png and /dev/null differ 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/elastic-vector-search/config.yml b/quickstarts/elastic-vector-search/config.yml index 6712b4f197..a3b0a70a72 100644 --- a/quickstarts/elastic-vector-search/config.yml +++ b/quickstarts/elastic-vector-search/config.yml @@ -3,35 +3,33 @@ 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. - Monitor your vector searches on Elastic Vector Search to get visibility on what you send to Elastic Vector Search, responses retrieved from Elastic Vector Search, 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 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 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. + ### 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? - - Elastic Vector Search uses New Relic Langchain monitoring which provides a variety of pre-built dashboards, which will help you gain insights into the health and performance of your Elastic Vector Search app. These reports include: + 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 Vector search's performance and quality with New Relic Elastic Vector Search quickstart. + 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: LangChain Vector Database integration documentation + - name: Elastic Vector Search 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. + 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 diff --git a/quickstarts/flutter-web/config.yml b/quickstarts/flutter-web/config.yml index d94cc7c384..5aefae2eca 100644 --- a/quickstarts/flutter-web/config.yml +++ b/quickstarts/flutter-web/config.yml @@ -34,8 +34,6 @@ keywords: - flutter - flutter web application - browser agent -installPlans: - - flutter-web dataSourceIds: - flutter-web dashboards: 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 ec2adfca15..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 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/jfrog-platform/config.yml b/quickstarts/jfrog-platform/config.yml index fb39f68fa0..cb48405615 100644 --- a/quickstarts/jfrog-platform/config.yml +++ b/quickstarts/jfrog-platform/config.yml @@ -34,11 +34,12 @@ keywords: - 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 index f8c5a087ad..43b88143fb 100644 --- a/quickstarts/jina-ai/config.yml +++ b/quickstarts/jina-ai/config.yml @@ -19,7 +19,7 @@ description: | - 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.svg +icon: logo.jpeg level: - New Relic authors: 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/jina-ai/logo.svg b/quickstarts/jina-ai/logo.svg deleted file mode 100644 index 79c4690d64..0000000000 --- a/quickstarts/jina-ai/logo.svg +++ /dev/null @@ -1,13 +0,0 @@ - - - Company logo_dark - - - - - - - - - - \ No newline at end of file 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/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/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/redpanda/config.yml b/quickstarts/redpanda/config.yml index be556b9fc2..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. 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/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 @@ + + + + + + + + + + + + + + + + + + + + +