autotel-posthog 0.1.0

package/LICENSE

@@ -0,0 +1,191 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the
+copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with
+that entity. For the purposes of this definition, "control" means (i) the
+power, direct or indirect, to cause the direction or management of such
+entity, whether by contract or otherwise, or (ii) ownership of fifty
+percent (50%) or more of the outstanding shares, or (iii) beneficial
+ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source,
+and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation
+or translation of a Source form, including but not limited to compiled
+object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that
+is included in or attached to the work (an example is provided in the
+Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form,
+that is based on (or derived from) the Work and for which the editorial
+revisions, annotations, elaborations, or other modifications represent, as
+a whole, an original work of authorship. For the purposes of this License,
+Derivative Works shall not include works that remain separable from, or
+merely link (or bind by name) to the interfaces of, the Work and Derivative
+Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the
+purposes of this definition, "submitted" means any form of electronic,
+verbal, or written communication sent to the Licensor or its
+representatives, including but not limited to communication on electronic
+mailing lists, source code control systems, and issue tracking systems that
+are managed by, or on behalf of, the Licensor for the purpose of discussing
+and improving the Work, but excluding communication that is conspicuously
+marked or otherwise designated in writing by the copyright owner as "Not a
+Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on
+behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable (except as stated in
+this section) patent license to make, have made, use, offer to sell, sell,
+import, and otherwise transfer the Work, where such license applies only to
+those patent claims licensable by such Contributor that are necessarily
+infringed by their Contribution(s) alone or by combination of their
+Contribution(s) with the Work to which such Contribution(s) was submitted.
+If You institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work or a
+Contribution incorporated within the Work constitutes direct or
+contributory patent infringement, then any patent licenses granted to You
+under this License for that Work shall terminate as of the date such
+litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and
+in Source or Object form, provided that You meet the following conditions:
+
+     (a) You must give any other recipients of the Work or Derivative Works
+a copy of this License; and
+
+     (b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+     (c) You must retain, in the Source form of any Derivative Works that
+You distribute, all copyright, patent, trademark, and attribution notices
+from the Source form of the Work, excluding those notices that do not
+pertain to any part of the Derivative Works; and
+
+     (d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must include a
+readable copy of the attribution notices contained within such NOTICE file,
+excluding those notices that do not pertain to any part of the Derivative
+Works, in at least one of the following places: within a NOTICE text file
+distributed as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or, within a
+display generated by the Derivative Works, if and wherever such third-party
+notices normally appear. The contents of the NOTICE file are for
+informational purposes only and do not modify the License. You may add Your
+own attribution notices within Derivative Works that You distribute,
+alongside or as an addendum to the NOTICE text from the Work, provided that
+such additional attribution notices cannot be construed as modifying the
+License.
+
+     You may add Your own copyright statement to Your modifications and may
+provide additional or different license terms and conditions for use,
+reproduction, or distribution of Your modifications, or for any such
+Derivative Works as a whole, provided Your use, reproduction, and
+distribution of the Work otherwise complies with the conditions stated in
+this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to
+the Licensor shall be under the terms and conditions of this License,
+without any additional terms or conditions. Notwithstanding the above,
+nothing herein shall supersede or modify the terms of any separate license
+agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor, except
+as required for reasonable and customary use in describing the origin of
+the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to
+in writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any
+warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
+FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
+determining the appropriateness of using or redistributing the Work and
+assume any risks associated with Your exercise of permissions under this
+License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether
+in tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to
+in writing, shall any Contributor be liable to You for damages, including
+any direct, indirect, special, incidental, or consequential damages of any
+character arising as a result of this License or out of the use or
+inability to use the Work (including but not limited to damages for loss of
+goodwill, work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor has been
+advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the
+Work or Derivative Works thereof, You may choose to offer, and charge a fee
+for, acceptance of support, warranty, indemnity, or other liability
+obligations and/or rights consistent with this License. However, in
+accepting such obligations, You may act only on Your own behalf and on Your
+sole responsibility, not on behalf of any other Contributor, and only if
+You agree to indemnify, defend, and hold each Contributor harmless for any
+liability incurred by, or claims asserted against, such Contributor by
+reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate
+notice, with the fields enclosed by brackets "[]" replaced with your own
+identifying information. (Don't include the brackets!)  The text should be
+enclosed in the appropriate comment syntax for the file format. We also
+recommend that a file or class name and description of purpose be included
+on the same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,158 @@
+# autotel-posthog
+
+Join autotel traces to PostHog sessions, replays and events. One session id, and a link in both directions.
+
+PostHog knows two things a tracer cannot work out for itself: which recorded session a page view belongs to, and which person is behind it. autotel knows which trace explains a given moment. This package is the join, and it depends on no PostHog package to make it — the methods it reads are the public browser API, read structurally off whatever instance is on the page.
+
+It is also where `PostHogSubscriber` lives, so one package covers PostHog end to end: the browser join on `autotel-posthog`, product events from the server on `autotel-posthog/subscriber`.
+
+## Install
+
+The two entry points need different things, so install the half you use.
+
+```bash
+# Browser join — needs the SDK whose session you are joining
+npm install autotel-posthog posthog-js autotel-web
+
+# Server events
+npm install autotel-posthog posthog-node autotel autotel-subscribers
+```
+
+Every peer is declared optional so the half you skip does not warn about
+packages it will never import. `posthog-js` is not bundled: two copies on one
+page means two session managers and two different answers to
+`get_session_id()`, which would break the join this package exists to make.
+
+## The short version
+
+One call wires both directions — PostHog's half itself, and the enricher for the tracer's half:
+
+```ts
+import posthog from 'posthog-js';
+import { initFull } from 'autotel-web/full';
+import { joinPostHog } from 'autotel-posthog';
+
+posthog.init('<key>');
+
+initFull({
+  service: 'web',
+  endpoint: 'https://collector.example.com/v1/traces',
+  spanEnrichers: [joinPostHog(posthog)],
+});
+```
+
+`joinPostHog` appends its hook to any `before_send` chain the app already has rather than replacing it, and calling it again — strict mode, HMR, a re-render — does not stack up another copy.
+
+Add `traceUrl` and PostHog events carry a link, not just ids to join on:
+
+```ts
+spanEnrichers: [
+  joinPostHog(posthog, {
+    traceUrl: ({ traceId }) => `https://traces.example.com/${traceId}`,
+    featureFlags: ['new-checkout'],
+  }),
+],
+```
+
+Everything below is what `joinPostHog` does, for anyone who wants the halves separately.
+
+## The halves, separately
+
+### Trace → PostHog
+
+`posthogCompatibility()` is a span enricher. It stamps the PostHog session and person onto spans, and on spans that failed, a replay link deep-linked to the moment it broke.
+
+```ts
+import { initFull } from 'autotel-web/full';
+import { posthogCompatibility } from 'autotel-posthog';
+
+initFull({
+  service: 'web',
+  endpoint: 'https://collector.example.com/v1/traces',
+  spanEnrichers: [posthogCompatibility()],
+});
+```
+
+| Attribute            | Source                                                    | On which spans                |
+| -------------------- | --------------------------------------------------------- | ----------------------------- |
+| `session.id`         | `posthog.get_session_id()`                                | every span                    |
+| `user.id`            | `posthog.get_distinct_id()`                               | every span                    |
+| `session.replay.url` | `posthog.get_session_replay_url({ withTimestamp: true })` | spans that recorded an error  |
+| `feature_flag.<key>` | `posthog.getFeatureFlag(key)`                             | every span, for keys you name |
+
+Identity is read when the span **starts**, not when it ends. PostHog rotates a session after 30 minutes idle and `identify()` can land mid-request; a long span asking at the end would be filed under whoever the visitor had become by then. The replay link is the one thing decided at the end, because only the end knows whether the span failed — and it is withheld if the session rotated in between, since the link would point at a recording the span has nothing to do with.
+
+A flag that evaluates to `false` is kept as a boolean: "not in the variant" is an answer, and comparing the two groups is the whole point. Only a flag PostHog has no opinion on is omitted.
+
+Use `spanEnrichers`, not `spanProcessor`. The latter _replaces_ the pipeline autotel builds, so passing an enricher there switches off the export you just configured.
+
+An error span now carries a link to the replay at the second it broke, in whatever backend the spans land in — so "a slow span" becomes "watch the person it was slow for" without leaving the trace view.
+
+The link appears only when `posthog.sessionRecordingStarted()` is true. `get_session_replay_url()` composes a URL from the session id whether or not anything was recorded, so replay being disabled, sampled out, or simply not started yet would otherwise produce a link that lands on an empty player — and one dead link is enough to stop people trusting the ones that work. An instance too old or too stubbed to answer produces no link rather than a confident wrong one.
+
+#### Feature flags are named, never harvested
+
+```ts
+posthogCompatibility({ featureFlags: ['new-checkout'] });
+```
+
+Every flag is another attribute on every span. Naming them is what keeps an analytics convenience from becoming a cardinality bill. A flag PostHog has no opinion on yet is omitted; one that evaluated to `false` is kept, because that is an answer.
+
+### PostHog → trace
+
+`autotelBeforeSend()` is a PostHog `before_send` hook. It stamps `$trace_id`, `$span_id` and — when you supply `traceUrl` — `$trace_url` on every PostHog event from the span in progress, using the same property names autotel's server-side subscriber already writes.
+
+```ts
+import posthog from 'posthog-js';
+import { autotelBeforeSend } from 'autotel-posthog';
+
+posthog.init('<key>', { before_send: [autotelBeforeSend()] });
+```
+
+A `$exception` or a funnel drop-off in PostHog now names the trace that explains it. Events an earlier hook dropped stay dropped: `before_send` is a chain, and `null` means the page suppressed the event deliberately.
+
+## Product events from the server
+
+```ts
+import { Event } from 'autotel/event';
+import { PostHogSubscriber } from 'autotel-posthog/subscriber';
+
+const events = new Event('checkout', {
+  subscribers: [
+    new PostHogSubscriber({ apiKey: process.env.POSTHOG_API_KEY! }),
+  ],
+});
+```
+
+Server-side `track()` events go to PostHog carrying `$trace_id` and `$span_id` — the same property names the browser hook writes, so an event points back at its trace whichever side captured it. Needs `autotel-subscribers` alongside it, for the `EventSubscriber` base it extends.
+
+## Without the OpenTelemetry pipeline
+
+The minimal `autotel-web` build writes spans straight to OTLP and has no processor pipeline to hang an enricher on. Give it the session id directly:
+
+```ts
+import { init } from 'autotel-web';
+import { posthogSessionId } from 'autotel-posthog';
+
+init({ service: 'web', session: { id: posthogSessionId } });
+```
+
+## Three states, one of which answers questions
+
+A page is in one of three states, and only the last one can be asked anything:
+
+1. no `posthog` on the page at all,
+2. the loader snippet's array stub, which queues calls made before the real library arrives and has none of these methods,
+3. the loaded library — which still returns an empty session id until it finishes initializing.
+
+Every call this package makes is guarded for all three. Analytics that is still starting up never throws inside a fetch handler, and never produces an attribute that means nothing.
+
+## Which session id wins
+
+Where PostHog has a session id, it replaces the one `autotel-web` mints for itself. PostHog's id is what the replay, the funnels and the person profile are all keyed on, so a span carrying any other id links to nothing. Where PostHog has none yet, the locally minted id stands, because spans with no session at all are worse than spans with a session only autotel knows about.
+
+`user.id` and the rest are filled, never overwritten — a span that set them already knows something this package does not.
+
+## License
+
+Apache-2.0

package/dist/index.cjs

@@ -0,0 +1,267 @@
+Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
+let _opentelemetry_api = require("@opentelemetry/api");
+//#region src/posthog-like.ts
+/**
+* Whether this object can actually answer questions yet.
+*
+* The loader snippet leaves an array on `window.posthog` that queues calls, and
+* posthog-js later *replaces* it with the real instance. An integration holding
+* the array from before the swap holds something that will never answer, so the
+* only useful test is whether the methods are there.
+*/
+function isUsable(posthog) {
+	return typeof posthog?.get_session_id === "function";
+}
+/**
+* Call a PostHog getter without letting the page's analytics break the page's
+* tracing. A stub throws `TypeError`, a partly-initialized instance returns an
+* empty string, and neither is worth an attribute.
+*/
+function readString(fn, receiver) {
+	if (typeof fn !== "function") return void 0;
+	try {
+		const value = fn.call(receiver);
+		return typeof value === "string" && value.length > 0 ? value : void 0;
+	} catch {
+		return;
+	}
+}
+function readSessionId(posthog) {
+	return readString(posthog.get_session_id, posthog);
+}
+function readDistinctId(posthog) {
+	return readString(posthog.get_distinct_id, posthog);
+}
+/**
+* Whether a replay actually exists to link to.
+*
+* `get_session_replay_url()` composes a URL out of the session id whether or
+* not anything was recorded — replay disabled, sampled out, or simply not
+* started yet all still produce a link, and it lands on an empty player. Only
+* an affirmative answer counts, so an instance too old or too stubbed to say
+* produces no link rather than a confident wrong one.
+*/
+function isRecording(posthog) {
+	try {
+		if (typeof posthog.sessionRecordingStarted === "function") return posthog.sessionRecordingStarted() === true;
+		return posthog.sessionRecording?.started === true;
+	} catch {
+		return false;
+	}
+}
+function readReplayUrl(posthog) {
+	if (!isRecording(posthog)) return void 0;
+	const fn = posthog.get_session_replay_url;
+	if (typeof fn !== "function") return void 0;
+	try {
+		const value = fn.call(posthog, { withTimestamp: true });
+		return typeof value === "string" && value.length > 0 ? value : void 0;
+	} catch {
+		return;
+	}
+}
+/**
+* An evaluated flag value.
+*
+* `false` is an answer — "this person is not in the variant" — and is kept as a
+* boolean so a query can ask for it. Only `undefined`, meaning PostHog has no
+* opinion yet, is dropped: an attribute that says nothing is worse than an
+* absent one.
+*/
+function readFeatureFlag(posthog, key) {
+	const fn = posthog.getFeatureFlag;
+	if (typeof fn !== "function") return void 0;
+	try {
+		const value = fn.call(posthog, key);
+		if (value === void 0) return void 0;
+		return typeof value === "boolean" ? value : String(value);
+	} catch {
+		return;
+	}
+}
+//#endregion
+//#region src/compatibility.ts
+/** `SpanStatusCode.ERROR`, without importing the enum for one comparison. */
+const STATUS_ERROR = 2;
+function failed(span) {
+	return span.status?.code === STATUS_ERROR || span.attributes["exception.type"] !== void 0 || span.events?.some((event) => event.name === "exception") === true;
+}
+function resolvePostHog(options) {
+	const configured = typeof options.posthog === "function" ? options.posthog() : options.posthog;
+	if (isUsable(configured)) return configured;
+	const global = globalThis.posthog;
+	return isUsable(global) ? global : void 0;
+}
+function posthogCompatibility(options = {}) {
+	return {
+		/**
+		* Identity is read here, not in `onEnd`, because it is a fact about when
+		* the operation happened. PostHog rotates a session after 30 minutes idle,
+		* and `identify()` can land mid-request; a long span asking at the end
+		* would be filed under whoever the visitor had become by then rather than
+		* who started it.
+		*/
+		onStart(span, _context) {
+			const posthog = resolvePostHog(options);
+			if (!posthog) return;
+			const sessionId = readSessionId(posthog);
+			if (sessionId !== void 0) span.setAttribute("session.id", sessionId);
+			const attributes = span.attributes;
+			const fill = (key, value) => {
+				if (value !== void 0 && attributes[key] === void 0) span.setAttribute(key, value);
+			};
+			fill("user.id", readDistinctId(posthog));
+			for (const key of options.featureFlags ?? []) fill(`feature_flag.${key}`, readFeatureFlag(posthog, key));
+		},
+		/**
+		* Only the replay link is left for the end, because only the end knows
+		* whether the span failed.
+		*/
+		onEnd(span) {
+			if (!failed(span)) return;
+			const posthog = resolvePostHog(options);
+			if (!posthog) return;
+			const attributes = span.attributes;
+			if (attributes["session.replay.url"] !== void 0) return;
+			const current = readSessionId(posthog);
+			if (current === void 0 || current !== attributes["session.id"]) return;
+			const url = readReplayUrl(posthog);
+			if (url !== void 0) attributes["session.replay.url"] = url;
+		},
+		forceFlush() {
+			return Promise.resolve();
+		},
+		shutdown() {
+			return Promise.resolve();
+		}
+	};
+}
+//#endregion
+//#region src/before-send.ts
+/**
+* The other half of the join: PostHog events that know which trace they
+* happened inside.
+*
+* `posthogCompatibility()` teaches the trace about the session. This teaches
+* the session about the trace, so a `$exception` or a funnel drop-off in
+* PostHog carries the trace id that explains it, and the property names match
+* the ones autotel's server-side subscriber already writes — one set of names
+* whichever side captured the event.
+*
+* @example
+* ```ts
+* posthog.init('<key>', {
+*   before_send: [
+*     autotelBeforeSend({
+*       traceUrl: ({ traceId }) => `https://traces.example.com/${traceId}`,
+*     }),
+*   ],
+* });
+* ```
+*/
+/**
+* A PostHog `before_send` hook that adds `$trace_id` and `$span_id` from the
+* span in progress.
+*/
+function autotelBeforeSend(options = {}) {
+	return (event) => {
+		if (event === null) return null;
+		const spanContext = _opentelemetry_api.trace.getSpanContext(_opentelemetry_api.context.active());
+		if (!spanContext) return event;
+		const properties = event.properties;
+		if (properties["$trace_id"] === void 0) properties["$trace_id"] = spanContext.traceId;
+		if (properties["$span_id"] === void 0) properties["$span_id"] = spanContext.spanId;
+		if (options.traceUrl && properties["$trace_url"] === void 0) try {
+			const url = options.traceUrl({
+				traceId: spanContext.traceId,
+				spanId: spanContext.spanId
+			});
+			if (url !== void 0) properties["$trace_url"] = url;
+		} catch {}
+		return event;
+	};
+}
+//#endregion
+//#region src/join.ts
+/**
+* Marks our hook so a second call recognises it. Framework code runs more than
+* once — strict mode, HMR, a re-render — and a chain that grows on every render
+* stamps the same properties again and again.
+*/
+const MARKER = "__autotelBeforeSend";
+function existingHooks(posthog) {
+	const current = posthog.config?.before_send;
+	if (Array.isArray(current)) return current;
+	return current ? [current] : [];
+}
+function joinPostHog(posthog, options = {}) {
+	const resolve = () => resolvePostHog({
+		...options,
+		posthog
+	});
+	/**
+	* Returns true once the hook is in place. Kept retryable because the loader
+	* snippet's stub has no `set_config`: giving up at call time would leave
+	* every PostHog event on that page without its trace for the life of the
+	* page, and the real library usually arrives a moment later.
+	*/
+	const wire = () => {
+		try {
+			const instance = resolve();
+			if (!instance) return false;
+			const hooks = existingHooks(instance);
+			if (hooks.some((hook) => hook[MARKER])) return true;
+			if (typeof instance.set_config !== "function") return false;
+			const hook = autotelBeforeSend(options);
+			hook[MARKER] = true;
+			instance.set_config({ before_send: [...hooks, hook] });
+			return true;
+		} catch {
+			return false;
+		}
+	};
+	let wired = wire();
+	const enricher = posthogCompatibility({
+		...options,
+		posthog
+	});
+	return {
+		onStart(span, context) {
+			if (!wired) wired = wire();
+			enricher.onStart(span, context);
+		},
+		onEnd: (span) => enricher.onEnd(span),
+		forceFlush: () => enricher.forceFlush(),
+		shutdown: () => enricher.shutdown()
+	};
+}
+//#endregion
+//#region src/session-id.ts
+/**
+* PostHog's session id, shaped for `autotel-web`'s `session.id` provider.
+*
+* The span enricher covers full mode, where there is an OpenTelemetry pipeline
+* to hang a processor on. The minimal browser build has no such pipeline — it
+* writes spans straight to OTLP — so it takes the id from a function instead,
+* and this is that function:
+*
+* ```ts
+* import { init } from 'autotel-web';
+* import { posthogSessionId } from 'autotel-posthog';
+*
+* init({ service: 'web', session: { id: posthogSessionId } });
+* ```
+*
+* Returns `undefined` when PostHog is absent or not yet initialized, which is
+* the signal for autotel-web to fall back to minting its own id rather than
+* emitting spans with no session at all.
+*/
+function posthogSessionId(posthog) {
+	const instance = posthog ?? globalThis.posthog ?? void 0;
+	return instance ? readSessionId(instance) : void 0;
+}
+//#endregion
+exports.autotelBeforeSend = autotelBeforeSend;
+exports.joinPostHog = joinPostHog;
+exports.posthogCompatibility = posthogCompatibility;
+exports.posthogSessionId = posthogSessionId;