Hi chris_itk, Thank you for commenting. You are correct, the initial
version of the data history feature historizes DTDL property updates
only. To historize DTDL telemetry in the interim, you could create an
event route to forward DTDL telemetry events to an event hub. You would
also need an Azure f...
Hi @ClairitEF - this doesn't seem to be related to this effort. I would
reach out to support. @yuvalom I'm not sure what you mean. That is a
symmetric key-based connection string, except the credential is fake.
All that needs to be tested is the TLS handshake. However, if you need
additional help, p...
Hey @RAMIoT @wduraesI would like to generate a SAS token equivalent to
the above connection string for testing the new CAHow can I get support
for this?Could not find a supporting page / linkRegards!
Hi,that's a nice out of the box solution for historizing adt data. Thank
you for your introduction to this. When I did my own experiments with
data history, I learned, that it only works with dtdl properties. dtdl
telemetries seem not to be supported. Can you recommend a way on how to
historize dtdl...
@Arty29 No you will not need a new hub. Your existing Hub will begin
serving a certificate that is rooted to the new root (DigiCert Global G2
Root) after the migration. @rameshkhot The new root will be DigiCert
Global G2, after which Microsoft may decide to migration to a native
MSFT root as mention...
Latest Comments