Skip to content

Conversation

@loosebazooka
Copy link
Member

Add the slos for rekor reads.

Signed-off-by: Appu Goundan <[email protected]>
@loosebazooka loosebazooka requested a review from a team as a code owner October 30, 2025 14:27
Copy link
Contributor

@haydentherapper haydentherapper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this SLO is not met, will this trigger a page? If so, what's the action that an oncaller should take?

@loosebazooka
Copy link
Member Author

loosebazooka commented Oct 30, 2025

Right, so merging this does nothing. I think what we need to do is allow a passthrough of the severity variable and then activate the slo so we control paging on the SLO module. I don't even know what kind of action an oncaller can take here -- gcs is down? our lb is down (is this even detected)?

Copy link
Contributor

@haydentherapper haydentherapper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, I'd like this to be a non-pageable SLO, so either just a dashboard or like you said, use severity to downgrade this to a warn.


availability_slos = {
gcs-read-availability = {
display_prefix = "Rekor V2 Availability"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd mention "Read Availability" or something like that

@loosebazooka
Copy link
Member Author

I'll go add the severity passthrough to slo first then.

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