Skip to content

Commit

Permalink
Fixed review comments
Browse files Browse the repository at this point in the history
  • Loading branch information
cbehera-newrelic committed Jan 7, 2025
1 parent 094035a commit 56b37f5
Show file tree
Hide file tree
Showing 4 changed files with 17 additions and 17 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -9,16 +9,16 @@ Before you [instrument Azure functions](/docs/serverless-function-monitoring/aws
## Basic requirements [#requirements]


* A New Relic account with either an [admin role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) or have the **Infrastructure manager** [add-on role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on).
* A New Relic account with either an [admin role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#roles) or an [Infrastructure manager role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#add-on).

* A <InlinePopover type="userKey" />.

* .NET agent version 10.30
* .NET agent version 10.30 or above


<Callout variant="tip" title="NOTE">

End-to-end distributed tracing is supported only for HTTP requests. Additionally, traces for calls to external services (e.g., databases, ServiceBus, etc.) are still available.
End-to-end distributed tracing is supported only for HTTP requests. Additionally, traces for calls to external services (e.g., Databases, Service Bus, etc.) are still available.

Check notice on line 21 in src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx#L21

[Microsoft.Passive] 'is supported' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is supported' looks like passive voice.", "location": {"path": "src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx", "range": {"start": {"line": 21, "column": 32}}}, "severity": "INFO"}

Check failure on line 21 in src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx#L21

[Microsoft.Foreign] Use 'for example' instead of 'e.g.,'.
Raw output
{"message": "[Microsoft.Foreign] Use 'for example' instead of 'e.g.,'.", "location": {"path": "src/content/docs/serverless-function-monitoring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx", "range": {"start": {"line": 21, "column": 122}}}, "severity": "ERROR"}
</Callout>


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,11 @@ freshnessValidatedDate: never
New Relic's instrumentation for Azure functions offers deep visibility into the inner workings of your functions. By adding the New Relic agent to your function, each invocation is monitored by New Relic. This enables you to track the duration of function invocations, monitor errors, see distributed tracing, and record details about the source events and your function's responses.

Check notice on line 11 in src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx#L11

[Microsoft.Passive] 'is monitored' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is monitored' looks like passive voice.", "location": {"path": "src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx", "range": {"start": {"line": 11, "column": 179}}}, "severity": "INFO"}

Check notice on line 11 in src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx#L11

[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'monitor'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'check' or 'watch' instead of 'monitor'.", "location": {"path": "src/content/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring.mdx", "range": {"start": {"line": 11, "column": 270}}}, "severity": "INFO"}


<Callout variant="important">

For Azure functions, the agent reports data such as distributed traces and logs, which are available under 'Services - APM' as an APM entity. However, a separate entity (provided by infrastructure monitoring) for Azure Functions still exists.

</Callout>

<img
title="azure_function_monitoring.gif"
Expand All @@ -21,8 +26,7 @@ New Relic's instrumentation for Azure functions offers deep visibility into the

<Callout variant="important">

For Azure functions, the agent reports data such as distributed traces and logs, which are available under 'Services - APM' as an APM entity. However, a separate entity for Azure Functions still exists with only the metric data.

For Azure functions, the agent reports data such as distributed traces and logs, which are available under 'Services - APM' as an APM entity. However, a separate entity (provided by infrastructure monitoring) for Azure Functions still exists.

</Callout>

Expand Down
10 changes: 6 additions & 4 deletions src/content/docs/serverless-function-monitoring/overview.mdx
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
---
title: Serverless function monitoring
title: Serverless monitoring
redirects:
- /docs/full-stack-observability/monitor-everything/observability-solutions/serverless-monitoring
- /docs/serverless-function-monitoring
freshnessValidatedDate: never
---

Serverless functions are a way to run code in the cloud without worrying about managing servers. Instead of setting up and maintaining servers, the cloud provider takes care of everything for you. This means that developers can focus on writing code that responds to specific events, like a user clicking a button, without dealing with the technical details of server management.
By leveraging New Relic's serverless function monitoring capabilities, organizations can enhance their operational efficiency, improve application performance, and ensure a seamless user experience.
By leveraging New Relic's serverless monitoring capabilities, organizations can enhance their operational efficiency, improve application performance, and ensure a seamless user experience.

Following are some of the key benefits of using New Relic for serverless function monitoring:
Following are some of the key benefits of using New Relic for serverless monitoring:

Check notice on line 12 in src/content/docs/serverless-function-monitoring/overview.mdx

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/docs/serverless-function-monitoring/overview.mdx#L12

[Microsoft.Wordiness] Consider using 'some' instead of 'some of the'.
Raw output
{"message": "[Microsoft.Wordiness] Consider using 'some' instead of 'some of the'.", "location": {"path": "src/content/docs/serverless-function-monitoring/overview.mdx", "range": {"start": {"line": 12, "column": 15}}}, "severity": "INFO"}

* **Unified monitoring:** Visualize all your serverless functions in a single dashboard, regardless of the cloud provider, simplifying the management and monitoring of functions across different environments

Expand All @@ -22,6 +22,8 @@ Following are some of the key benefits of using New Relic for serverless functio
Select the cloud provider you are using to learn more about how New Relic can help you monitor your serverless functions:




<LandingPageTileGrid>
<LandingPageTile
title="AWS Lambda"
Expand All @@ -31,7 +33,7 @@ Select the cloud provider you are using to learn more about how New Relic can he

<LandingPageTile
title="Azure Functions"
href="/docs/integrations/microsoft-azure-integrations/azure-integrations-list/azure-functions-monitoring-integration"
href="/docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring"
icon="logo-azure"
/>

Expand Down
10 changes: 2 additions & 8 deletions src/nav/serverless-function-monitoring.yml
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,9 @@ pages:
- title: Forward your Lambda function logs with OpenTelemetry
path: /docs/serverless-function-monitoring/aws-lambda-monitoring/opentelemetry/otel-adot-log-ingestion-serverless

- title: Azure functions monitoring
- title: Azure Functions monitoring
pages:
- title: Introduction to Azure Function monitoring
- title: Introduction to Azure Functions monitoring
path: /docs/serverless-function-monitoring/azure-function-monitoring/introduction-azure-monitoring
- title: Installation and configuration
pages:
Expand All @@ -58,12 +58,6 @@ pages:
path: /docs/serverless-function-monitoring/azure-function-monitoring/install-serverless-azure-monitoring
- title: Environment variables
path: /docs/serverless-function-monitoring/azure-function-monitoring/env-variables-azure
# - title: Instrumentation for Azure functions hosted on Linux
# path: /docs/serverless-function-monitoring/azure-function-monitoring/instrument-linux-function
# - title: Instrumentation for Azure functions hosted on Windows
# path: /docs/serverless-function-monitoring/azure-function-monitoring/instrument-windows-function
# - title: Instrumentation for containerized Azure functions
# path: /docs/serverless-function-monitoring/azure-function-monitoring/instrument-containerized-function

- title: Google Cloud Functions monitoring
path: /docs/infrastructure/google-cloud-platform-integrations/gcp-integrations-list/google-cloud-functions-monitoring-integration

0 comments on commit 56b37f5

Please sign in to comment.