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

[Mandiant] Connector does not show accurate progess, and ingests reports very slowly #2892

Open
damians-filigran opened this issue Nov 1, 2024 · 0 comments
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. filigran team use to identify PR from the Filigran team needs triage use to identify issue needing triage from Filigran Product team
Milestone

Comments

@damians-filigran
Copy link
Contributor

Description

When ingesting reports, for the first day's ingest, the connector shows 100% progress, but then continues to ingest and increase the total operations despite the job apparently being completed. This continues for 1hr so far, with the count going higher and higher, despite the job showing as complete.

Environment

  1. OS: SaaS
  2. OpenCTI version: 6.2.8
  3. OpenCTI client: Edge on MacOS
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Configure Mandiant connector
  2. Set start date from 2 months ago
  3. Click into connector status view
  4. Watch the completed job continue to build total count

Expected Output

Job should stay as In Progress until complete

Actual Output

Job apparently complete
image

Job even more complete
image

Additional information

In effect, this accompanies a very slow ingest of the report from the API, maybe 1 operation per second, for Reports specifically.

Screenshots (optional)

@damians-filigran damians-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Nov 1, 2024
@nino-filigran nino-filigran added filigran team use to identify PR from the Filigran team filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. labels Nov 5, 2024
@nino-filigran nino-filigran added this to the Bugs backlog milestone Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. filigran team use to identify PR from the Filigran team needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

2 participants