Supabase OpenTelemetry Integration Package

[ishleenk17]

Supabase OpenTelemetry Integration (Composable package)

This package depends upon the prometheus_input_otel and the supabase_otel content package.

Related Issue: https://github.com/elastic/obs-integration-team/issues/1153

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 3 warnings, 1 suggestion found

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

File	Line	Rule	Message
packages/supabase/_dev/build/docs/README.md	77	Elastic.Latinisms	Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'.
packages/supabase/manifest.yml	105	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
packages/supabase/manifest.yml	105	Elastic.MenuArrows	Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
packages/supabase/changelog.yml	1	Elastic.Versions	Use 'later versions' instead of 'newer versions' when referring to versions.

---

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.

[github-actions]

TL;DR

The Check integrations supabase_integration_otel step failed, but the supplied Buildkite log does not contain the underlying package-test or validation error. It only records the package as failed at line 75, followed by stack teardown and artifact upload; identifying a source-level root cause from this data would be speculative. The separate changelog-link failure is already reported by the existing Buildkite comment and is not repeated here.

Remediation

• Re-run ./.buildkite/scripts/test_one_package.sh packages/supabase_integration_otel origin/main 5d313c95ba0479d2e3bfba5bf997ff0fd937cc05 with the complete command output, or expose the failed test result/log artifact from build 46060.
• Inspect the first failing package test or validation message before changing the integration; the current log does not identify a failing file, assertion, manifest field, or service error.

Investigation details

Root Cause

Not determinable from the available package log. The log ends the test phase with --- [supabase_integration_otel] failed and exit status 1, then immediately begins artifact upload. No actionable error appears before that point.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/46060
• Job/step: Check integrations supabase_integration_otel
• Key log excerpt: /tmp/gh-aw/buildkite-logs/integrations-check-integrations-supabase_integration_otel.txt:75-80 shows only the generic failure and exit status; lines 82 onward show artifact upload.
• The PR head package manifest declares prometheus_input_otel as its required input and includes three data streams, but the available failure output does not say whether dependency resolution, package validation, pipeline tests, or stack tests failed.

Verification

• Not run: the checkout is not at PR commit 5d313c95ba0479d2e3bfba5bf997ff0fd937cc05, and the supplied Buildkite output omits the failing test details needed to reproduce the failure confidently.

Follow-up

Once the first package-test error is available, trace it against the PR head diff and update the remediation with the exact file and line.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[teresaromero]

I've tried to build the package and the bundle looks good. I've installed into a 9.4.4 stack and i see variables and options as expected.

However, i encourage to have a good set of tests for the data streams so there is a clear expectation and good review that all is set as expected. Could you add policy tests and some default system tests with a basic mock service? If i recall correctly supabase can be set with a docker environment, so we should be able to check this out?

[teresaromero]

when installing this with elastic-package stack up i get an error, this package is not available yet? also, i have not seen it locally.

[ishleenk17]

YEs this package will be merged soon.
Also say if we update the version on content package with some change. I am hoping this package automatically undestands to always pick the latest pacakge. Or is it expected to change the version of the content packa here too.
Version should be a minimum version criteria imo. Else it should always pick the latest
@teresaromero

[ishleenk17]

@mrodm @teresaromero
Since we are going with the workaround of enabling the TSDB index manually for now.
I a unable to write proper tests. As I want to keep TSDB but the current dimention field (that I had to add to validate) is not semthing that is present in all the documents.
And I don't want to put another field attributes.* as dimension field as if I do that would overwirete tha. mappings of the other child fields of attributes.*

Do you have any suggestion on how to go about it ?
Or else for now, I would skip the test part. Till the time we have the datatreams using TSDB by default.

[mykola-elastic]

Configuration was pretty straightforward to me and it worked. LGTM

[teresaromero]

This package depends on #20265 being on EPR; on install time. I guess it can be released but for prod use the content pack should be available.

This is not surfacing here because there is no system test that requires package installation, just build. Composable packages require only inputs, content dependencies are downloaded by fleet.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: b647dc4

History

• 💚 Build #46809 succeeded 27de0ac
• 💚 Build #46389 succeeded 8659ce6
• 💔 Build #46360 failed fd13112
• 💔 Build #46359 failed ab8360a
• 💔 Build #46218 failed 4e46af2
• 💔 Build #46191 failed 0dff13c

[elastic-vault-github-plugin-prod]

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