-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Synthetics] Standardize the uses of MONITOR_QUERY_ID and CONFIG_ID throughout the app #144176
[Synthetics] Standardize the uses of MONITOR_QUERY_ID and CONFIG_ID throughout the app #144176
Conversation
…-ref HEAD~1..HEAD --fix'
…hub.com/dominiqueclarke/kibana into feature/synthetics-monitor-id-migration
…hub.com/dominiqueclarke/kibana into feature/synthetics-monitor-id-migration
…ics-monitor-id-migration
30b6411
to
53c1d9e
Compare
…ics-monitor-id-migration
…ics-monitor-id-hook
Pinging @elastic/uptime (Team:uptime) |
const monitorId = useMonitorQueryId(); | ||
|
||
if (!monitorId) { | ||
return null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be a loading here? or maybe monitorId should be passed from parent component and there we can a central loading.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What loader do you think we should have, since most of these are exploratory view visualizations.
@@ -75,7 +75,6 @@ export const fetchSyntheticsMonitor = async ({ | |||
|
|||
return { | |||
...savedObject.attributes, | |||
id: savedObject.id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was removed in favor of MONITOR_QUERY_ID
, which is on the attributes. Now, there's no longer an id
field on the front end that is the monitor saved object id. Instead, we rely on CONFIG_ID
for that value.
…ics-monitor-id-hook
…ics-monitor-id-hook
...thetics/public/apps/synthetics/components/monitor_details/monitor_summary/duration_trend.tsx
Outdated
Show resolved
Hide resolved
…nitor_details/monitor_summary/duration_trend.tsx
…-ref HEAD~1..HEAD --fix'
💚 Build Succeeded
Metrics [docs]Async chunks
Unknown metric groupsESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
…hroughout the app (elastic#144176) Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: shahzad31 <shahzad.muhammad@elastic.co> Co-authored-by: Shahzad <shahzad31comp@gmail.com> Resolves elastic#143309
Summary
Resolves #143309
Standardizes the uses of
ConfigKey.MONITOR_QUERY_ID
andCONFIG_KEY.CONFIG_ID
throughout the public app.Regression testing
This PR requires full manual regression testing for the Synthetics app.