Details
-
Task
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
Description
Context
Leverage Jenkins to regularly check whether the Connector credentials are still valid?
Each analytics connector could e.g. have a IT that does this check regularly.
- Google Analytics
- Matomo
- Adobe Analytics
Acceptance criteria
Create a Jenkins job to evaluate the endpoints generated for analytics healthcheck
Development notes
Check first if a basic bash file can get executed in the project and evaluate the outcome.
Integrate if we can use https://learning.postman.com/docs/collections/using-newman-cli/newman-options/#exit-status to inject and make the build fail
Or, otherwise, another implementation can be https://blog.jetbrains.com/idea/2022/12/http-client-cli-run-requests-and-tests-on-ci/
Execute the installation via Jenkins of new script and evaluate the exit status accordingly.
SRE notes
Using the synthetic monitoring or uptime tests to check the Addon connectors availability and performance across development environments.
Checklists
Attachments
Issue Links
- clones
-
MKTAUT-157 Set up Jenkins jobs to regularly check Connectors credentials
-
- Open
-
- is cloned by
-
EXTDAM-385 Set up Jenkins jobs to regularly check Connectors credentials
-
- Open
-
- is related to
-
ANALYTICS-470 Action plan for monitoring the analytics connectors
-
- Closed
-