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

Should non-OK status entries be listed for non-matching component groups? #169

Open
atc0005 opened this issue Nov 28, 2022 · 1 comment
Open
Labels
app/check_statuspage_components question Further information is requested
Milestone

Comments

@atc0005
Copy link
Owner

atc0005 commented Nov 28, 2022

Example:

$ go run ./cmd/check_statuspage_components/ --url 'https://status.zoom.us/api/v2/components.json' --group 6zvc1tw9rpfm
OK: 0 evaluated "Zoom" components have a non-operational status (6 evaluated, 135 total)
**THRESHOLDS**

* CRITICAL: major_outage
* WARNING: under_maintenance, partial_outage, degraded_performance

**DETAILED INFO**

Specified filter: {Group: "6zvc1tw9rpfm", Components: ""}
NOTE: Component count (135) is higher than display limit (50); overriding default display of OK components.

Page: Zoom (https://status.zoom.us)
Time Zone: America/Los_Angeles
Last Updated: 2022-11-28T07:33:01-08:00


NOTE: Omitting OK/operational components as requested.


GROUP NAME                    COMPONENT NAME                STATUS
----------                    --------------                ------
LATIN AMERICA - Zoom Phone    Zoom Phone                    DEGRADED PERFORMANCE
LATIN AMERICA - Zoom Phone    Calling (Inbound/Outbound)    DEGRADED PERFORMANCE



Summary:

* Filtering applied to components set: true
* Evaluating all components in the set: false
* Omitting OK/operational components (if requested): true
* Number of total top-level components: 6
* Number of total component groups: 20
* Number of total subcomponents: 109
* Number of total problem components: 2
* Number of ignored problem components: 2
* Number of remaining problem components: 0


 | 'all_problem_components'=2;;;; 'remaining_components_critical'=0;;;; 'remaining_components_warning'=0;;;; 'all_component_groups'=20;;;; 'all_components_warning'=3;;;; 'remaining_components_unknown'=0;;;; 'time'=222ms;;;; 'all_components'=135;;;; 'all_components_critical'=0;;;; 'remaining_components_ok'=6;;;; 'excluded_problem_components'=2;;;; 'remaining_problem_components'=0;;;; 'all_components_unknown'=0;;;; 'all_components_ok'=132;;;;

These non-OK status components have nothing to do with the specified component group:

GROUP NAME                    COMPONENT NAME                STATUS
----------                    --------------                ------
LATIN AMERICA - Zoom Phone    Zoom Phone                    DEGRADED PERFORMANCE
LATIN AMERICA - Zoom Phone    Calling (Inbound/Outbound)    DEGRADED PERFORMANCE

I suspect that this was intentional on my part, but it's been so long since I worked with the codebase that I don't recall for sure and will need to review docs/code to be sure.

@atc0005 atc0005 added question Further information is requested app/check_statuspage_components labels Nov 28, 2022
@atc0005 atc0005 added this to the Future milestone Nov 28, 2022
@atc0005
Copy link
Owner Author

atc0005 commented Nov 6, 2023

Stumbled across this again today, came back here to file a GH issue for it so I could research further.

I think a compromise is to detect this scenario (other problems exist, but not problems for the specified component group) and provide some lead-in text noting as much right before the table in the output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/check_statuspage_components question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant