feat: add structured monitoring to migration controller#259
feat: add structured monitoring to migration controller#259thomas-waite wants to merge 23 commits intomainfrom
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c43bcd5365
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b08129fb2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| crate::info!( | ||
| "migration_run.started total_processors={} timestamp={}", | ||
| self.processors.len(), | ||
| run_start_time.to_rfc3339() |
There was a problem hiding this comment.
hmm the logging layer should automatically add timestamps
Add structured monitoring to migration controller, so we can track state of migration
Added thorough structured monitoring to the migration controller so we can build Datadog dashboards to track the overall status of migrations, including the number of failed migrations, which are failing/succeeding, how long each migration takes etc.
Bedrock implements a foreign logger (a pattern used throughout Bedrock) with the
log()trait exported via UniFFI. The higher level calling app attaches the userId identifying information to the logs, so they can be identified in Datadog.Specifically:
log::info/warn/errorcalls with structuredcrate::info/warn/error key=valuelogging for Datadog dashboard compatibility.duration_msto all execution outcomes - failed, successful etc.