-
Notifications
You must be signed in to change notification settings - Fork 450
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
FunctionAppLogs from Diagnostic settings have different format at "properties" field by OS/SKU #7864
Comments
Thank you for your feedback! We will check for the possibilities internally and update you with the findings. |
Hi @pragnagopa , Could you please look into this? |
Thanks for reporting the issue. Tagging @CooperLink for initial investigation. |
As an FYI, it looks like this is occurring for Linux Dedicated as well, i.e. key-value pairs in the object under |
Hi @pragnagopa, @CooperLink |
Adding notes from ICM - 356696604 Linux Elastic Premium: Data time in US format This will be addressed as of breaking changes for Functions Runtime V5. No ETA yet. |
We are taking closer look into this - specifically to check if we can expose an opt-in flag for Cx to choose US format vs ISO 8601 format. |
Thanks for confirming this! Is there an update on the ETA for runtime v5? |
+1, also curious if there is an ETA |
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
All OS and SKU should have same format.
Actual behavior
■Linux Elastic Premium
"properties" is quoted with "(double quote),
key-values in stringifyed object are quoted with '(single quote)
■Linux Consumption
"properties" is not quoted, key-value in object are quoted with '(single quote)
Single quotation in json object is invalid
■Windows Elastic Premium
"properties" is not quoted, key-value in object are quoted with "(double quote)
This format is totally valid json
■Windows Consumption
"properties" is not quoted, key-value in object are quoted with "(double quote)
This format is totally valid json
This format is as same as Windows Elastic Premium
Known workarounds
N/A
Related information
Provide any related information
The text was updated successfully, but these errors were encountered: