Skip to content
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

Chore: Use ruleId instead of alertId as log keyword #18738

Merged
merged 1 commit into from Aug 27, 2019
Merged

Conversation

marefr
Copy link
Member

@marefr marefr commented Aug 26, 2019

What this PR does / why we need it:
Use the in-memory representation of alert identifier, ruleId, instead of the database one, alertId, as keyword when logging.

Which issue(s) this PR fixes:
Fixes #18688

Special notes for your reviewer:

@marefr marefr requested a review from kylebrandt August 26, 2019 20:30
@marefr marefr added this to Under review in Backend Platform Backlog via automation Aug 26, 2019
@torkelo torkelo merged commit e83f55f into master Aug 27, 2019
Backend Platform Backlog automation moved this from Under review to Done Aug 27, 2019
@torkelo torkelo deleted the 18688_fix branch August 27, 2019 06:40
@marefr marefr modified the milestones: 6.3.4, 6.4 Aug 27, 2019
ryantxu added a commit to ryantxu/grafana that referenced this pull request Aug 27, 2019
* grafana/master:
  DashboardDatasource: reuse query results within a dashboard (grafana#16660)
  Plugins: show a clear error on the plugin page when it failed to load (grafana#18733)
  Chore: Use ruleId instead of alertId as log keyword (grafana#18738)
ryantxu added a commit to ryantxu/grafana that referenced this pull request Aug 28, 2019
* grafana/master:
  Explore: Use PanelQueryState to handle querying (grafana#18694)
  Chore: Improve err message for notifications (grafana#18757)
  @grafana/toolkit: add package versions to the ci report (grafana#18751)
  @grafana/data: Matchers and Transforms (grafana#16756)
  Docs: Document LDAP config reload in admin http api (grafana#18739)
  center NoDataSourceCallToActionCard in Explore (grafana#18752)
  DataLinks: enable data links in Gauge, BarGauge and SingleStat2 panel (grafana#18605)
  DashboardDatasource: reuse query results within a dashboard (grafana#16660)
  Plugins: show a clear error on the plugin page when it failed to load (grafana#18733)
  Chore: Use ruleId instead of alertId as log keyword (grafana#18738)
  @grafana/data: improve the CircularVector api (grafana#18716)
  QueryEditor: check if optional func toggleEditorMode is provided (grafana#18705)
  Emails: remove the yarn.lock (grafana#18724)
  OAuth: Support JMES path lookup when retrieving user email (grafana#14683)
  Emails: resurrect template notification (grafana#18686)
  Email: add reply-to and direct attachment (grafana#18715)
  Dashboard: Adds Logs Panel (alpha) as visualization option for Dashboards (grafana#18641)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Key word in log messages differ in alerting.evalContext and alerting.resultHandler
3 participants