Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update intro-slm.mdx to spell out SLA #6846

Merged
merged 1 commit into from
Mar 30, 2022
Merged

Update intro-slm.mdx to spell out SLA #6846

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/service-level-management/intro-slm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ See the [Service level management use case implementation guide](/docs/new-relic

## Service levels and APM SLA reports [#slm-sla]

New Relic has provided automatic [SLA Reports for APM Services](/docs/apm/reports/service-level-agreements/apm-sla-reports/) for a long time. The Apdex-based reports, which you can get on your email inbox on Mondays, are automatically generated for services that produce web transactions, and are useful to see trends over time.
New Relic has provided automatic [service level agreement (SLA) reports for APM services](/docs/apm/reports/service-level-agreements/apm-sla-reports/) for a long time. The Apdex-based reports, which you can get on your email inbox on Mondays, are automatically generated for services that produce web transactions, and are useful to see trends over time.

On top of the SLAs, our new service levels capability is better aligned with modern service level best practices, such as those promoted by the [Google SRE Handbook](https://sre.google/books/), and provides new, improved functionality:

Expand Down