-
Notifications
You must be signed in to change notification settings - Fork 9
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
Diagnose function #24
Labels
Comments
✔️ All good! |
This comment has been minimized.
This comment has been minimized.
1 similar comment
While performing the daily checks some issues were found with this issue.
|
Merged
adamyeats
pushed a commit
that referenced
this issue
Sep 4, 2020
Closes #24. This adds the long-awaited diagnose CLI. In a new app, this can now be used by running `npx appsignal-diagnose` from your project directory after `@appsignal/nodejs` is installed. As `@appsignal/nodejs` doesn't use a config file, it relies on the correct environment variables being set at the time. If unset, you can use the command like this: `APPSIGNAL_PUSH_API_KEY="<key>" npx appsignal-diagnose`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was skipped in the initial implementation as the integration as the log output would always output an error even though the agent had started successfully.
The text was updated successfully, but these errors were encountered: