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
It seems that the APPSIGNAL_APP_ENV environment variable doesn't have the effect it's supposed to (as per the other integrations). Our staging environment runs with NODE_ENV set to production, which is fairly common. On our Ruby services we use APPSIGNAL_APP_ENV to set it to the right thing. This doesn't work in the Node integration.
Looking through the code, it seems that the APPSIGNAL_APP_ENV environment variable is mapped through to env on the options, but this isn't actually ever used -- elsewhere, NODE_ENV is used, defaulting to development.
The text was updated successfully, but these errors were encountered:
While performing the daily checks some issues were found with this issue.
This issue has not had any activity in 14 days. Please provide a status update if it is still relevant. Closed it if it is no longer relevant. Or move it to another column if it's blocked or requires another look at it. - (More info)
It seems that the
APPSIGNAL_APP_ENV
environment variable doesn't have the effect it's supposed to (as per the other integrations). Our staging environment runs withNODE_ENV
set toproduction
, which is fairly common. On our Ruby services we useAPPSIGNAL_APP_ENV
to set it to the right thing. This doesn't work in the Node integration.Looking through the code, it seems that the
APPSIGNAL_APP_ENV
environment variable is mapped through toenv
on the options, but this isn't actually ever used -- elsewhere,NODE_ENV
is used, defaulting todevelopment
.The text was updated successfully, but these errors were encountered: