Incident Index data not coming 353

Incident Index data not coming 353






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

  1. After restarting dao-vunode container issue got resolved.

Solution Steps in Detail

  1. As first step of flow of incident data we should check dao container service running or not.
  2. vsmaps status all all
  4. Check data in kafka input topic of incident data.
  5. /etc/kafka/bin/kafka-topics.sh --list --bootstrap-server localhost:9092 | grep incident
  7. /etc/kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092  --topic incidents
  9. If no data in kafka input topic we need to restart dao container.
  10. vsmaps restart dao all
  12. 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.
  13. /etc/kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092  --topic incidents-out
  15. If data present in kafka output topic. Step to check consumer group lag.
  16. /etc/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --all-groups --describe | grep incident
  18. /etc/kafka/bin/kafka-consumer-groups.sh --bootstrap-server localhost:9092 --group incidents_app –describe
  20. No Issue in lag now step to check es connector.
  21. curl BMCSLDCVUAN01:9082/connectors | jq
  23. curl BMCSLDCVUAN01:9082/connectors/remedy-es-sink/status | jq


Corrective actions if any to avoid in future

  1. No


More Help: 

References: 








    • Related Articles

    • Telegraf data was not coming 369

           Solution Document        Telegraf data was not coming           Overview General/Customer specific General Author Shreyash Soni Reviewer Seema Approver  Shreyash Soni Release date 07/07/2022 Product Version 8.X and 7.X               Audience: ...

    • Data retention settings- 452

      Solution Document Managing Data Retention Settings Overview General/Customer specific General Author Mantika Jadhav Reviewer Seema Approver  Ravi  Release date 19/07/2022 Product Version 8.5r5 Audience: CSG/TechWarriors/PAC/Platform/Product teams ...

    • unable to read data from ES having nested fields 505

       Solution Document ICICI || unable to read data from ES having nested fields   Overview General/Customer specific General Author Tejaswi Botla Reviewer NA Approver  NA  Release date 18/08/2022 Product Version 8.5r5 Audience: ...

    • Can we restore an archived index and close it and then again archive it?

      Question: I want to understand that can we restore an archived index and then close it and archive it again after using the information required? For example: We are keeping the data open for last 2 days for an index and archiving the older data than ...

    • [RBL] Issue With Data Indexing

      There is following issue with the RBL project.  We are monitoring ESB as an application in RBL. Currently, I am not able to see proper data getting indexed. Redis queue building up and dequeuing is also happening properly. There is no error in ES as ...