Skip to content

Commit 308df22

Browse files
committed
04-cleanup-complete
1 parent e024dea commit 308df22

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

modules/use-cases-architectures/pages/real-time-data-pipeline/04-debugging-and-clean-up.adoc

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,17 @@ This guide is part of a series that creates a real-time data pipeline with Astra
1313

1414
== Debugging the pipeline
1515

16-
Maybe things didn’t go so smoothly for you. Or maybe you're just having a bad day :(. Whatever the case use the flow above to find where in the pipeline things are broken. Then get a bit deeper into that object. You’ll want to test input data at the point of failure. The first question to answer is if the input data is malformed or if the object itself is erring. Decodable’s UI gives you the ability in each pipeline to “Preview” the processing. This is a very powerful debugging tool. Your Astra Tenant has the “Try Me” area where you can set up producing and consuming messages in specific topics. These tools can help you recreate each step of the pipeline and debug issues.
16+
Maybe things didn’t go so smoothly for you. Or maybe you're just having a bad day :(. Whatever the case, we can fix this!
17+
18+
Follow the data flows described in xref:real-time-data-pipeline/03-put-it-all-together.adoc#following-the-flow[Step 3] to find where in the pipeline things are broken. Decodable is a great visualization tool for this, because you can click through the connections, streams, and pipelines and actually *see* where connections are failing. For example, if you accidentally named a stream "click-stream" instead of "clicks-stream", you can follow the click event to the outbound "clicks-stream" and then to the pipeline, and see that the pipeline is not receiving the message because its inbound stream is misnamed "click-stream". Stop the pipeline, choose the correct stream, and restart the pipeline to get data flowing again.
19+
20+
Test input data at the point of failure. The first question to ask is if the input data is malformed, or if the object itself is failing. Decodable’s UI gives you the ability to “Preview” the processing in each pipeline. This is a very powerful debugging tool. Additionally, your Astra Tenant has the “Try Me” area where you can produce and consume messages in specific topics, which is great for testing purposes.
21+
These tools can help you recreate each step of the pipeline and debug issues.
1722

1823
== Clean up
1924

2025
=== Removing Decodable objects
2126

22-
2327
. For each "Connection" click the 3 dots and choose "Stop".
2428
+
2529
image:decodable-data-pipeline/04/image1.png["Stop decodable connection"]
@@ -43,8 +47,9 @@ image:decodable-data-pipeline/04/image3.png["Delete Astra tenant"]
4347
+
4448
image:decodable-data-pipeline/04/image4.png["Terminate Astra database"]
4549

46-
You have removed all objects and are ready to start fresh! Your next processing pipeline can solve a business challenge like fraud detection or removing personally identifiable information, or maybe how to get to the moon! Have fun!
50+
You have now removed all objects and are ready to start fresh!
51+
Your next processing pipeline can solve a business challenge like fraud detection, or removing personally identifiable information (PII), or maybe how to get to the moon! Have fun!
4752

4853
== Next step
4954

50-
Head back to the xref:real-time-data-pipeline/index.adoc[guide home]
55+
Return to the xref:real-time-data-pipeline/index.adoc[guide home].

0 commit comments

Comments
 (0)