Skip to content

Service Metrics - Availability uptime and downtime#5665

Merged
fhibf merged 3 commits into
mainfrom
user/fhibf/serviceMetrics
Jul 10, 2026
Merged

Service Metrics - Availability uptime and downtime#5665
fhibf merged 3 commits into
mainfrom
user/fhibf/serviceMetrics

Conversation

@fhibf

@fhibf fhibf commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Description

Emitting availability uptime and downtime based on the response of health checks.

Related issues

Addresses AB#197037

Testing

Describe how this change was tested.

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@fhibf fhibf added this to the FY27\Q1\2wk\2wk01 milestone Jul 10, 2026
@fhibf fhibf requested a review from a team as a code owner July 10, 2026 01:29
@fhibf fhibf added Enhancement Enhancement on existing functionality. No-Issue-Activity This issue is now considered stale and will be closed soon Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs No-PaaS-breaking-change No-ADR ADR not needed labels Jul 10, 2026
@fhibf fhibf changed the title Service Metrics Service Metrics - Availability uptime and downtime Jul 10, 2026
@codecov-commenter

codecov-commenter commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.56%. Comparing base (fab0817) to head (aaeb7be).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5665      +/-   ##
==========================================
- Coverage   77.56%   77.56%   -0.01%     
==========================================
  Files        1004     1005       +1     
  Lines       36924    36943      +19     
  Branches     5600     5601       +1     
==========================================
+ Hits        28641    28653      +12     
- Misses       6926     6929       +3     
- Partials     1357     1361       +4     

see 13 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@fhibf fhibf enabled auto-merge (squash) July 10, 2026 22:36
@fhibf fhibf merged commit 318be27 into main Jul 10, 2026
49 checks passed
@fhibf fhibf deleted the user/fhibf/serviceMetrics branch July 10, 2026 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Enhancement Enhancement on existing functionality. No-ADR ADR not needed No-Issue-Activity This issue is now considered stale and will be closed soon No-PaaS-breaking-change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants