The telemetry code was creating a singleton base telemetry event the first time that telemetry was being sent. That base event included the date. If a PowerShell session lasted multiple days, the telemetry reporting would eventually start to fail because the date being reported for the event was too old.
We now just create a new telemetry event every time one is requested (this also ensures that it honors changes to the ApplicationInsightsKey), and now we only cache a GUID that we use to represent the "session" ID which we consider to be the duration of the current PowerShell session.
Issues Fixed
None
Checklist
[x] You actually ran the code that you just wrote, especially if you did just "one last quick change".
[x] ~Comment-based help added/updated, including examples.~
[x] ~Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.~
[x] ~Relevant usage examples have been added/updated in USAGE.md.~
Description
The telemetry code was creating a singleton base telemetry event the first time that telemetry was being sent. That base event included the date. If a PowerShell session lasted multiple days, the telemetry reporting would eventually start to fail because the date being reported for the event was too old.
We now just create a new telemetry event every time one is requested (this also ensures that it honors changes to the
ApplicationInsightsKey), and now we only cache a GUID that we use to represent the "session" ID which we consider to be the duration of the current PowerShell session.Issues Fixed
None
Checklist