Google IoT Core registry with additional telemetry topic and wildcard in subfolder?
I want to add telemetry topics to a registry and distribute telemetry streams to different pubsub topics. Since our MQTT topics on the devices use more than one subfolder, the registry's subfolder string does not match exactly to the pubsub topic.
For example, our device sends telemetry to the topic:
/devices/devId/events/pubsubTopicId/additionalInfo/evenMoreInfo
I'd wish the resulting pubsub messages to be placed in the topic /projects/projectId/topics/pubsubTopicId and to have the pubsub subfolder property like /additionalInfo/evenMoreInfo.
Instead currently, all messages are published in the registry's default pubsub topic.
So this question is more of a feature request to the google team to enable wildcards in the subfolderMatches property of registry's EventNotificationConfig. Than a positive match could be evaluted if the first subfolder after /devices/devId/events would match.
Thx for your answer!
google-cloud-iot
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
add a comment |
I want to add telemetry topics to a registry and distribute telemetry streams to different pubsub topics. Since our MQTT topics on the devices use more than one subfolder, the registry's subfolder string does not match exactly to the pubsub topic.
For example, our device sends telemetry to the topic:
/devices/devId/events/pubsubTopicId/additionalInfo/evenMoreInfo
I'd wish the resulting pubsub messages to be placed in the topic /projects/projectId/topics/pubsubTopicId and to have the pubsub subfolder property like /additionalInfo/evenMoreInfo.
Instead currently, all messages are published in the registry's default pubsub topic.
So this question is more of a feature request to the google team to enable wildcards in the subfolderMatches property of registry's EventNotificationConfig. Than a positive match could be evaluted if the first subfolder after /devices/devId/events would match.
Thx for your answer!
google-cloud-iot
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
add a comment |
I want to add telemetry topics to a registry and distribute telemetry streams to different pubsub topics. Since our MQTT topics on the devices use more than one subfolder, the registry's subfolder string does not match exactly to the pubsub topic.
For example, our device sends telemetry to the topic:
/devices/devId/events/pubsubTopicId/additionalInfo/evenMoreInfo
I'd wish the resulting pubsub messages to be placed in the topic /projects/projectId/topics/pubsubTopicId and to have the pubsub subfolder property like /additionalInfo/evenMoreInfo.
Instead currently, all messages are published in the registry's default pubsub topic.
So this question is more of a feature request to the google team to enable wildcards in the subfolderMatches property of registry's EventNotificationConfig. Than a positive match could be evaluted if the first subfolder after /devices/devId/events would match.
Thx for your answer!
google-cloud-iot
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
I want to add telemetry topics to a registry and distribute telemetry streams to different pubsub topics. Since our MQTT topics on the devices use more than one subfolder, the registry's subfolder string does not match exactly to the pubsub topic.
For example, our device sends telemetry to the topic:
/devices/devId/events/pubsubTopicId/additionalInfo/evenMoreInfo
I'd wish the resulting pubsub messages to be placed in the topic /projects/projectId/topics/pubsubTopicId and to have the pubsub subfolder property like /additionalInfo/evenMoreInfo.
Instead currently, all messages are published in the registry's default pubsub topic.
So this question is more of a feature request to the google team to enable wildcards in the subfolderMatches property of registry's EventNotificationConfig. Than a positive match could be evaluted if the first subfolder after /devices/devId/events would match.
Thx for your answer!
google-cloud-iot
google-cloud-iot
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
asked Nov 24 '18 at 13:03
Matthias RombachMatthias Rombach
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I hear the feature request, and I can bring that to our engineering team.
As a possible solution for now...what if you set up something where the telemetry always goes to the /devices/devId/events/pubsubTopicId/ folder. And then inside the telemetry payload, you had subfolders where you wanted things going in addition to that, and you ran a cloud function, or a dataflow pipeline to parse the payload, and send the telemetry to the appropriate bucket?
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
add a comment |
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%2f53458415%2fgoogle-iot-core-registry-with-additional-telemetry-topic-and-wildcard-in-subfold%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I hear the feature request, and I can bring that to our engineering team.
As a possible solution for now...what if you set up something where the telemetry always goes to the /devices/devId/events/pubsubTopicId/ folder. And then inside the telemetry payload, you had subfolders where you wanted things going in addition to that, and you ran a cloud function, or a dataflow pipeline to parse the payload, and send the telemetry to the appropriate bucket?
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
add a comment |
I hear the feature request, and I can bring that to our engineering team.
As a possible solution for now...what if you set up something where the telemetry always goes to the /devices/devId/events/pubsubTopicId/ folder. And then inside the telemetry payload, you had subfolders where you wanted things going in addition to that, and you ran a cloud function, or a dataflow pipeline to parse the payload, and send the telemetry to the appropriate bucket?
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
add a comment |
I hear the feature request, and I can bring that to our engineering team.
As a possible solution for now...what if you set up something where the telemetry always goes to the /devices/devId/events/pubsubTopicId/ folder. And then inside the telemetry payload, you had subfolders where you wanted things going in addition to that, and you ran a cloud function, or a dataflow pipeline to parse the payload, and send the telemetry to the appropriate bucket?
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
I hear the feature request, and I can bring that to our engineering team.
As a possible solution for now...what if you set up something where the telemetry always goes to the /devices/devId/events/pubsubTopicId/ folder. And then inside the telemetry payload, you had subfolders where you wanted things going in addition to that, and you ran a cloud function, or a dataflow pipeline to parse the payload, and send the telemetry to the appropriate bucket?
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
answered Nov 26 '18 at 18:26
GabeWeissGabeWeiss
86168
86168
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
add a comment |
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Thank you for communicating that to the engineers. We'll probably only use the registry's default telemetry topic for now.
– Matthias Rombach
Nov 28 '18 at 6:50
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
Sounds good, if you have more questions, feel free to reach out on Twitter (easier to get ahold of me than SO generally).
– GabeWeiss
Nov 28 '18 at 20:43
add a comment |
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.
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%2f53458415%2fgoogle-iot-core-registry-with-additional-telemetry-topic-and-wildcard-in-subfold%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
