Support for temporary http status codes

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, python
Domain
cloud, observability

Research direction

Start by tracing the Lambda's HTTP status handling and CloudWatch metric emission. Clarify whether the expected behavior is a configurable grace period or a different metric value for temporary status codes; done should define the configuration and ensure alarms do not trigger while the temporary response remains within the grace period.

Written by the indexing model from the issue text.

Description

enhancement lambda-http-check

Use-Case: Someone manually puts an endpoint into some sort of maintenance mode so instead of return a 200 it now returns a 302.

Right now this triggers a status code metric to change for 0 to 1. It would be nice to be able to specify a grace period for this temporary status code.

Another option would be to output a different metric value when the temporary status code is being returned.

This would then be able to not trigger alarms unless the temporary status code remains in-place for greater than grace period

Dominant language
Python
Stars
33
Forks
16
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from base2Services/aws-lambda-http-check

All issues in base2Services/aws-lambda-http-check

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.