[ADVAPP-127] & [ADVAPP-128]: Creating and Managing SLAs

[danharrin]

Ticket(s) or GitHub Issue

• https://canyongbs.atlassian.net/browse/ADVAPP-127
• https://canyongbs.atlassian.net/browse/ADVAPP-128

Technical Description

Implemented SLAs, related to a type-priority. Monitored compliance with Eloquent rather than on the database level for now.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Content or styling update (Changes which don't affect functionality)
• DevOps
• Documentation

Screenshots (if appropriate)

Screen.Recording.2024-01-16.at.18.34.36.mp4

Any deployment steps required?

A deployment step could be a command that needs to be executed or an ENV key that needs to be added, for example.

• Yes, please specify
• No

---

Before contributing and submitting this PR, make sure you have:

• Read the contributing guidelines.
• Title the PR with the ticket/issue number and a short description of the changes made. Or if no ticket/issue exists, title the PR with a short description of the changes made
• Linked a relevant ticket or issue or describe the issue/feature which this PR resolves/implements.
• Resolved all conflicts, if any.
• Rebased your branch PR on top of the latest upstream develop branch.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
2.2% Duplication on New Code

See analysis details on SonarCloud