Feature request - Ability to define search order for misp.search function
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 491
- Forks
- 290
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Description
When running misp.search() and using relative timestamps for parameter such as published_timestamps='4h' or date_from='4h', it starts to fetch the oldest event first in my case it starts fetching events from 2022 and works towards 2026 which resulted in it fetching nearly 40,000 pages of 100 events each before starting to fetch the actual event which were within the filter range
Feature request: Ability to define search order (descending) as a parameter to the function in PyMISP to be able to use relative time frame search more effectively
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the PyMISP misp.search() implementation and trace how relative timestamps such as published_timestamps='4h' and date_from='4h' are passed to the MISP REST API. Add support for selecting descending search order, then verify that relative-time searches examine recent events first and avoid the reported excessive paging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100