Incident Index data not coming

Overview

General/Customer specific	General
Author	Rukmini
Reviewer	Seema
Approver
Release date	03/09/2022
Product Version	9.1r3

Audience: CSG/TechWarriors/PAC/Platform/Product teams

What’s the Issue?  In BMCSL setup no incident index data.

Describe the Issue in Detail In BMCSL setup there is no incident index from last one week. Remedy data is indexing in incident index.

Solution Summary After restarting dao-vunode container issue got resolved.

Solution Steps in Detail As first step of flow of incident data we should check dao container service running or not. vsmaps status all all Check data in kafka input topic of incident data. /etc/kafka/bin/kafka-topics.sh --list --bootstrap-server localhost:9092 | grep incident /etc/kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092  --topic incidents If no data in kafka input topic we need to restart dao container. vsmaps restart dao all If data presence in input topic no need to restart dao, as next step we should check the pipeline configuration and is there data in output kafka topic and lag of kafka. /etc/kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092  --topic incidents-out If data present in kafka output topic. Step to check consumer group lag. /etc/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --all-groups --describe | grep incident /etc/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --group incidents_app –describe No Issue in lag now step to check es connector. curl BMCSLDCVUAN01:9082/connectors | jq curl BMCSLDCVUAN01:9082/connectors/remedy-es-sink/status | jq

Corrective actions if any to avoid in future No

More Help: 

References: