TheHive-Project / TheHive-Project/Cortex

[BUG] Analyzers and Responders not loading in Cortex 3.1.0-RC-1

Open
#325 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.6k
Forks
264
PR merge metrics
No merged PRs in 30d

Description

Request Type

Bug

Work Environment
Question Answer
OS version (server) Ubuntu 20.04
Cortex version / git hash 3.1.0-RC-1
Package Type Binary
Problem Description

After modifying the application.conf file and restarting the service analyzers and responders are not available via the GUI.

Steps to Reproduce

Downloaded the Analyzers and Responders.
Modified the application.conf
Restarted the service

Complementary information## ANALYZERS

Here is the section I'm modifying

analyzer {

analyzer location

path = ["/opt/Cortex-Analyzers/analyzers/"]

url can be point to:

- directory where analyzers are installed

- json file containing the list of analyzer descriptions

urls = ["https://dl.bintray.com/thehive-project/cortexneurons/analyzers.json"]

Sane defaults. Do not change unless you know what you are doing.

fork-join-executor {
# Min number of threads available for analysis.
parallelism-min = 2
# Parallelism (threads) ... ceil(available processors * factor).
parallelism-factor = 2.0
# Max number of threads available for analysis.
parallelism-max = 4
}
}

RESPONDERS

responder {

responder location (same format as analyzer.urls)

path = ["/opt/Cortex-Analyzers/responders/"]
urls = ["https://dl.bintray.com/thehive-project/cortexneurons/reponders.json"]

Sane defaults. Do not change unless you know what you are doing.

fork-join-executor {
# Min number of threads available for analysis.
parallelism-min = 2
# Parallelism (threads) ... ceil(available processors * factor).
parallelism-factor = 2.0
# Max number of threads available for analysis.
parallelism-max = 4
}
}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with application.conf and the analyzer/responder loading path, then check the service logs after restarting with the shown paths and URLs. Done means the downloaded analyzers and responders load successfully and appear in the GUI.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.