Does datadog_events sink have a Privatelink Service?

[nzxwang]

Hi team,

Similar to how you've helped us set up our connections to Datadog over AWS Privatelink in #21325 and #21867, I was wondering if the datadog_events sink has an appropriate Privatelink Service? It doesn't seem like the Datadog documentation on using AWS Privatelink has an appropriate service. Any insight would be appreciated.

Thank you

[pront]

Hi @nzxwang, what you do mean by "appropriate Privatelink Service"? Vector doesn't do anything with PrivateLink but it sounds like you could configure the sink endpoint per the guide you linked.

[nzxwang]

Sorry for the poor wording. I should have asked: Does the datadog_events sink have a privatelink service that it can use to forward events to Datadog? For example, both logs and metrics have obvious counterparts in this table from the guide I linked:

[pront]

Thank you for the clarification. I don't see events in that table, I would reach out and ask if it supported or if there are plans to support it:

Click Verify. If this does not return Service name found, reach out to [Datadog support](https://docs.datadoghq.com/help/).

There is another issue here. Are you using Vector e.g. for logs with a PrivateLink service? I don't see how this is possible today because the URI is built using the endpoint and the site. We will need a way to specify the whole URI e.g. com.amazonaws.vpce.us-east-1.vpce-svc-025a56b9187ac1f63.

---

Here is the code that builds the URI:

vector/src/sinks/datadog/mod.rs

Lines 148 to 154 in 450de36

	/// Gets the API endpoint with a given suffix path.
	///
	/// If `endpoint` is not specified, we fallback to `site`.
	fn get_api_endpoint(&self, path: &str) -> crate::Result<Uri> {
	let base = datadog::get_api_base_endpoint(self.endpoint.as_deref(), self.site.as_str());
	[&base, path].join("").parse().map_err(Into::into)
	}

vector/src/common/datadog.rs

Lines 83 to 88 in 450de36

	/// Gets the base API endpoint to use for any calls to Datadog.
	///
	/// If `endpoint` is not specified, we fallback to `site`.
	pub(crate) fn get_api_base_endpoint(endpoint: Option<&str>, site: &str) -> String {
	endpoint.map_or_else(|| format!("https://api.{}", site), compute_api_endpoint)
	}

[nzxwang]

Thanks for confirming. I will submit a feature request to Datadog directly.

At the moment we are using vector for logs and metrics with a Privatelink service. We get around the uri-building limitation you mentioned by creating a DNS name for the respective URIs.