jop-software / typo3-sentry-client Goto Github PK

This ensures we don't mess up our lower constraints

Docs: https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/WritingDocForExtension/Index.html

the typo3 rector configuration got moved out of rector/rector and all configuration changed in 0.14

Check and ensure TYPO3 11.5 (LTS) Compatability

make use of typo3/minmal like EXT:loki

Setup the intended TYPO3 Extension testing with docker-composer.

The setup should run locally and in GHA.

See: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Testing/ExtensionTesting.html

The version defined in ext_emconf.php is still 1.0.0 instead of 1.1.0 which would be the latest release.

Remove those we don't need to run the extension.

Followup for 0970039 and #35.

This change deactivated transaction support for cli processes.

Tasks

• Start transaction for cli
• Stop transaction for cli
  The middleware doesn't get executed. We need to find another way to finish the transaction in cli context.

This should be possible with ext_conf_template and environment variables

TYPO3 Documentation: https://docs.typo3.org/m/typo3/reference-coreapi/10.4/en-us/ApiOverview/Logging/Logger/Index.html

There is currently not much to test but we should at least bootstrap them.

Ooops ...

For the Headless PWA approcah we would need to inject a JS SDK into NuxtJS.
I guess thats better haused in a separate plugin.

Check weather is makes sense to create a own typo3-nuxt-pwa extension or if we can reccomend an existing NuxtJS Sentry Integration.

Uncaught TYPO3 Exception #1436717322: The parsedUri "http:///var/www/html/vendor/bin/typo3" appears to be malformed
thrown in file /var/www/html/public/typo3/sysext/core/Classes/Http/Uri.php
in line 125

Deactivating the extension helps.
I first recognized that on the scheduler:run task of the typo cli.

See jop-software/typo3-loki

I guess it wouldn't be that hard to ensure compatability with TYPO3 11.4

Based on this package, everyone can implement cron monitoring themself, but can we build it in a generic way that automatically triggers for every Scheduler Task?

https://docs.sentry.io/product/crons/

Send use information in a user databag to sentry.
This feature should be Opt-In because of data protection rules.

Can this extension lead to performance issues? And If so, how can we mitigate them?

Currently, the message for is always empty

"message":""

this prevents e.G. Inbound Filters to work properly.

• Run agains PHP 7.4, 8.0 and 8.1
• Searate Linting and testing into multiple workflows / jobs

TYPO3 Documentation: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/ConfigurationOptions/Index.html

Sentry documentation: https://docs.sentry.io/platforms/php/performance/

We need to basically change two things:

• Initialize Sentry on every request
• Pass the required configuration to the Sentry Client

Install and configure phpstan/phpstan.
PHPStan should also run in pipelines for each push / pull-request.

in parallal to #24

Docs: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Testing/ProjectTesting.html

Sentry allows for User Feedback, we should integrate that.
This needs to be configurable due to GDPR.

See: https://docs.sentry.io/product/user-feedback/

There should be an option to send a example exception to Sentry from the Backend.

Two options

1. A Button in the extension configuration
2. A Button in the "Clear Cache" dropdown

In the case of Option 2, should the permission to test the integration be configurable to prevent abuse.

Other extensions should have an option to register e.G. their own metrics by subscribing to a custom event.

• Check and ensure compatability with TYPO3 12
• Run CI against 11 and 12

Note: When possible both Version 11 and 12 should be supported in the same major version.

This extension cannot be installed without composer currently.
We rely on some composer packages, which are not part of TYPO3 itself.

Is it possible to run composer install when creating a release and include the vendor directory in the ZIP-Archive Github generates for the release?
Also: I guess we need to adjust dependency loading.

Is this even worth it? How many TYPO3 installations nowadays do not use composer?

EDIT
It seems like there is a pretty easy way with composer to accomplish this.
Example from EXT:solr: TYPO3's EXT:solr does this: https://github.com/TYPO3-Solr/ext-solr/blob/main/Resources/Private/Php/ComposerLibraries/composer.json

tbd

TYPO3 11 itself uses "php": "^7.4 || ^8.0" we should match that.

https://docs.sentry.io/platforms/php/configuration/options/?original_referrer=https%3A%2F%2Fduckduckgo.com%2F#error-types

• #47
• GH-Actions workflow for auto publish to TER
• Publish a new release

• Readme

Successor-Of: #10

There should be an options to blacklist exceptions.

Introduce a new system configuration that contains a regex that gets matches agains every exception FQCN of the exception.

Should be configurable, because it can be a GDPR issue

Rector: https://github.com/rectorphp/rector
TYPO3 "Extension": https://github.com/sabbelasichon/typo3-rector