Add SSH tunnel documentation for remote Grafana access#4912
Open
Imaanpreet wants to merge 1 commit into
Open
Conversation
- Add new section 'Accessing Grafana remotely using an SSH tunnel' - Include Linux/macOS command-line instructions - Include Windows PuTTY GUI-based setup instructions - Include Windows PowerShell/OpenSSH instructions - Add background tunnel setup and teardown instructions This addresses the common issue where users cannot directly access http://localhost:3000 on the Satellite/Foreman server from their remote workstation. File modified: - guides/common/modules/proc_retrieving-metrics-in-the-web-ui.adoc
github-actions
Bot
added
Needs tech review
|
The PR preview for 33ad6ef is available at theforeman-foreman-documentation-preview-pr-4912.surge.sh The following output files are affected by this PR: |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This addresses the common issue where users cannot directly access
http://localhost:3000 on the Satellite/Foreman server from their
remote workstation.
File modified:
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into: