-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Daily merge/04 01 25 morning #20357
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
Daily merge/04 01 25 morning #20357
Conversation
…cing information with the Sliding window functionality The users on Advanced and Core Compute pricing plans may incur additional CCU charges when utilizing sliding window aggregation. Adding a pricing section to that topic and callouts at other places where we have communicated about this feature.
Hey docs folks -- this is a spot fix, but it needs to be made on the hundreds of spots in the docs that refer to the product as "New Relic One." That's not the name for the product that we use anymore (for at least a year). In addition, there's not a home page, so I removed the reference to home page. Getting to transaction 360 isn't straightforward and it's not part of "All Capabilities" if that's what this was referring to — you need to go to the transaction page for a service and open it from there. Here's the spot in the style guide that describes how to refer to New Relic: https://newrelic.atlassian.net/wiki/spaces/PD/pages/3804889254/Product+and+capabilities+capitalization+trademarks+and+usage Note that there's also a guideline not to say "New Relic's" Thanks.
Added the last reviewed and updated date.
Updated the language to the Streaming Video and Ads
Remove reference to New Relic One
feat: (Alerts: Sliding window aggregation): Adding the associated pricing details
docs:android agent update for hybrid agents
feat(APM): Python Agent v10.8.1 Docs
…_release_notes-2025-03-31_17_40 feat: Add release notes for Kubernetes integration v3.36.0
…3.0.25 updated release notes for node browser runtime
Update acceptable-use-policy.mdx
Hi @adutta-newrelic 👋 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. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
No description provided.