Agent release 3.0 #567
Draft
Agent release 3.0 #567
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* docs:Adding agent v3 docs * docs: fix missing file reference * docs: Add missing install page * docs: Add v3 migrate docs * docs: Add missing feedback from PR
* docs: review Agent v3 install doc * docs: fix link * docs: rewrite sentence * docs: move manual connect section * docs: collapse install sections * docs: replace amazon with aws icon * docs: replace <i> with shortcode
* fix: root requirements for agent install * fix: bold not
* fix: root requirements for agent install * fix: bold not
* docs: about formatting * fix: product name * fix: fix product name
* docs: update agent v3 tech specs * docs: fix moved v2 path * Update content/agent/technical-specifications.md Co-authored-by: yar <[email protected]> * Update content/agent/technical-specifications.md Co-authored-by: yar <[email protected]> * Update content/agent/technical-specifications.md Co-authored-by: yar <[email protected]> --------- Co-authored-by: yar <[email protected]>
* Update metrics docs, add run-container guide * Apply suggestion to update metadata for how-to guide. Co-authored-by: Jon Torre <[email protected]> * Apply suggestion to update markdown format, and code block Co-authored-by: Jon Torre <[email protected]> * Apply suggestion to update locating config file Co-authored-by: Jon Torre <[email protected]> * Apply suggestion to title Co-authored-by: Jon Torre <[email protected]> * Apply suggestion to title Co-authored-by: Alan Dooley <[email protected]> * Apply suggestion to sentence. Co-authored-by: Jon Torre <[email protected]> * Apply suggestion to use correct note element Co-authored-by: Alan Dooley <[email protected]> * Apply suggestion Co-authored-by: Jon Torre <[email protected]> * Apply suggestion Co-authored-by: Jon Torre <[email protected]> * Update content/agent/how-to/run-agent-container.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/how-to/run-agent-container.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/how-to/run-agent-container.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/how-to/run-agent-container.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: Jon Torre <[email protected]> * docs: Change Container to container, based on PR feedback * Update content/agent/otel/configure-otel-metrics.md Co-authored-by: yar <[email protected]> * Apply suggestions from code review Co-authored-by: Mike Jang <[email protected]> * docs: improve layout --------- Co-authored-by: Jon Torre <[email protected]> Co-authored-by: Alan Dooley <[email protected]> Co-authored-by: yar <[email protected]> Co-authored-by: Mike Jang <[email protected]> Co-authored-by: Jon Cahill-Torre <[email protected]>
* docs: move agent content to includes and n1 * fix: move agent section * fix: relref to ref
Fix URL in Update NGINX Agent
* update v3 agent about * update hugo * updage go.sum * convert about agent to includes * fix mermaid graphs
* move agent v3 docs to NGINX One * fix: update community pages * remove github discussions from agent v3 docs * one line content types * update message * update messaging * remove agent connect instances doc * modify N1 doc to cover v2 and v3
Add a table that details agents options
* Update agent install docs * PR feedback * PR feedback
update glossary
* fix n1 broken link * N1 and Agent updates
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Co-authored-by: yar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Publish Agent release v3 documentation
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.mdFootnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩