message body routing from non-SDK leaf devices
the docs say to route messages within Edge properly based on the content of the body of the message, you have to set the content-type and content-encoding system properties, as shown in the sample below that uses the SDK
// Encode message body using UTF-8
var messageBytes = Buffer.from(messageBody, "utf8");
var message = new Message(messageBytes);
// Set message body type and content encoding
message.contentEncoding = "utf-8";
message.contentType = "application/json";
However, for a client that does not use the SDK, and instead uses straight MQTT such as the Paho client (as in this example), how do you specify those system properties? the IoT Hub docs (not edge) say that you can add a property bag of properties to the topic, but that doesn't seem to work for Edge.
So how can I route messages within Edge, based on the body of the messages, from non-SDK leaf devices?
azure-iot-edge
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
add a comment |
the docs say to route messages within Edge properly based on the content of the body of the message, you have to set the content-type and content-encoding system properties, as shown in the sample below that uses the SDK
// Encode message body using UTF-8
var messageBytes = Buffer.from(messageBody, "utf8");
var message = new Message(messageBytes);
// Set message body type and content encoding
message.contentEncoding = "utf-8";
message.contentType = "application/json";
However, for a client that does not use the SDK, and instead uses straight MQTT such as the Paho client (as in this example), how do you specify those system properties? the IoT Hub docs (not edge) say that you can add a property bag of properties to the topic, but that doesn't seem to work for Edge.
So how can I route messages within Edge, based on the body of the messages, from non-SDK leaf devices?
azure-iot-edge
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
add a comment |
the docs say to route messages within Edge properly based on the content of the body of the message, you have to set the content-type and content-encoding system properties, as shown in the sample below that uses the SDK
// Encode message body using UTF-8
var messageBytes = Buffer.from(messageBody, "utf8");
var message = new Message(messageBytes);
// Set message body type and content encoding
message.contentEncoding = "utf-8";
message.contentType = "application/json";
However, for a client that does not use the SDK, and instead uses straight MQTT such as the Paho client (as in this example), how do you specify those system properties? the IoT Hub docs (not edge) say that you can add a property bag of properties to the topic, but that doesn't seem to work for Edge.
So how can I route messages within Edge, based on the body of the messages, from non-SDK leaf devices?
azure-iot-edge
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
the docs say to route messages within Edge properly based on the content of the body of the message, you have to set the content-type and content-encoding system properties, as shown in the sample below that uses the SDK
// Encode message body using UTF-8
var messageBytes = Buffer.from(messageBody, "utf8");
var message = new Message(messageBytes);
// Set message body type and content encoding
message.contentEncoding = "utf-8";
message.contentType = "application/json";
However, for a client that does not use the SDK, and instead uses straight MQTT such as the Paho client (as in this example), how do you specify those system properties? the IoT Hub docs (not edge) say that you can add a property bag of properties to the topic, but that doesn't seem to work for Edge.
So how can I route messages within Edge, based on the body of the messages, from non-SDK leaf devices?
azure-iot-edge
azure-iot-edge
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
asked Nov 14 '18 at 3:12
Steve Busby - MSFT
636
636
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292668%2fmessage-body-routing-from-non-sdk-leaf-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292668%2fmessage-body-routing-from-non-sdk-leaf-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
