You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To better understand how often the review checklists are being used, we should track the download of JSON files in detail. These metrics can be used to detect trends in usage, which is valuable feedback.
We'd like to know:
How many times did each JSON file get imported into the worksheet per month?
Are there any increases month over month in requests for landing zone, security, avd, etc?
Are there any anomalies in JSON file requests or increases in static XLSX file requests that indicate a problem with the macros?
A few ways we might do this...
Update the GH actions workflow to publish new release versions of the JSON files with every merge to main. The release tracking / insights in GH would provide tracking. This is not ideal because it would require a new release to be published (automating multiple steps) with EVERY merge to main.
On merge, publish the JSON files to blob storage with metrics logged. We could then build monitoring workbooks on the data.
Build custom telemetry calls into the VBA code to call a logging API when a JSON file is being imported.
My instinct is that option 2 is the right path forward. In all 3 cases, the macros would need to be updated in some way to account for tracking the download of JSON files.
The text was updated successfully, but these errors were encountered:
Thanks for this @sdolgin ! If you create a Github action that copies the JSON files to a storage account, I can update the spreadsheet to support downloading from the storage account. Would you need any help with the Github action?
To better understand how often the review checklists are being used, we should track the download of JSON files in detail. These metrics can be used to detect trends in usage, which is valuable feedback.
We'd like to know:
A few ways we might do this...
Update the GH actions workflow to publish new release versions of the JSON files with every merge to main. The release tracking / insights in GH would provide tracking. This is not ideal because it would require a new release to be published (automating multiple steps) with EVERY merge to main.
On merge, publish the JSON files to blob storage with metrics logged. We could then build monitoring workbooks on the data.
Build custom telemetry calls into the VBA code to call a logging API when a JSON file is being imported.
My instinct is that option 2 is the right path forward. In all 3 cases, the macros would need to be updated in some way to account for tracking the download of JSON files.
The text was updated successfully, but these errors were encountered: