Azure-docs: Json shaping best practices: Multiple events at the same time - correalting values with tagId approach

[tymtam2]

In the first example there are 2 value pairs for device FXXX:

        "series": [
            {
                "Flow Rate ft3/s": 1.0172575712203979,
                "Engine Oil Pressure psi ": 34.7
            },
            {
                "Flow Rate ft3/s": 2.445906400680542,
                "Engine Oil Pressure psi ": 49.2
            }
        ]

1.[email protected] and 2.[email protected]

Using 2nd approach the correlation is lost.

"series": [
            {
                "tagId": "pumpRate",
                "value": 1.0172575712203979
            },
            {
                "tagId": "oilPressure",
                "value": 49.2
            },
            {
                "tagId": "pumpRate",
                "value": 2.445906400680542
            },
            {
                "tagId": "oilPressure",
                "value": 34.7
            }
        ]

It's not longer possible to match 1.01 with 34.7.

Would this have practical consequences when querying data?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3ddb99e3-d1bd-a593-8353-5fcfcbf6217c
• Version Independent ID: a00e09c7-4dcf-bd5d-d05a-d315fb6041b7
• Content: Best practices for shaping JSON - Azure Time Series Insights queries
• Content Source: articles/time-series-insights/how-to-shape-query-json.md
• Service: time-series-insights
• GitHub Login: @deepakpalled
• Microsoft Alias: dpalled

[AshokPeddakotla-MSFT]

@tymtam2 Thanks for the feedback! We are currently investigating and will update you shortly.

[AshokPeddakotla-MSFT]

Adding @lyrana to help with this query.

[lyrana]

This page will be removed to reduce confusion with Gen2, will update PR status here

[lyrana]

PR merged, #please-close