-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-------------------------------------------
Requirement from Marc Landry:
The team was looking to implement a solution to receive CDS based network script execution results into ELK so we can track what happens. The NSO ELK stack (for now) is our eyes into the performance of our entire stack. We are currently blind to what happens on CDS.
It would be very useful to have results available on a Kafka topic so that other microservice could leverage the messages (as well as ELK ingestion). There may also be a VES object that could be used for this purpose.
Is this something NSO could generically build for every user of CDS instead of asking network script writers and part of the CDS blue print is specifying which output topic for results are located?
-------------------------------------------
Internal business value to understand what's going on
Need to take care of sensitive data
Acceptance criteria * This feature will need to be approved by upstream community
- First implementation would be on a single topic since we are running a single instance of CDS.
- Nothing will be published in VES format
- Publish to Kafka bus message for both CDS input and output that can be correlated (in the same message or not as long as we can correlate them)
- A way exist to correlate input and output (create UUID?)
- There must be a way to hide sensitive data
- is blocked by
-
CCSDK-2370 Kafka Audit Service : CorrelationUUID from request is not matching the correct response in Kafka
- Closed