Skip to content
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

Monitor from different nodes #1315

Open
wants to merge 10 commits into
base: PMM3_Beta
Choose a base branch
from

Conversation

catalinaadam
Copy link
Contributor

No description provided.

@catalinaadam catalinaadam requested a review from a team as a code owner October 2, 2024 11:24
@@ -36,7 +36,7 @@ The choices are:

## Add services

On each PMM Client, you configure then add to PMM Server's inventory the node or service you want to monitor.
On each PMM Client, you configure then add to PMM Server's inventory the nodes or service you want to monitor.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we write "nodes", shouldn't we write "services"?


When adding a new service through the PMM UI, you can now select the node that will run the exporter. By default, PMM Server is chosen, but you have the option to select any node with a PMM Client installed. If a node has multiple Clients installed, you can choose which one to use.

Currently, this feature is availabl only when adding new services. Support for editing existing services will be included in a future update.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Currently, this feature is availabl only when adding new services. Support for editing existing services will be included in a future update.
Currently, this feature is available only when adding new services. Support for editing existing services will be included in a future update.

@@ -18,6 +18,18 @@ By default, an encryption key is automatically generated and stored at `/srv/pmm

When upgrading to PMM 3, any existing unencrypted PMM 2 data will be encrypted automatically.

## Distribute monitoring across multiple nodes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should add it to somewhere else, not only in release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants