[vercel_otel] new vercel content pack by jakubgalecki0 · Pull Request #20387 · elastic/integrations

jakubgalecki0 · 2026-07-28T20:02:05Z

Proposed commit message

Checklist

I have reviewed tips for building integrations and this pull request is aligned with them.
I have verified that all data streams collect metrics or logs.
I have added an entry to my package's changelog.yml file.
I have verified that Kibana version constraints are current according to guidelines.
I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

[ ]

How to test this PR locally

Related issues

Screenshots

github-actions · 2026-07-28T20:03:33Z

Elastic Docs Style Checker (Vale)

Summary: 1 warning found

⚠️ Warnings (1): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
packages/vercel_otel/docs/README.md	73	Elastic.DontUse	Don't use 'and/or'.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

ishleenk17 · 2026-07-31T12:58:26Z

In the logs dashboard, I think it will be good to have a filter for log.source @jakubgalecki0
As different log sources help with different type of information

jakubgalecki0 · 2026-07-31T13:30:50Z

@ishleenk17

In the logs dashboard, I think it will be good to have a filter for log.source @jakubgalecki0 As different log sources help with different type of information

Added filter

ishleenk17 · 2026-07-31T16:59:44Z

I see us mentoning the endpoint as managed OTLP endpoint.
Its not. Its just a managed endpoint.
Aslo lets give example of how the endpoint would look like.
Please remove al references of managed OTLP endpoint in the documetnation.

ishleenk17 · 2026-07-31T17:23:25Z

I don't think all logs are runtime logs. Only ones with sources as lambda and edge fall under this.
So we should name is something else in the documentation ?

ishleenk17 · 2026-08-01T12:02:23Z

+Setup has three parts, done in order:
+
+1. Enable the Vercel features you want to collect.
+2. Gather two values from Elastic: a **drain URL** and an **API key**.


Suggested change

2. Gather two values from Elastic: a **drain URL** and an **API key**.

2. Gather two values from Elastic: a **managed endpoint URL** and an **API key**.

ishleenk17 · 2026-08-01T12:04:57Z

+- **Web Analytics**: install and enable the [@vercel/analytics](https://vercel.com/docs/analytics) SDK in your application so page views and custom events are emitted.
+- **Speed Insights**: install and enable the [@vercel/speed-insights](https://vercel.com/docs/speed-insights) SDK in your application so Web Vitals are collected in the browser.
+
+### Step 2: Gather the drain URL and API key from Elastic


Suggested change

### Step 2: Gather the drain URL and API key from Elastic

### Step 2: Gather the managed endpoint URL and API key from Elastic

ishleenk17 · 2026-08-01T12:05:36Z

+
+You need an Elastic Cloud Serverless project or an Elastic Cloud Hosted deployment.
+
+#### Drain URL


Suggested change

#### Drain URL

#### Managed Endpoint URL for Vercel

ishleenk17 · 2026-08-01T12:12:19Z

+
+1. Log in to the [Elastic Cloud Console](https://cloud.elastic.co/).
+2. Open your project or deployment and select **Manage**.
+3. In **Application endpoints, cluster and component IDs**, select **OpenTelemetry** (Serverless projects) or **Managed OTLP** (Hosted deployments), then copy the public endpoint value.


Suggested change

3. In **Application endpoints, cluster and component IDs**, select **OpenTelemetry** (Serverless projects) or **Managed OTLP** (Hosted deployments), then copy the public endpoint value.

3. In **Application endpoints, cluster and component IDs**, select the Vercel endpoint, then copy the public endpoint value.

The vercel endpoint will be added to the application endpoints

ishleenk17 · 2026-08-01T12:12:56Z

+2. Open your project or deployment and select **Manage**.
+3. In **Application endpoints, cluster and component IDs**, select **OpenTelemetry** (Serverless projects) or **Managed OTLP** (Hosted deployments), then copy the public endpoint value.
+
+The drain URL is that public endpoint plus `/vercel`, which is the path that accepts Vercel drain payloads:


Suggested change

The drain URL is that public endpoint plus `/vercel`, which is the path that accepts Vercel drain payloads:

The managed endpoint URL for Vercel is that public endpoint plus `/vercel`, which is the path that accepts Vercel drain payloads:

ishleenk17 · 2026-08-01T12:13:18Z

+https://<managed-endpoint>/vercel
+```
+
+For example, if your public endpoint is `https://abc123.ingest.us-east-1.aws.elastic.cloud`, then the drain URL is:


Suggested change

For example, if your public endpoint is `https://abc123.ingest.us-east-1.aws.elastic.cloud`, then the drain URL is:

For example, if your public endpoint is `https://abc123.ingest.us-east-1.aws.elastic.cloud`, then the managed endpoint URL for vercel is:

ishleenk17 · 2026-08-01T12:14:35Z

+
+1. Open your team **Drains** settings and create a drain for that data type.
+2. Choose **Custom Endpoint** as the destination.
+3. Set the **Endpoint URL** to the drain URL, for example `https://abc123.ingest.us-east-1.aws.elastic.cloud/vercel`.


Suggested change

3. Set the **Endpoint URL** to the drain URL, for example `https://abc123.ingest.us-east-1.aws.elastic.cloud/vercel`.

3. Set the **Endpoint URL** to the managed endpoint URL for Vercel, for example `https://abc123.ingest.us-east-1.aws.elastic.cloud/vercel`.

ishleenk17 · 2026-08-01T12:15:06Z

+
+For Logs drains, you can also narrow which sources, environments, and sampling rates are forwarded under **Additional configuration for logs**. Refer to [Log Drains reference](https://vercel.com/docs/drains/reference/logs).
+
+> **Note**: The drain URL is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.


Suggested change

> **Note**: The drain URL is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.

> **Note**: The managed endpoint URL for Vercel is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.

ishleenk17 · 2026-08-01T12:15:59Z

+## Reference
+
+Vercel drain payloads are decoded by the Elastic Cloud managed endpoint and written to the data streams below. For drain configuration and payload types on the Vercel side, see [Using drains](https://vercel.com/docs/drains/using-drains). For managed endpoint behavior, see [Managed inputs](https://www.elastic.co/docs/reference/opentelemetry/managed-inputs).
+


@jakubgalecki0 : Can we point to a place where the fields (for meterics and logs) are documented ?

ishleenk17 · 2026-08-01T18:06:39Z

why

are the

project values different across the 3 dashbaord. Don't they refer to same field ?

ishleenk17 · 2026-08-01T18:07:37Z

Shouldn't these be integer values ?

ishleenk17 · 2026-08-02T06:16:34Z

Thanks for making the changes @jakubgalecki0
Please add screenshots of the dashboard in the PR description and remove the alerts screesnhot.

Also update the web analytics screenshot in the PR. it still shows decimal values

ishleenk17

Please update the screenshots in the img folder to showcase the latest changes.
Else looks good now!

mergify · 2026-08-02T06:31:54Z

Queued — the merge queue status continues in this comment ↓.

mergify · 2026-08-02T08:12:24Z

elastic-vault-github-plugin-prod · 2026-08-02T08:16:43Z

✅ All changelog entries have the correct PR link.

infra-vault-gh-plugin-prod · 2026-08-02T08:30:14Z

💚 Build Succeeded

Buildkite Build
Commit: 2ae2931

History

💚 Build #46989 succeeded a989a5e
💚 Build #46988 succeeded 6921dfe
💚 Build #46987 succeeded 7b289e8
💚 Build #46985 succeeded 7737d19
💚 Build #46971 succeeded 9a2218b
💚 Build #46966 succeeded 6ff58e6

elastic-vault-github-plugin-prod · 2026-08-02T08:44:54Z

Package vercel_otel - 0.1.0 containing this change is available at https://epr.elastic.co/package/vercel_otel/0.1.0/

[vercel_otel] new vercel content pack

a555652

andrewkroh added the New Integration Issue or pull request for creating a new integration package. label Jul 29, 2026

jakubgalecki0 added 8 commits July 29, 2026 17:24

draft audit logs, logs and web-analytics dashboards

1a5b311

update logs & audit logs dashboards

d0c1b13

update decimlas

c4ca4c4

update links table and fix grok pattern in web analytics

eb50c64

add readme file & screenshots

f5f040d

update pr link

d841daf

Merge branch 'main' into vercel_otel_cp

d03369e

make title smaller

7163ccf

add filter to logs dashboard

ec68d98

jakubgalecki0 added 2 commits July 31, 2026 16:31

add slo template

4e5a491

remove slo

6ff58e6

jakubgalecki0 marked this pull request as ready for review July 31, 2026 16:40

jakubgalecki0 requested a review from a team as a code owner July 31, 2026 16:40

jakubgalecki0 added 2 commits July 31, 2026 18:44

speed insights dashboard

42f5f1d

update description

9a2218b

update readme

7737d19

ishleenk17 reviewed Aug 1, 2026

View reviewed changes

jakubgalecki0 added 2 commits August 1, 2026 18:41

address review comments

7b289e8

remove speed insights metrics dashboard

6921dfe

update project filter and decimals

a989a5e

ishleenk17 approved these changes Aug 2, 2026

View reviewed changes

jakubgalecki0 added 2 commits August 2, 2026 10:07

update dashboard screenshots

4f10749

Merge branch 'main' into vercel_otel_cp

2ae2931

jakubgalecki0 merged commit 356555d into elastic:main Aug 2, 2026
11 checks passed

Navigation Menu

Uh oh!

[vercel_otel] new vercel content pack - #20387

[vercel_otel] new vercel content pack#20387
jakubgalecki0 merged 20 commits into
elastic:mainfrom
jakubgalecki0:vercel_otel_cp

jakubgalecki0 commented Jul 28, 2026 •

edited

Loading

github-actions Bot commented Jul 28, 2026 •

edited

Loading

ishleenk17 commented Jul 31, 2026 •

edited

Loading

jakubgalecki0 commented Jul 31, 2026

ishleenk17 commented Jul 31, 2026

ishleenk17 commented Jul 31, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 Aug 1, 2026

ishleenk17 commented Aug 1, 2026

ishleenk17 commented Aug 1, 2026

ishleenk17 commented Aug 2, 2026 •

edited

Loading

ishleenk17 left a comment

mergify Bot commented Aug 2, 2026 •

edited

Loading

mergify Bot commented Aug 2, 2026 •

edited

Loading

elastic-vault-github-plugin-prod Bot commented Aug 2, 2026

infra-vault-gh-plugin-prod Bot commented Aug 2, 2026

Uh oh!

elastic-vault-github-plugin-prod Bot commented Aug 2, 2026

Labels

3 participants

	2. Gather two values from Elastic: a drain URL and an API key.
	2. Gather two values from Elastic: a managed endpoint URL and an API key.

	### Step 2: Gather the drain URL and API key from Elastic
	### Step 2: Gather the managed endpoint URL and API key from Elastic


		You need an Elastic Cloud Serverless project or an Elastic Cloud Hosted deployment.

		#### Drain URL

	3. In Application endpoints, cluster and component IDs, select OpenTelemetry (Serverless projects) or Managed OTLP (Hosted deployments), then copy the public endpoint value.
	3. In Application endpoints, cluster and component IDs, select the Vercel endpoint, then copy the public endpoint value.

	The drain URL is that public endpoint plus `/vercel`, which is the path that accepts Vercel drain payloads:
	The managed endpoint URL for Vercel is that public endpoint plus `/vercel`, which is the path that accepts Vercel drain payloads:

	For example, if your public endpoint is `https://abc123.ingest.us-east-1.aws.elastic.cloud`, then the drain URL is:
	For example, if your public endpoint is `https://abc123.ingest.us-east-1.aws.elastic.cloud`, then the managed endpoint URL for vercel is:

	3. Set the Endpoint URL to the drain URL, for example `https://abc123.ingest.us-east-1.aws.elastic.cloud/vercel`.
	3. Set the Endpoint URL to the managed endpoint URL for Vercel, for example `https://abc123.ingest.us-east-1.aws.elastic.cloud/vercel`.


		For Logs drains, you can also narrow which sources, environments, and sampling rates are forwarded under Additional configuration for logs. Refer to [Log Drains reference](https://vercel.com/docs/drains/reference/logs).

		> Note: The drain URL is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.

	> Note: The drain URL is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.
	> Note: The managed endpoint URL for Vercel is always your Elastic Cloud public endpoint plus `/vercel`. Do not point the drain at a self-hosted collector for these assets; the supported path is the Elastic Cloud managed endpoint.

		## Reference

		Vercel drain payloads are decoded by the Elastic Cloud managed endpoint and written to the data streams below. For drain configuration and payload types on the Vercel side, see [Using drains](https://vercel.com/docs/drains/using-drains). For managed endpoint behavior, see [Managed inputs](https://www.elastic.co/docs/reference/opentelemetry/managed-inputs).

Uh oh!

Conversation

jakubgalecki0 commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed commit message

Checklist

Author's Checklist

How to test this PR locally

Related issues

Screenshots

github-actions Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Elastic Docs Style Checker (Vale)

ishleenk17 commented Jul 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

jakubgalecki0 commented Jul 31, 2026

ishleenk17 commented Jul 31, 2026

ishleenk17 commented Jul 31, 2026

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ishleenk17 commented Aug 1, 2026

ishleenk17 commented Aug 1, 2026

ishleenk17 commented Aug 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ishleenk17 left a comment

Choose a reason for hiding this comment

mergify Bot commented Aug 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

mergify Bot commented Aug 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge Queue Status

elastic-vault-github-plugin-prod Bot commented Aug 2, 2026

infra-vault-gh-plugin-prod Bot commented Aug 2, 2026

💚 Build Succeeded

History

Uh oh!

elastic-vault-github-plugin-prod Bot commented Aug 2, 2026

Labels

3 participants

jakubgalecki0 commented Jul 28, 2026 •

edited

Loading

github-actions Bot commented Jul 28, 2026 •

edited

Loading

ishleenk17 commented Jul 31, 2026 •

edited

Loading

ishleenk17 commented Aug 2, 2026 •

edited

Loading

mergify Bot commented Aug 2, 2026 •

edited

Loading

mergify Bot commented Aug 2, 2026 •

edited

Loading