List of products / apps we want to test with CKSource Monitoring

[dpawlowski-cksource]

Why

As we want to make this tool a central place with information about our product's health, we need to specify a list of all PUBLIC products/applications available for customers.

What

👇 Below is a list of public products / sites / apps 👇

CKEditor homepage

• [x] Ping https://ckeditor.com/

CKSource homepage

• [x] Ping https://cksource.com/

Online HTML Editor

• [x] Ping https://onlinehtmleditor.dev/

Online Markdown Editor

• [x] Ping https://onlinemarkdowneditor.dev/

CKEditor demo pages

new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/feature-rich/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#classic' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#document' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#balloon' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#balloon-block' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#inline' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#bottom-toolbar' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/editor-types/#button-grouping' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ai-assistant/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/collaboration/demo/#real-time-collaboration' ),
new EditorDemoTest( agent, 'https://ckeditor.com/collaboration/demo/#collaboration' ),
new EditorDemoTest( agent, 'https://ckeditor.com/productivity-pack/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/internationalization/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/export-to-pdf-word/#export-to-pdf' ),
new EditorDemoTest( agent, 'https://ckeditor.com/export-to-pdf-word/#export-to-word' ),
new EditorDemoTest( agent, 'https://ckeditor.com/export-to-pdf-word/#pagination' ),
new EditorDemoTest( agent, 'https://ckeditor.com/import-from-word/demo/#simple-import' ),
new EditorDemoTest( agent, 'https://ckeditor.com/productivity-pack/paste-from-office-enhanced-demo/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckbox/demo/#ckeditor-with-ckbox' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/html-support/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/markdown/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/ckeditor-5/demo/headless/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/mathtype/' ),
new EditorDemoTest( agent, 'https://ckeditor.com/spellchecker/' )

[LukaszGudel]

CKEditor origins

Our ckeditor.com page is kinda complicated on the Cloudfront side. We have many rules defined and depending on the path the Cloudfront is using a different origin (source) URL:

Pinging just the https://ckeditor.com/ is not enough as that will check only the S3 origin with the main website, while other origins may be not working (just like in the case from the 12th of June where I broke some ckeditor.com functionality while the main side and docs where working correctly).

Thus we should also test/ping:

• https://ckeditor.com/docs/
• https://ckeditor.com/ckeditor-5/builder/
• https://ckeditor.com/cke4/addons/plugins/all
• https://ckeditor.com/docs/ckfinder/ckfinder3/
• https://origin.ckeditor.com/old/forums
• https://ckeditor.com/ckfinder/demo/ (this CKFinder demo is using /apps/ path to make requests to ckfinder "backend" adapter, this could be tested with EditorDemoTest() to make sure that the demo is loading without errors)
• https://ckeditor.com/partners/ (this is a redirect to an external website that mimics our headers/footers/styles and presents some info about partners)
• https://ckeditor.com/technology-partners (this is a redirect to an external website that mimics our headers/footers/styles and presents some info about partners)

[LukaszGudel]

CDNs

Must have. We don't have any other monitoring for our CDNs and if something would break we would learn about it from customers.

• https://cdn.ckeditor.com/
• https://download.cksource.com/
• https://cdn.ckbox.io/ckbox/latest/ckbox.js (there is no homepage here so we could add some empty health.html file that could be pinged to reduce the transfer)
• https://download.ckbox.io/ckbox/ckbox_2.4.0.zip (there is no homepage here so we can add some empty health.html file that could be pinged to reduce the transfer)

Internal CDNs

We don't have to check them but these cdns might be useful for devs/qa and if something broke we would only notice it if someone wanted to access it. IMO, it's nice to have but optional.

• https://ckeditor5.github.io/docs/nightly/ckeditor5/latest/index.html
• https://builder.ckeditor-dev.com/ckeditor-5/builder/
• https://builder-nightly.ckeditor-dev.com/ckeditor-5/builder/
• https://portal-storybook.ckeditor-dev.com/ (requires basic auth, same as our other preview websites)
• https://ckbox-storybook.cke-cs-dev.com/ (requires basic auth, same as our other preview websites)

Important internal tools

These tools are handling important integrations or are listening for webhooks and then reacting to them, thus any downtime for these tools can negatively impact our workflows or in the case of CLA and buttercms-ai-proxy also devs outside our org/end-users. We will get alerts on Slack if these services would not be responding to healthchecks or would restart often, but still it may be nice to have them also monitored in CKSource Monitoring. Your call 😄

• https://cla.tiny.cloud/tiny/img/cla-workflow.png (we should contact Robert/Bartek Młotek to see if there are any lighter files to ping)
• https://cla.ckeditor.com/cksource/img/cla-workflow.png (we should contact Robert/Bartek Młotek to see if there are any lighter files to ping)
• https://buttercms-ai-proxy.internal.cke-cs-dev.com/health/liveliness
• https://buttercms-ai-proxy.internal.cke-cs.com/health/liveliness
• https://builder-api.internal.cke-cs-dev.com/healthz/live
• https://builder-api.ckeditor.com/healthz/live
• https://zenhub-integration.internal.cke-cs-dev.com/
• https://merge-branches.internal.cke-cs-dev.com/
• https://docs-builder.internal.cke-cs-dev.com/favicon.ico

Less important internal tools

Other tools. We already have health checks and alerts for them, but if we go for all the apps and services in the monitoring then it would be nice to have them monitored as well.

• https://scrum-poker.internal.cke-cs-dev.com/
• https://qa-automation.internal.cke-cs-dev.com/health
• https://hanghub.cksource.com/healthz
• https://cs-framework-docs.internal.cke-cs-dev.com/healthz

[dpawlowski-cksource]

We should also cover these domains: https://github.com/cksource/cs/issues/19797#issuecomment-2297242615