Skip to content

Commit

Permalink
Merge pull request #3045 from romansprykee/patch-3
Browse files Browse the repository at this point in the history
Update monitoring.md
  • Loading branch information
gechetspr authored Feb 7, 2025
2 parents fce8711 + 9330a95 commit 847b6e5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/ca/dev/monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,6 @@

Effective monitoring is crucial for maintaining the health and performance of your Spryker applications. This page provides access to resources and integrations that enable comprehensive monitoring through logs and application performance metrics.

## Logs with CloudWatch
CloudWatch offers robust logging capabilities, allowing you to track, store, and analyze logs from your Spryker applications and services. Learn more about [working with Logs](/docs/ca/dev/working-with-logs.md).

## Application Performance Monitoring
Application Performance Monitoring (APM) provides near real-time insights into the performance of your applications, helping you quickly identify and resolve issues. For Spryker customers, APM ensures optimal application health, enhancing the user experience by minimizing downtime and performance bottlenecks.
### Spryker Monitoring Integration (OTel)
Expand All @@ -13,6 +10,9 @@ Integrate Spryker monitoring data into your preferred APM tool using OpenTelemet
### New Relic APM
Leverage New Relic’s powerful APM features to monitor and troubleshoot your Spryker applications with ease. Learn more about how to use [New Relic APM with Spryker solutions](/docs/dg/dev/integrate-and-configure/configure-services.html#new-relic).

## Logs with CloudWatch
CloudWatch offers robust logging capabilities, allowing you to track, store, and analyze logs from your Spryker applications and services. Learn more about [working with Logs](/docs/ca/dev/working-with-logs.md).

## Monitoring issues and informing about alerts
This section outlines the process for monitoring issues and managing alerts within the Spryker ecosystem. It provides guidance on configuring alerting systems, responding to incidents, and ensuring smooth communication during operational disruptions. For detailed instructions and best practices, check out the [full guide here](/docs/ca/dev/monitoring-issues-and-informing-about-alerts.md).

0 comments on commit 847b6e5

Please # to comment.