feat(elasticsearch-otel): Add elasticsearch otel integration document… #22578
Conversation
|
Hi @vagrawal-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. Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local. If you really require a preview url, reach out to one of the writers and they will generate one for you. |
|
netlify build fork |
|
✅ Your PR has been mirrored to our repository as PR #22590. |
|
netlify build fork |
|
✅ Your updates have been mirrored to our repository in PR #22590. |
…erience - Rewrite introduction with clearer value proposition and use case - Add structured "What you'll get" and "Before you begin" sections - Simplify technical language for broader accessibility - Improve content flow following New Relic style guidelines - Add clear prerequisites and setup time expectations 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
…e redundancy Overview document improvements: - Remove duplicate metrics between summary and detailed tables - Move prerequisites to installation doc for better UX flow - Eliminate redundant sections for cleaner reading experience - Focus overview on value proposition and benefits Installation document improvements: - Enhance "Before you begin" section with time estimates - Add Step 5 for alerts setup (moved from overview) - Update step navigation to include all 5 steps - Improve prerequisites formatting and clarity This creates better separation of concerns: - Overview: What you get and why to use it - Installation: What you need and how to set it up 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
- Fix broken link in overview document's Next Steps section - Update path from /docs/more-integrations/... to /docs/opentelemetry/get-started/... - Ensure users can properly navigate to related OpenTelemetry integrations 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
- Update title to action-oriented "Install Elasticsearch OpenTelemetry integration" - Improve introduction with clearer language about what the guide does - Add descriptive step navigation with explanations of each step - Fix broken localhost URL in prerequisites section - Add important callout in Step 2 highlighting required customizations - Enhance Step 3 with clearer language about environment variables - Significantly improve Step 4 with success indicators and troubleshooting tips - Add helpful "Next steps with your data" guidance - Fix capitalization inconsistencies (OpenTelemetry vs Opentelemetry) The installation document now provides better user guidance and clearer expectations at each step, making it much more GA-ready. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
…ation discovery Traditional Elasticsearch integration improvements: - Add prominent callout promoting new OpenTelemetry alternative - Guide users to modern OTEL-based monitoring option - Highlight benefits: vendor neutrality, enhanced performance, future-proof architecture OpenTelemetry integration improvements: - Add bidirectional cross-reference to traditional integration - Provide clear choice guidance without being pushy - Enhanced tags for better discoverability and SEO - Added comprehensive tagging: OpenTelemetry, OTEL, On-host integrations This fulfills the JIRA requirement for cross-linking existing OHI documentation to ensure customers can easily find the new OpenTelemetry path. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
3 participants
…ation
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
links to related docs, screenshots, etc.