Skip to content

Commit 57fd2a3

Browse files
committed
fix: handle case when Elasticsearch index does not exist in alerts fetching
1 parent f077fee commit 57fd2a3

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

backend/src/main/java/com/park/utmstack/service/threat_management/AdversaryAlertsService.java

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,11 @@ public class AdversaryAlertsService {
2727
private final ElasticsearchService elasticsearchService;
2828

2929
public List<AdversaryAlertsResponseDto> fetchAdversaryAlerts(List<FilterType> filters){
30+
31+
if(!elasticsearchService.indexExist(V11_ALERTS_INDEX_PATTERN)) {
32+
return Collections.emptyList();
33+
}
34+
3035
SearchRequest request = SearchRequest.of(s -> s
3136
.index(V11_ALERTS_INDEX_PATTERN)
3237
.query(SearchUtil.toQuery(filters))

backend/src/main/java/com/park/utmstack/web/rest/threat_management/AdversaryAlertsResource.java

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ public class AdversaryAlertsResource {
2424

2525
@PostMapping("/alerts")
2626
public ResponseEntity<List<AdversaryAlertsResponseDto>> search(@RequestBody(required = false) List<FilterType> filters) {
27+
2728
List<AdversaryAlertsResponseDto> responseDto = adversaryAlertsService.fetchAdversaryAlerts(filters);
2829

2930
if (responseDto.isEmpty())

0 commit comments

Comments
 (0)