Schema at Microsoft.Insights/components/analyticsItems@2015-05-01 is impossible

[Willem-J-an]

Schema at Microsoft.Insights/components/analyticsItems@2015-05-01 is impossible

[alex-frankel]

There was an internal discussion about it, but it did not end up producing anything meaningful. I just asked for an update.

[Willem-J-an]

You should be able to use the mentioned ARM payload in an az rest command.

[alex-frankel]

I'm having trouble following the exact issue. Can you share the full bicep file? This looks like a partial snippet atm.

A working payload would look like this:

When you say working payload, is that the REST API payload? Where is that coming from?

[Willem-J-an]

Ah I was missing some details indeed. I have updated the issue to include the parent resource and the ARM template this compiles to.

Working payload is indeed for the REST API, as it is used in the Azure Portal. It also works to add items when they do not exist yet. When the item does exist, the REST API requires an additional property to be set on the body, [ Id ], with the Id of the existing item. Additionally a query parameter must be set overrideItem=true. Not sure if those things are handled through an ARM template, and cannot test because the deploy command does not get that far.

[alex-frankel]

Something seems really off here. I've never seen a top level property content before..

It also does not make sense to have two name properties. The name is going to map to a specific segment in the resource ID, so it is not possible to have two name properties. I wonder if these are actually supposed to be inside of the properties object.

I'm going to reach out to the microsoft.insights team to see if they can take a look.

cc @anthony-c-martin who might be able to take a closer look at the swagger definition.

[benclerix-cegeka]

Hi,
Is there any update on this?

[radxhunter]

@alex-frankel any update on this?

[alex-frankel]

No update. The best path forward will be to open a support ticket. We have made efforts to get the Insights team to work on it, but it is not being prioritized.

[triplebeta]

Same problem here, using latest version of az and bicep.
resource myFunction 'microsoft.insights/components/analyticsItems@2015-05-01' = { name: 'item' // must be set to item Name: 'Foo' // There is another Name property (?) with uppercase? parent: azAppInsights Scope: 'user' Id: 'b401c7de-0c50-4c07-91c4-e975694fdd32' Content: loadTextContent('some_function.kql') // throws the error Properties: { functionAlias: 'some_function' } }
That show the following error
{"code": "InvalidRequestContent", "message": "The request content was invalid and could not be deserialized: 'Could not find member 'Content' on object of type 'TemplateResource'. Path 'properties.template.resources[0].Content', line 21, position 16.'."}

[electroma]

I'm having the same issue. Were you able to find any workaround to deploy functions using ARM or AZ CLI calls?
In the meantime I have created a support case and crosslinked this issue there.

[electroma]

In case somebody else will hit this issue, there is a workaround: for log analytics workspace-based AppInsights instances, you can switch to Log Analytics functions, which have proper Bicep support and can accept parameters as well.