Updated child node behaviour change#21073
Conversation
kanelatechnical
force-pushed
the
rules
branch
from
712cb97 to
97b2e4c
Compare
kanelatechnical
force-pushed
the
rules
branch
from
97b2e4c to
2fae3a4
Compare
| **Child Node Behavior** | ||
|
|
||
| - Child nodes that are only indirectly connected to Cloud (through a Parent Agent) are no longer automatically added to the same Room as the Parent. | ||
| - If your workflow depended on this automatic grouping, we recommend setting up Room assignment rules. | ||
|
|
There was a problem hiding this comment.
Maybe put this at the beginning of Connect Agent to Cloud (with a link to Node Rule-Based Room Assignment)?
There was a problem hiding this comment.
Perhaps just a note linking to [docs/netdata-cloud/node-rule-based-room-assignment.md] ? I don't know, it seems more appropriate to me that it is on this page
There was a problem hiding this comment.
note linking to [docs/netdata-cloud/node-rule-based-room-assignment.md
Yes. Having this note in the node-rule-based-room-assignment.md looks like circular dependency 😄 I think this info belongs to "Connect Agent to Cloud" (maybe not exclusively, we can have it in multiple places 🤷 )
There was a problem hiding this comment.
You know what though? I'm thinking that this is useful info for people actively thinking about Room organization, not about connecting individual Agents to Cloud. I think we could keep it here safely and maybe place a link in the Connect Agent to Cloud doc
There was a problem hiding this comment.
That’s why I said maybe not exclusively, we can have it in multiple places and approved this PR. See this Slack thread. This is a new behavior. They changed it. I expected it to work differently, and it’s closely related to the topic of connecting Agents to Cloud.
2 participants
Updated child node behaviour change