Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TrackEvent no longer reporting Measurements #1318

Open
JCBauza opened this issue Apr 26, 2024 · 3 comments
Open

TrackEvent no longer reporting Measurements #1318

JCBauza opened this issue Apr 26, 2024 · 3 comments

Comments

@JCBauza
Copy link

JCBauza commented Apr 26, 2024

Hi,

If I do the following:

// Set up some properties and metrics:
var properties = {"name": "SomeRandomName"};
var metrics = {"MetricA": 10, "MetricB": 5};

// Send the event:
instanceClient.trackEvent({name: "TestEvent", properties: properties, measurements: metrics});

I can see the event with the correct name and properties... but the measurements/metrics I pass get completely dropped. My dashboards are coming back empty. Any ideas what changed?

@JacksonWeber
Copy link
Contributor

@JCBauza Thank you for reporting this issue. It'll be resolved by #1319. For now, using version 2.X SDK or recording related metrics separately should be valid solutions.

@JCBauza
Copy link
Author

JCBauza commented Apr 30, 2024

Thank you. Are those metrics going to be related to the event that sends them as before? I’m asking because the properties of the event in my case are used to filter those metrics, or more specifically, I use them as tags and on the graphs the values are grouped by those tags.

JacksonWeber added a commit to Azure/azure-sdk-for-js that referenced this issue May 1, 2024
…ting Logs (#29511)

### Packages impacted by this PR
@azure/monitor-opentelemetry-exporter

### Issues associated with this PR
microsoft/ApplicationInsights-node.js#1318

### Describe the problem that is addressed by this PR
Previously measurements passed from the Application Insights 3.X SDK
were not being populated on logs in the exporter. These should be
populated from the log body and exported to breeze.

### Are there test cases added in this PR? _(If not, why?)_
Yes, added a test case to ensure that when measurements exist in the log
body field, they're populated on the final envelope.

### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [x] Added a changelog (if necessary)
@JacksonWeber
Copy link
Contributor

@JCBauza Yes, that's correct. They should operate in the same way they have in the past and will be available upon the next release of the Azure Monitor Exporter in the PR mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants