Expected property 'targetProperty' is missing from event metadata
See original GitHub issueI have got a sample/simple repo at https://github.com/ysmoradi/AppInsightsSdkWithoutAzureAccount/tree/elastic
HealthCheck:
2020-05-11 20:12:36Z,Microsoft.Diagnostics.EventFlow.Output,Error,ElasticSearchOutput: Expected property 'targetProperty' is missing from event metadata
StdOutput is working fine, but the elastic output is not working properly.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
EventTrigger Not Working When Declared in Window. ...
Hey Clement, as @AnatoliyNikolaev says, all you need to do to make your 'broken' example work is to remove the Storyboard.TargetName property ......
Read more >Custom dependency properties - UWP applications
Explains how to define and implement custom dependency properties for a Windows Runtime app using C++, C#, or Visual Basic.
Read more >Property binding best practices
As a best practice, use only properties and methods that return values. Return the proper typelink. A template expression should result in the...
Read more >TypeScript errors and how to fix them
Set the “target” property in your “tsconfig.json” file to “es5” or higher: tsconfig.json ... const lastName = throw new Error('Missing last name'); ...
Read more >Analytics API Reference
Return the number of events with unique values, for a target property in a collection matching given criteria. A common use for this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ApplicationInsights input version 1.5.1 has been published to nuget.org. Thanks @ysmoradi for bringing this to our attention and for a great repro.
@ysmoradi just a couple of remarks while I am working on the fix
You can work around the issue by setting the target on the dependency telemetry. i.e. after this line add something like
Also, just FYI, you can also filter events before they get to any output, for example (
eventFlowConfig.json
file):