DPLT-1044 Create scheduled Lambda to write lag behind near social #137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces
latest-post-metrics-writer
with a scheduled Lambda which writes the block height difference between the QueryAPI social feed and the near social feed. It does this by fetching the latest block height from each API, and writing the difference to CloudWatch.Writing the metrics from the QueryAPI indexers themselves has the following problems:
Having a scheduled Lambda will create a consistent metrics timeline which we can trigger alerts off.