DOCSP-45009 - Cluster Monitoring #361
Conversation
✅ Deploy Preview for mongodb-docs-csharp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| .. code-block:: csharp | ||
|
|
||
| var clientSettings = MongoClientSettings.FromConnectionString(MongoConnectionString); |
There was a problem hiding this comment.
Tech reviewer: Does the event-subscription process look any different in pre-3.0 driver versions? Or can I backport this all the way to 2.19?
There was a problem hiding this comment.
Users should have been using this event-subscription process even prior 3.0 driver. There is only one case where users could subscribe to a ClusterDescriptionChangedEvent directly through Client.Cluster since the cluster used to expose its DescriptionChanged handler. But we removed that in 3.0 and there are no other ways for users to subscribe to events other than through ClusterBuilder.
There was a problem hiding this comment.
Thanks. I'll backport this page all the way to v2.22 then.
mongoKart
requested review from
a team,
JamesKovacs and
BorisDog
and removed request for
a team and
JamesKovacs
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.30 v2.30
# Navigate to the new working tree
cd .worktrees/backport-v2.30
# Create a new branch
git switch --create backport-361-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.30
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.30Then, create a pull request where the |
(cherry picked from commit ff92199)
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.29 v2.29
# Navigate to the new working tree
cd .worktrees/backport-v2.29
# Create a new branch
git switch --create backport-361-to-v2.29
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.29
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.29Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.28 v2.28
# Navigate to the new working tree
cd .worktrees/backport-v2.28
# Create a new branch
git switch --create backport-361-to-v2.28
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.28
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.28Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.27 v2.27
# Navigate to the new working tree
cd .worktrees/backport-v2.27
# Create a new branch
git switch --create backport-361-to-v2.27
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.27
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.27Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.26 v2.26
# Navigate to the new working tree
cd .worktrees/backport-v2.26
# Create a new branch
git switch --create backport-361-to-v2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.26
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.26Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.25 v2.25
# Navigate to the new working tree
cd .worktrees/backport-v2.25
# Create a new branch
git switch --create backport-361-to-v2.25
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.25
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.25Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.24 v2.24
# Navigate to the new working tree
cd .worktrees/backport-v2.24
# Create a new branch
git switch --create backport-361-to-v2.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.24
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.24Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.23 v2.23
# Navigate to the new working tree
cd .worktrees/backport-v2.23
# Create a new branch
git switch --create backport-361-to-v2.23
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.23
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.23Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.22 v2.22
# Navigate to the new working tree
cd .worktrees/backport-v2.22
# Create a new branch
git switch --create backport-361-to-v2.22
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ff92199dd14d917e26633c9161a565f5ce399247
# Push it to GitHub
git push --set-upstream origin backport-361-to-v2.22
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.22Then, create a pull request where the |
(cherry picked from commit ff92199)
(cherry picked from commit ff92199) Co-authored-by: Mike Woofter <[email protected]>
(cherry picked from commit ff92199) Co-authored-by: Mike Woofter <[email protected]>
(cherry picked from commit ff92199)
(cherry picked from commit ff92199)
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-45009
Staging Links
Self-Review Checklist