[ANALYTICS-469] Set up Jenkins jobs to regularly check Connectors credentials Created: 22/Jan/21  Updated: 22/Aug/23

Status: Open
Project: Analytics
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MKTAUT-157 Set up Jenkins jobs to regularly chec... Open
is cloned by EXTDAM-385 Set up Jenkins jobs to regularly chec... Open
relation
is related to ANALYTICS-470 Action plan for monitoring the analyt... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Connectors Health-checks
Team: AuthorX

 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.


Generated at Sun Feb 11 23:19:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.