Skip to content

Conversation

@luke-zhu
Copy link
Contributor

What does this PR do?

The schedule previously ran once an hour. It now should do what the interval variable says it does

Testing

I tested 1 minute, 5 minutes, and 3 hours

The schedule previously ran once an hour.

I tested 1 minute, 5 minutes, and 3 hours
@luke-zhu luke-zhu changed the title fix: metric submodule schedule fix(cloudwatch_metrics): correct rule schedule expression Mar 11, 2023
@luke-zhu luke-zhu merged commit 0b118ae into main Mar 11, 2023
@luke-zhu luke-zhu deleted the luke/metric-schedule branch March 11, 2023 03:22
jta pushed a commit that referenced this pull request Mar 13, 2023
PR #62 fixed our schedule expression to fire at the correct cadence, but
subtly changed the time at which the rule would trigger. The use of the
`rate` function ensures a rule will trigger at regular intervals from
rule creation. Given the nature of the data we are collecting, we want
rules to trigger aligned to fixed time boundaries (e.g. every minute,
every hour). This commit reintroduces a correct cron expression.
jta pushed a commit that referenced this pull request Mar 13, 2023
PR #62 fixed our schedule expression to fire at the correct cadence, but
subtly changed the time at which the rule would trigger. The use of the
`rate` function ensures a rule will trigger at regular intervals from
rule creation. Given the nature of the data we are collecting, we want
rules to trigger aligned to fixed time boundaries (e.g. every minute,
every hour). This commit reintroduces a correct cron expression.
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.

3 participants