track serverless functions executions

[anamarn]

Solves:
https://github.com/twentyhq/private-issues/issues/74

TLDR
When a serverless function is executed, the result is send to tinybird event data source.

In order to test:

1. Set ANALYTICS_ENABLED to true
2. Put your TINYBIRD_INGEST_TOKEN from twenty_event_playground in your .env file
3. Don't forget to run the worker
4. Create your serverless function and run it
5. The event should be logged on the event datasource in twenty_event_playground

What is the structure of the payload of a serverless function event?

Here are two examples of the payload:
{"duration":37,"status":"SUCCESS","functionId":"a9fd87c0-af86-4e17-be3a-a6d3d961678a","functionName":"testingFunction"}

{"duration":34,"status":"ERROR","errorType":"ReferenceError","functionId":"a9fd87c0-af86-4e17-be3a-a6d3d961678a","functionName":"testingFunction"}

Possible improvments

• Change the status(str) to success(bool)
• Enrich data in the payload

[greptile-apps]

PR Summary

This pull request implements analytics tracking for serverless function executions, sending results to a Tinybird event data source.

• Added AnalyticsModule to ServerlessFunctionModule imports in packages/twenty-server/src/engine/metadata-modules/serverless-function/serverless-function.module.ts
• Integrated AnalyticsService in packages/twenty-server/src/engine/metadata-modules/serverless-function/serverless-function.service.ts to create events after function execution
• Implemented event payload structure including duration, status, error type, function ID, and name
• Requires ANALYTICS_ENABLED set to true and TINYBIRD_INGEST_TOKEN configured in .env file for testing

_{2 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Ensure that the 'serverless-function' string is defined as a constant to avoid typos

Suggested change

	this.analyticsService.create(
	eventInput,
	'serverless-function',
	workspaceId,
	);
	const ANALYTICS_SERVICE_NAME = 'serverless-function';
	this.analyticsService.create(
	eventInput,
	ANALYTICS_SERVICE_NAME,
	workspaceId,
	);

[greptile-apps]

style: Use optional chaining for error property access

Suggested change

	...(resultServerlessFunction.error && {
	errorType: resultServerlessFunction.error.errorType,
	}),
	...(resultServerlessFunction.error?.errorType ? {
	errorType: resultServerlessFunction.error.errorType,
	} : {}),

[FelixMalfait]

Change name to serverlessFunction.executed as discussed :). Otherwise all good for me!