Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: App stats availability measurement #115

Merged
merged 1 commit into from
May 1, 2024

Conversation

acrmp
Copy link
Member

@acrmp acrmp commented Apr 30, 2024

Currently concerned with when stats are seen as unavailable by the client. Does not include when stats are set to zero by the Cloud Controller when one or more required metrics are missing.

README.md Outdated Show resolved Hide resolved
main.go Outdated Show resolved Hide resolved
Currently concerned with when stats are seen as unavailable by the
client. Does not include when stats are set to zero by the Cloud
Controller when one or more required metrics are missing.

Co-authored-by: Rebecca Roberts <rebecca.roberts@broadcom.com>
@ctlong ctlong merged commit c88e649 into cloudfoundry:main May 1, 2024
5 checks passed
@ctlong ctlong deleted the stats-availability branch May 1, 2024 16:49
winkingturtle-vmw added a commit to winkingturtle-vmw/cf-deployment-concourse-tasks that referenced this pull request May 9, 2024
Context: cloudfoundry/uptimer#115

After adding this new measurement, our CI is failing this measurement
because the default value of 0 is too aggresssive for cf-deployment.
This PR adds the ablity to set app_stats when needed.
ctlong pushed a commit to cloudfoundry/cf-deployment-concourse-tasks that referenced this pull request May 9, 2024
Context: cloudfoundry/uptimer#115

After adding this new measurement, our CI is failing this measurement
because the default value of 0 is too aggresssive for cf-deployment.
This PR adds the ablity to set app_stats when needed.
jochenehret added a commit to cloudfoundry/cf-deployment that referenced this pull request May 13, 2024
* don't run the upgrade jobs two times as the second attempt is a BOSH no-op and will not measure anything meaningful
* configure stats check threshold (see cloudfoundry/uptimer#115)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants