Coupled the anonymized Cura id with the same id in CuraEngine Sentry, allowing us to determine the general health of the engine.
Allow for tracking of internal QA users by settings the environmental variable CURAENGINE_SENTRY_USER=pietje.puk@ultimaker.com
You can then filter issues in Sentry using the user.email:pietje.puk@ultimaker.com this allows you to quickly identify the crash that occurred during QA. It is recommended to make this environmental variable persistent, since all crashes from builds are after all logged.
Send over additional log info as breadcrumbs.
Add the tag plugin_<specific_engine_plugin_name>.version such that we can also track if an engine plugin is being used and which version might give us trouble
Type of change
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
How Has This Been Tested?
[X] from source
[X] from build
Test Configuration:
Operating System: Linux
Checklist:
[X] My code follows the style guidelines of this project as described in UltiMaker Meta
Description
Coupled the anonymized Cura id with the same id in CuraEngine Sentry, allowing us to determine the general health of the engine.
Allow for tracking of internal QA users by settings the environmental variable
CURAENGINE_SENTRY_USER=pietje.puk@ultimaker.comYou can then filter issues in Sentry using the
user.email:pietje.puk@ultimaker.comthis allows you to quickly identify the crash that occurred during QA. It is recommended to make this environmental variable persistent, since all crashes from builds are after all logged.Send over additional log info as breadcrumbs.
Add the tag
plugin_<specific_engine_plugin_name>.versionsuch that we can also track if an engine plugin is being used and which version might give us troubleType of change
How Has This Been Tested?
Test Configuration:
Checklist: