NOISSUE - Add blog post: How to Save JSON Messages in Magistrala - #175
Open
ianmuchyri wants to merge 2 commits into
Open
NOISSUE - Add blog post: How to Save JSON Messages in Magistrala#175ianmuchyri wants to merge 2 commits into
ianmuchyri wants to merge 2 commits into
Conversation
Tutorial covering the Rules Engine's new Internal DB (JSON) output: wiring it into a rule, what it does differently from the SenML output, why a JSON-capable writer must also be deployed for messages to actually persist, and verifying a saved message shows up in a JSON-format Message View. Signed-off-by: ianmuchyri <ianmuchiri8@gmail.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
absmach-website | 512f9f4 | Commit Preview URL Branch Preview URL |
Aug 05 2026, 10:26 AM |
- coverImage/ogImage plus in-context screenshots for the Add Output dialog, completed rule canvas, populated JSON Message View, and the JSON payload viewer - all captured against a real deployment now that the writer-deployment gap (magistrala-ee#12) is fixed. Closes the known gap called out in the PR description. - mosquitto_pub example used channels/<channel-id>/messages with cert-only auth, neither of which matches how Magistrala actually expects a client to publish. Corrected to m/<domain_id>/c/<channel_id> with client id/secret auth, matching every other mosquitto_pub example in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
src/content/blogs/how-to-save-json-messages-magistrala.md,category: tutorial, modeled on the existing Custom Nodes tutorial's structure (Prerequisites -> walkthrough -> Verification -> Troubleshooting -> Next steps).json-table routing), the writer-deployment prerequisite, and verifying a saved message shows up in a JSON-format Message View.mosquitto_pubverification example, which used a topic format and auth method that don't match how Magistrala actually expects a client to publish.Test plan
pnpm run build- full Astro build succeeds, post renders at/blog/how-to-save-json-messages-magistrala/with all four images resolvingprettier --checkpasses on the changed file