Add server name to email and push notifications when users have more than one server

[begunfx]

If a user only has one server then just showing the container updates is sufficient, but if they have multiple servers with the same services running on each one, it can be hard to parse the notifications. It would be nice if in that instance the notifications (push or email) included the server name and easier to identify which server had the update for each service. Thanks!

[s-b-e-n-s-o-n]

Thanks for the suggestion! This is coming in v1.5-rc7.

The default notification templates will now automatically include an [agentName] prefix when a container belongs to a remote agent. For example:

• Single server (no agent): New minor found for container nginx — no change
• Multi-server: [prod-server] New minor found for container nginx

This applies to all notification types (update available, update applied/failed, security alerts, digest, batch) across all trigger providers (email, push, Slack, etc.).

If you use custom templates, the new container.notificationAgentPrefix variable is available for use however you like — or you can access container.agent directly for full control.

No configuration needed — it just works when you have agents configured.

[begunfx]

Reading this again. The only gap would be if updates are on the primary drydock server vs agents. If I understand you correctly we will get the server name for an update that is from an agent but not for the primary server? I would recommend including the server name for the primary server IF there are registered agents. If not, then you can bypass the server name. That would handle the use case for server name to appear across ALL hosts. Does that make sense? Thanks!

[s-b-e-n-s-o-n]

Great catch — you're exactly right. The initial implementation only prefixed agent containers, leaving the controller's containers unlabeled.

This is now fixed. The behavior is:

• No agents registered (single server): no prefix, no change
• Agents registered, controller container: [controller-hostname] New minor found for container nginx
• Agents registered, agent container: [prod-server] New minor found for container nginx

The controller name defaults to the machine hostname and can be overridden with DD_SERVER_NAME.

For custom templates, container.notificationServerName always resolves to the server identity (agent name or controller name) regardless of setup.

[begunfx]

Thanks again for adding the hostname. Super helpful. One call out. I'm seeing the hostname post 2x in both gmail and push notifications in rc.7. See below:

- [mediavault] Container lidarr (mediavault) running tag latest has a newer
image available

- [mediavault] Container tracearr-db (mediavault) running with tag
pg18.1-ts2.25.0 can be updated to tag pg18.3-ts2.26.2-oss

We should only see it at the beginning.

[s-b-e-n-s-o-n]

Good catch on the duplicate — fixed in the upcoming RC. The notification prefix and suffix were both independently injecting the server name, resulting in [mediavault] Container lidarr (mediavault). Now the suffix suppresses the server name when the prefix already includes it, so you'll just see:

[mediavault] Container lidarr running tag latest has a newer image available

The next RC will be out shortly — please verify the deduplication across both email and push notifications.