Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
02-21-2019 02:03 PM
Two part question.
1. What environment variables get logged by the AppDynamics NodeJs agent by default? We can see that the Java agent logs all JVM variables, but we are not able to see any environment variables being logged by the NodeJs agent.
2. If environment variables were getting logged and we wanted to mask them, what is the correct matchPattern to use?
We can see configuration outlined here:
https://docs.appdynamics.com/display/PRO45/Node.js+Settings+Reference
// Add an environment variable filter dataFilters: [{ "appliesTo": "env-vars", "matchPattern": "password|key" }],
But it's not clear from that example what kind of "match" this is. Is it an exact match? Is it a "contains" type match? Can you use wildcards such as "*"?
03-19-2019 02:53 PM - edited 03-19-2019 02:54 PM
Hi @Jim.Moody
Thank you for posting your question on the AppDynamics community.
Our documentation team has appreciated the feedback and they went ahead and updated the documentation on environment variables and match patterns.
According to the documentation, the matchpattern/parampattern is a standard regex.
Hope the updated doc helps clarify your question.
Let us know if you have further queries.
03-20-2019 01:23 AM
Hi Jim,
Appreciate your patience, So in early days of nodejs agent, We used to wire all the Env variables to the controller. But for now, data filtering is by default adopted for Env variables in Nodejs agent (we are no more propagating all the Env variables )
Also, Thanks to your valuable feedback. We have updated the doc. The matchpattern/parampattern is a standard regex.
Please let us know if you have any concerns.
Regards!
Arun G
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form