-
Notifications
You must be signed in to change notification settings - Fork 56
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
[Feature] Date/Time should be formatted human readable #478
[Feature] Date/Time should be formatted human readable #478
Comments
@NobleWolf I think here we'd probably want to do an environment variable so you can put in your own date/time format string... there's just too many people that are going to want it in a different way and I'm hesitant to change it to one way for everyone that's different than what it is already... we could also probably do a time zone offset via environment variable as well |
I like the idea of a date pattern. Shall it be as a hidden default param per module? Or at the solution level? I guess it's easier at the solution level but I feel that if the biggest driver not to hardcode it is the flexibility, the the module option makes sense. |
@piaudonn I'm thinking solution level, I can't imagine a scenario where you would want it different on a per module basis. And if it's an environment variable it's one place to configure it with no need to touch any of the logic apps |
I can imagine plenty :) I am good with the solution level tho |
Lol @piaudonn I'm curious what your ideas are. 🤣 @briandelmsft Solution level environment variable makes perfect sense for maintainability and simple setup. In my head it was going to be a drop-down or something, but using the Environment variable with a link in the wiki docs to a Microsoft doc or something that explains it like the KQL datetime function Supported Formats doc would be perfectly usable. |
Is your feature request related to a problem? Please describe.
Currently the date time in all modules is like 2025-01-03T15:45:00Z which is not easily readable by a person. It is difficult for an Analyst to consume and understand a table with dates formatted like this (especially when they word-wrap to a new line)
Describe the solution you'd like
All date times in all modules should present in a human readable format like:
2025-01-03 15:45:00 UTC
At minimum this allows more human-readable word wrapping
A better option would be to have a configurable option to allow a common formatting like:
January 1, 2025 15:45:00 UTC
Describe alternatives you've considered
Writing my own enrichment.
Additional context
None.
The text was updated successfully, but these errors were encountered: