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

Daily release/jul 14 2023 6 38 #13868

Merged
merged 4 commits into from
Jul 17, 2023
Merged

Daily release/jul 14 2023 6 38 #13868

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5e8b9f7
Update intro-synthetic-monitoring.mdx
ammartens Jul 14, 2023
aeef45a
Merge pull request #13861 from ammartens/patch-2
zuluecho9 Jul 14, 2023
ffbf88a
Update missing-route-changes-spa-agent.mdx
hariseldon27 Jul 14, 2023
2969b84
Merge pull request #13867 from hariseldon27/patch-2
homelessbirds Jul 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .../single-page-app-monitoring/troubleshooting/missing-route-changes-spa-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ redirects:

You are using the Pro + SPA agent, but you are not seeing all of the `route change` browser interactions you expect.

We are aware that this can be frustrating. Our goal throughout 2021 is to reevaluate the SPA feature functionality, making it simpler and more reliable, starting with the methods we use to detect and capture route changes. Additionally, we plan to add new frameworks and use cases to our testing suite based on your feedback and examples. Likely this work will include new APIs as well as framework-specific plug-ins. Check our [release notes](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes) for the latest updates.
We are aware that this can be frustrating. Our ongoing goal is to improve SPA feature functionality, making it simpler and more reliable, starting with the methods we use to detect and capture route changes.

## Solution

Expand Down
2 changes: 1 addition & 1 deletion ...s/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,7 +329,7 @@ Synthetic monitoring includes the following features:
After you've set up some synthetic monitors, we recommend these next steps:

* Check how your synthetics data turns your aggregated results into [metrics](/docs/synthetics/new-relic-synthetics/dashboards/synthetics-overview-dashboard), allowing you to see patterns and identify causes of poor performance.
* See how[each and every monitor result](/docs/synthetics/new-relic-synthetics/using-monitors/viewing-monitor-results#understanding)is broken down.
* See how [each and every monitor result](/docs/synthetics/new-relic-synthetics/using-monitors/viewing-monitor-results#understanding) is broken down.
* Want to supplement your synthetics data with real-user data? Check out our [Improve your website's performance](/docs/journey-performance/improve-website-performance) tutorial.
* Create [alerts that notify you](/docs/synthetics/new-relic-synthetics/using-monitors/alerting-synthetics) if your website or API endpoint is inaccessible. You can even expand your geographical coverage or monitor internal websites by creating [private locations](/docs/synthetics/new-relic-synthetics/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations).
* You can also [query your monitor results](/docs/using-new-relic/data/understand-data/query-new-relic-data) for a closer look. New Relic retains monitor results for thirteen months, ensuring you can compare usage year over year.
Loading