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.

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

Remove the availability SLI for browser apps #6199

Merged
merged 3 commits into from
Feb 16, 2022
Merged

Remove the availability SLI for browser apps #6199

merged 3 commits into from
Feb 16, 2022

Conversation

helenapm
Copy link
Contributor

We've noticed that the suggested queries for the Browser app availability service level are not working well. The reason is that one Page View event can generate more than one Javascript error event, therefore the number of bad events is not always a subset of valid events. Until we come up with a better option, we're removing this section (I'm commenting the content so we can reuse it quickly if needed).

Please follow conventional commit standards
in your commit messages and pull request title.

Give us some context

  • What problems does this PR solve?
  • Add any context that will help us review your changes such as testing notes,
    links to related docs, screenshots, etc.
  • If your issue relates to an existing GitHub issue, please link to it.

We've noticed that the suggested queries for the Browser app availability service level are not working well. The reason is that one Page View event can generate more than one Javascript error event, therefore the number of bad events is not always a subset of valid events. Until we come up with a better option, we're removing this section (I'm commenting the content so we can reuse it quickly if needed).
@github-actions
Copy link

Hi @helenapm 👋
Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes).

@github-actions github-actions bot added this to Hero to triage in Docs PRs and Issues Feb 16, 2022
@gatsby-cloud
Copy link

gatsby-cloud bot commented Feb 16, 2022

Gatsby Cloud Build Report

docs-website-develop

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 23m

@urbiz-nr urbiz-nr self-assigned this Feb 16, 2022
@urbiz-nr urbiz-nr added content requests related to docs site content from_internal Identifies issues/PRs from Relics (except writers) labels Feb 16, 2022
@urbiz-nr urbiz-nr moved this from Hero to triage to In progress/being reviewed (by Hero or any TW) in Docs PRs and Issues Feb 16, 2022
urbiz-nr
urbiz-nr previously approved these changes Feb 16, 2022
@urbiz-nr urbiz-nr merged commit d78e475 into newrelic:develop Feb 16, 2022
@urbiz-nr urbiz-nr removed this from In progress/being reviewed (by Hero or any TW) in Docs PRs and Issues Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content from_internal Identifies issues/PRs from Relics (except writers)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants