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
Here is an idea to make the ey-logentries recipe way more user-friendly.
Right now, we're stuck with hardcoded log paths, which is a pain for users who want to track custom logs.
What if we set up an environment variable called EY_LOGENTRIES_FOLLOW_PATHS? It'd work just like the EY_PACKAGES variable. This way, users could easily add their own log paths without having to mess with the recipe itself. Keep all the default logs that are already being tracked, but users could add in their own app-specific logs too.
The text was updated successfully, but these errors were encountered:
Here is an idea to make the ey-logentries recipe way more user-friendly.
Right now, we're stuck with hardcoded log paths, which is a pain for users who want to track custom logs.
What if we set up an environment variable called
EY_LOGENTRIES_FOLLOW_PATHS
? It'd work just like the EY_PACKAGES variable. This way, users could easily add their own log paths without having to mess with the recipe itself. Keep all the default logs that are already being tracked, but users could add in their own app-specific logs too.The text was updated successfully, but these errors were encountered: