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

Responder run displayed as Analyzer run #207

Closed
ITServ-DE opened this issue Jul 3, 2019 · 0 comments
Closed

Responder run displayed as Analyzer run #207

ITServ-DE opened this issue Jul 3, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@ITServ-DE
Copy link

Request Type

Enhancement

Work Environment

Question Answer
OS version (server) Ubuntu
OS version (client) Win7
Cortex version / git hash 3.0.0-RC3
Package Type DEB

Problem Description

Total unimportant, but ...

In the job history, all job executions are listed as they were "Analyzers". Even those which are Responders, such as this example (SecurityIncident_1_0 is a responder)
ResponderAnalyzer

Steps to Reproduce

  1. run a responder
  2. check the cortex job history

Possible Solutions

In /www/src/app/pages/jobs/components/jobs.list.html, line 39: replace hardcoded

<strong>Analyzer:</strong>

with a dynamic value of the job type (analyzer/responder).

@ITServ-DE ITServ-DE changed the title Responder run logged as Analyzer run Responder run shown as Analyzer run Jul 3, 2019
@ITServ-DE ITServ-DE changed the title Responder run shown as Analyzer run Responder run displayed as Analyzer run Jul 3, 2019
@nadouani nadouani added this to the 3.0.0-RC4 milestone Jul 4, 2019
@nadouani nadouani closed this as completed Jul 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants