diff --git a/src/content/docs/alerts/incident-management/postmortems-applied-intelligence.mdx b/src/content/docs/alerts/incident-management/postmortems-applied-intelligence.mdx index 2de9a3eab71..074d6c288e9 100644 --- a/src/content/docs/alerts/incident-management/postmortems-applied-intelligence.mdx +++ b/src/content/docs/alerts/incident-management/postmortems-applied-intelligence.mdx @@ -20,8 +20,10 @@ import accountsPostmortem6 from 'images/accounts_screenshot-crop_postmortem-6.we import accountsPostmortemEdit from 'images/accounts_screenshot-full_postmortem-edit.webp' - -This feature is still in development, but we encourage you to try it out. + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). With alerts' postmortems feature, events, metrics, and metadata are automatically collected to create a template you can use to run an incident postmortem for your team. diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/atlassian-integration.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/atlassian-integration.mdx index 40f558598d7..1197782a786 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/atlassian-integration.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/atlassian-integration.mdx @@ -21,8 +21,10 @@ import opentelemetryJiraNRConfiguration from 'images/opentelemetry_screenshot-fu New Relic offers an integration with Atlassian Jira that syncs your New Relic issue and incident information with Jira. This data then appears in Jira in the [incidents feature](https://support.atlassian.com/jira-software-cloud/docs/what-is-the-incidents-feature/) and lets you connect it with Jira issues to improve your outage workflows. The sections cover how to set up this integration and best practices for using it. - - This feature is still in preview, but we encourage you to try it out! + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx index f33497e6979..ed6632a0cbd 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx @@ -17,8 +17,11 @@ import OsLinux from 'images/os_icon_linux.webp' import OsWindows from 'images/os_icon_windows.webp' - - This feature is currently a public preview. + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). Our IBM MQ [integration](/docs/integrations/host-integrations/getting-started/introduction-host-integrations) diff --git a/src/content/docs/infrastructure/host-integrations/host-integrations-list/powerdns-monitoring-integration.mdx b/src/content/docs/infrastructure/host-integrations/host-integrations-list/powerdns-monitoring-integration.mdx index d1b631e0a01..c2e3879eaa7 100644 --- a/src/content/docs/infrastructure/host-integrations/host-integrations-list/powerdns-monitoring-integration.mdx +++ b/src/content/docs/infrastructure/host-integrations/host-integrations-list/powerdns-monitoring-integration.mdx @@ -11,8 +11,12 @@ redirects: freshnessValidatedDate: never --- - - This feature is currently in public preview and only applies to the versions starting on [0.0.5](https://github.com/newrelic/newrelic-prometheus-exporters-packages/releases/tag/nri-powerdns-0.0.5) released in October 2021. + + We're still working on this feature, but we'd love for you to try it out! + + It only applies to the versions starting on [0.0.5](https://github.com/newrelic/newrelic-prometheus-exporters-packages/releases/tag/nri-powerdns-0.0.5) released in October 2021. + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). Our PowerDNS [integration](/docs/integrations/host-integrations/getting-started/introduction-host-integrations) diff --git a/src/content/docs/instrumentation-editor-instrument-net-ui.mdx b/src/content/docs/instrumentation-editor-instrument-net-ui.mdx index ea8a812d71e..6ca49a5cc75 100644 --- a/src/content/docs/instrumentation-editor-instrument-net-ui.mdx +++ b/src/content/docs/instrumentation-editor-instrument-net-ui.mdx @@ -9,10 +9,13 @@ freshnessValidatedDate: never import apmDotnetInstrumentationEditor from 'images/apm_screenshot-full_dotnet-instrumentation-editor.webp' - - This feature is currently in preview. + +We're still working on this feature, but we'd love for you to try it out! + +If you have questions or feedback, or if you need help during the preview of the .NET agent's **Instrumentation** editor, send an email to [dotnet-li-editor-beta@newrelic.com](mailto:dotnet-li-editor-beta@newrelic.com). + +This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). - If you have questions or feedback, or if you need help during the preview of the .NET agent's **Instrumentation** editor, send an email to [dotnet-li-editor-beta@newrelic.com](mailto:dotnet-li-editor-beta@newrelic.com). Our **Instrumentation** editor allows .NET app users to implement custom instrumentation from the New Relic user interface without requiring a restart of the instrumented application. This editor: diff --git a/src/content/docs/kubernetes-pixie/kubecost/get-started-kubecost.mdx b/src/content/docs/kubernetes-pixie/kubecost/get-started-kubecost.mdx index 5a584e43737..1652f5c0772 100644 --- a/src/content/docs/kubernetes-pixie/kubecost/get-started-kubecost.mdx +++ b/src/content/docs/kubernetes-pixie/kubecost/get-started-kubecost.mdx @@ -10,8 +10,10 @@ metaDescription: "Understand the costs associated with your Kubernetes resources freshnessValidatedDate: 2023-08-12 --- - - This feature is currently in preview. + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). With New Relic and [Kubecost](https://kubecost.github.io/cost-analyzer/), you can understand the costs associated with each of your Kubernetes resources. diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx index 77f42577f9f..0ac95248342 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx @@ -12,8 +12,11 @@ freshnessValidatedDate: never import kubernetesAdapterDiagram from 'images/kubernetes_diagram_adapter-diagram.svg' - - This feature is still in public preview, but we encourage you to try it out! + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). You can use metrics from your New Relic account to autoscale applications and services in your Kubernetes cluster by deploying the [New Relic Metrics Adapter](https://github.com/newrelic/newrelic-k8s-metrics-adapter). This adapter fetches the metric values from New Relic and makes them available for the [Horizontal Pod Autoscalers](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/). diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx index 0405db1cbed..7bdbb19366b 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx @@ -11,6 +11,8 @@ freshnessValidatedDate: 2024-06-28 We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). The Kubernetes agent operator streamlines full-stack observability for Kubernetes environments by automating APM instrumentation alongside Kubernetes agent deployment. By enabling APM auto instrumentation, developers no longer need to manually manage [APM agents](/docs/apm/new-relic-apm/getting-started/introduction-apm/). The Kubernetes agent operator will automatically installs, upgrades, and removes APM agents. @@ -249,7 +251,7 @@ To uninstall and delete the Kubernetes agent operator, run this command: > Yes, you just need to change your [license key](/docs/apis/intro-apis/new-relic-api-keys/#license-key) injected in the secret in the appropriate namespace. - + The [K8s APM experience](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page/) is only available on the account where the data from the applications and the K8s cluster is available. diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-eks-fargate.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-eks-fargate.mdx index 5a0b007439b..5bb2a93d68d 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-eks-fargate.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-eks-fargate.mdx @@ -17,8 +17,11 @@ import kubernetesFargateWorkflow from 'images/kubernetes_diagram_fargate-workflo import kubernetesFargateUi from 'images/kubernetes_screenshot-crop_fargate-ui.webp' - -This feature is currently in preview. + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-windows.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-windows.mdx index 5795ee12220..b0eb6d6cb66 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-windows.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-windows.mdx @@ -9,8 +9,10 @@ metaDescription: "New Relic's Kubernetes integration: The installation of Kubern freshnessValidatedDate: 2024-04-29 --- - -This feature is currently in preview. + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). Use this option when you've a Windows-based Kubernetes system. Note that Windows integration has several [limitations](#k8-windows-limitations). diff --git a/src/content/docs/nrql/using-nrql/query-infrastructure-dimensional-metrics-nrql.mdx b/src/content/docs/nrql/using-nrql/query-infrastructure-dimensional-metrics-nrql.mdx index 513bc55d537..9acb5e9d47e 100644 --- a/src/content/docs/nrql/using-nrql/query-infrastructure-dimensional-metrics-nrql.mdx +++ b/src/content/docs/nrql/using-nrql/query-infrastructure-dimensional-metrics-nrql.mdx @@ -12,8 +12,11 @@ freshnessValidatedDate: 2024-03-19 import queriesnrqlDimensionalMetricsNamingConvention from 'images/queries-nrql_diagram_dimensional-metrics-naming-convention.webp' - - This feature is currently in preview. + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). [Dimensional metrics](/docs/using-new-relic/data/understand-data/new-relic-data-types#dimensional-metrics) are an industry standard for storing and querying metric data. New Relic stores all infrastructure metrics [as event data](/docs/data-apis/understand-data/new-relic-data-types/#metric-event-attributes), but you can also query them as dimensional metrics. diff --git a/src/content/docs/style-guide/structure/callouts.mdx b/src/content/docs/style-guide/structure/callouts.mdx index 82b9795b3c2..81dbb15ecaf 100644 --- a/src/content/docs/style-guide/structure/callouts.mdx +++ b/src/content/docs/style-guide/structure/callouts.mdx @@ -83,11 +83,6 @@ Here are examples of our callout variants: ``` - For preview docs, add a custom callout. Also, we recommend that you don't include a variant so you display the default color: - - - This feature is still in development, but we encourage you to try it out! - @@ -117,3 +112,32 @@ Here's an example of the stacked callouts we'd love to avoid. Think carefully before adding another callout on the page. + +## Preview doc callouts [#preview-callouts] + +For preview docs, add a custom callout using the default color: + + + We're still working on this feature, but we'd love for you to try it out! + + +For the content inside the callout, you can use whatever text you want for the first line, but for the remainder of the callout, you need to include some boilerplate language. + +* **For public previews on `docs.newrelic.com`**: You must also include this standard message in the callout at the top of each preview page. + + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + +* **For preview features only available on our private beta site**: You must also include this standard message in the callout at the top of each preview page. + + + We're still working on this feature, but we'd love for you to try it out! + + New Relic's proprietary and confidential information. For authorized users only. Unauthorized uses and disclosures are prohibited. + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). + + diff --git a/src/content/docs/style-guide/word-choice/usage-dictionary.mdx b/src/content/docs/style-guide/word-choice/usage-dictionary.mdx index 7e396b195f3..42f8fee1699 100644 --- a/src/content/docs/style-guide/word-choice/usage-dictionary.mdx +++ b/src/content/docs/style-guide/word-choice/usage-dictionary.mdx @@ -694,13 +694,13 @@ E words are words that use `e` as a shorthand for electronic, like ebook, ecomme id="new-preview" title="New or preview usage" > -Use *New* to refer to a feature or capability that has recently been released to the general public (GA). In the UI, use the [badge component](https://one-core.newrelic.com/components/badge/) to label new features or capabilities. +Use `New` to refer to a feature or capability that has recently been released to the general public (GA). In the UI, use the [badge component](https://one-core.newrelic.com/components/badge/) to label new features or capabilities. -Use *Preview* to refer to features and capabilities that are pre-GA but are available to select users and sometimes more broadly. These features or capabilities are usually not complete. Previews enable us to gather initial user feedback as we work towards general availability. +Use `Preview` to refer to features and capabilities that are pre-GA but are available to select users and sometimes more broadly. These features or capabilities are usually not complete. Previews enable us to gather initial user feedback as we work towards general availability. For either term, in the UI, use the [badge component](https://one-core.newrelic.com/components/badge/) in spots like these: - the left-hand navigation -- the tile on the All Capabilities page +- the tile on the **All Capabilities** page - the page title @@ -926,13 +926,13 @@ For more information about observability, see [Product and cabilities: observabi id="Preview" title="preview" > - Docs use the [preview callout](/docs/style-guide/quick-reference/callouts/) for features in [preview](#new-preview). In the body text, use lowercase. For example: + Docs use the [preview callout](/docs/style-guide/structure/callouts/#preview-callouts) for features in [preview](#new-preview). In the body text, use lowercase. For example: - - This feature is currently in preview. + + We're still working on this feature, but we'd love for you to try it out! - If the developer team prefers to use a term other than preview, clarify what is driving that use of the term (Legal requirement?), and add any relevant info here in the usage dictionary. + In addition to your preview invitation, you should add legal boilerplate language as outlined in our [style guide](/docs/style-guide/structure/callouts/#preview-callouts). - This feature is currently a public preview. + + We're still working on this feature, but we'd love for you to try it out! + + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). Our IBM MQ [integration](/docs/integrations/host-integrations/getting-started/introduction-host-integrations)