-
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
[Alerting & Actions ] More debug logging #85149
Conversation
…ing/debug-logging
|
||
generateNewAndRecoveredInstanceEvents({ | ||
eventLogger, | ||
originalAlertInstances, | ||
currentAlertInstances: instancesWithScheduledActions, | ||
recoveredAlertInstances, |
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.
Changed based on suggestion from previous PR: #84670 (comment)
@@ -333,12 +356,15 @@ export class TaskRunner { | |||
schedule: taskSchedule, | |||
} = this.taskInstance; | |||
|
|||
const runDate = new Date().toISOString(); | |||
this.logger.debug(`executing alert ${this.alertType.id}:${alertId} at ${runDate}`); |
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.
Question from previous PR:
Was the runDate added to match the Kibana logs with the event log data timestamp when debugging?
Yes, that was my intention
@@ -120,6 +120,8 @@ export class ActionExecutor { | |||
} | |||
|
|||
const actionLabel = `${actionTypeId}:${actionId}: ${name}`; | |||
logger.debug(`executing action ${actionLabel}`); |
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.
From previous PR:
With the logger prefixing all the logs with a timestamp, is there a reason for the extra at ${new Date().toISOString()} here?
Updated to remove timestamp from debug message
Discussed this comment #84670 (comment) from the previous PR offline and decided that this will not be included in this PR. @mikecote is there another issue for this already? should i make an issue? |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
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.
Changes LGTM! Few nits on the message to indicate scheduling instead of executing.
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.
LGTM w/Mike's suggestions
💚 Build SucceededMetrics [docs]Distributable file count
History
To update your PR or re-run it, just comment with: |
* Adding debug messages * Adding timestamp to action execution log * Jest tests * Merging in master * PR fixes * Cleanup * PR fixes Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Adding debug messages * Adding timestamp to action execution log * Jest tests * Merging in master * PR fixes * Cleanup * PR fixes Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…k-field-to-hot-phase * 'master' of github.com:elastic/kibana: (429 commits) simplify popover open state logic (elastic#85379) [Logs UI][Metrics UI] Move actions to the kibana header (elastic#84648) [Search Source] Do not pick scripted fields if * provided (elastic#85133) [Search] Session SO polling (elastic#84225) [Transform] Replace legacy elasticsearch client (elastic#84932) [Uptime]Refactor header and action menu (elastic#83779) Fix agg select external link (elastic#85380) [ILM] Show forcemerge in hot when rollover is searchable snapshot is enabled (elastic#85292) clear using keyboard (elastic#85042) [GS] add tag and dashboard suggestion results (elastic#85144) [ML] API integration tests - skip GetAnomaliesTableData Add ECS field for event.code. (elastic#85109) [Functional][TSVB] Wait for markdown textarea to be cleaned (elastic#85128) skip flaky suite (elastic#62060) skip flaky suite (elastic#85098) Bump highlight.js to v9.18.5 (elastic#84296) Add `server.publicBaseUrl` config (elastic#85075) [Alerting & Actions ] More debug logging (elastic#85149) [Security Solution][Case] Manual attach alert to a case (elastic#82996) Loosen UUID regex to accept uuidv1 or uuidv4 (elastic#85338) ... # Conflicts: # x-pack/plugins/index_lifecycle_management/__jest__/client_integration/edit_policy/edit_policy.helpers.tsx # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/phases/hot_phase/hot_phase.tsx # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/phases/shared_fields/index.ts # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/phases/warm_phase/warm_phase.tsx # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/edit_policy.tsx # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/i18n_texts.ts # x-pack/plugins/index_lifecycle_management/server/routes/api/policies/register_create_route.ts
Resolves #49401
Redo of this PR #84670 because I mucked that up with a bad merge from master.
Summary
Added debug logging for:
muteAll
mute
orthrottle
Verified that error logging for alert and action execution errors log any detailed messages that bubble up