[
https://issues.apache.org/jira/browse/METRON-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629201#comment-16629201
]
ASF GitHub Bot commented on METRON-1794:
----------------------------------------
GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/1212
METRON-1794 Include User Details When Escalating Alerts
When an alert is escalated in the Alerts UI, the escalation should be
attributable to a user. This PR ensures that an escalation can be attributed
to the user who initiated the escalation.
## Changes
When an alert is escalated, the alert is serialized and pushed to the
escalation topic in Kafka. The username and a timestamp should be appended to
this escalation message.
* `metron_escalation_user`: The name of the user who escalated the alert.
* `metron_escalation_timestamp`: A timestamp in epoch milliseconds
indicating when the alert was escalated.
This does not change the alert stored in the Indexer; Elasticsearch or Solr.
This adds some logging around alert escalation.
## Testing
TODO
## Pull Request Checklist
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
- [ ] Have you written or updated unit tests and or integration tests to
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1794
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/1212.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1212
----
commit ba84df73384c374dd4ea086d61110ef4658c557f
Author: Nick Allen <nick@...>
Date: 2018-09-26T17:43:14Z
METRON-1794 Include User Details When Escalating Alerts
----
> Include User Details When Escalating Alerts
> -------------------------------------------
>
> Key: METRON-1794
> URL: https://issues.apache.org/jira/browse/METRON-1794
> Project: Metron
> Issue Type: Improvement
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> When an alert is escalated in the Alerts UI, the escalation should be
> attributable to a user. The username and a timestamp should be appended to
> the escalation message that is pushed to the escalation topic in Kafka.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
