Yes, we are using the extra_endpoints on the agent side. In our use case, we are in an enterprise environment where there are two disparate teams using Datadog to monitor their area of responsibility on that particular server. So, we have the primary team's keys configured in the main part of the agent config, and the secondary or other teams are configured with their keys under extra_endpoints. For example, we have a database server with two operational teams. The first is the OS operational team, and the second are the DBA teams. Each team needs to have their own keys in place so they can setup monitors in their own DataDog accounts due to the specific alerting and monitoring workflows they've already established.

…

On Tue, Feb 13, 2018 at 10:02 AM, Olivier Vielpeau ***@***.*** > wrote: This would be a welcome feature indeed. Are you still using the extra_endpoints on the Agent side? This was originally implemented mostly for our internal usage, but I'd be interested in your use case. A contribution would be welcome for this feature, I'll put this in triage to estimate demand. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#452 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB2A7XnjV6cvXhoB_VOlp5Q5cLgg3p7Gks5tUc5CgaJpZM4OXMHt> .

Extend #395 to accommodate extra_endpoints #452

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions