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
graylog not log!
i am using graylog2 in several projects. nodeJS and meteorJS
but seems that some logs are missed!!
after a lot of headache we figured out exactly what was the problem.
in json object that we sent as detailes, we used with keywords from graylog for field names.
graylog don't log them! and not raised any error or warning!!!
it's crazy! how the developer can found this problem? and how he can know from which keywords he need to avoid??
for example: 'error', 'host' are keyword .
so if you write:
catch(ex){
logger.error("error in registration", "an exception raised through registration process", {error: ex})
}
nothing log!!!
but if :
logger.error("error in registration", "an exception raised through registration process", {err: ex})
all it's ok!!!!
The text was updated successfully, but these errors were encountered:
Looking through the code I don't see anything that suggests what the problem is; could this be a problem with Graylog? Is there anything in Graylog's logs that gives any hints?
Cheers,
Erwin
gVolop
changed the title
graylog not log if you are using with aome keywords
graylog not log if you are using with some keywords
Aug 4, 2016
graylog not log!
i am using graylog2 in several projects. nodeJS and meteorJS
but seems that some logs are missed!!
after a lot of headache we figured out exactly what was the problem.
in json object that we sent as detailes, we used with keywords from graylog for field names.
graylog don't log them! and not raised any error or warning!!!
it's crazy! how the developer can found this problem? and how he can know from which keywords he need to avoid??
for example: 'error', 'host' are keyword .
so if you write:
nothing log!!!
but if :
all it's ok!!!!
The text was updated successfully, but these errors were encountered: