Nagios Support Forum

I am not able to see complete logs of one API call on NLS. For API call some are logs are visible on NLS from some are not from same instance.

Regards,
Yaduraj Singh

Can you give an example of what you are doing and the results you are getting?

Let's assume, in a API call, 10 steps are executing. Sometimes I only get last 5 steps in NLS. First 5 are missing.

Regards,

What API calls are you making? Can you provide some screenshots so we can understand the problem better?

On server we are getting below logs.

info: finicityRequestId: FIN292309034
info: processMessageAndReply started for request id FIN292309034: {"requestType":"XXXXXXX","partnerId":"XXXXXXX","customerId":"XXXXXXX","institutionId":"XXXXXXX","keys":{"PIN":"*****","ID":"*****"}}
FIN292309034 browserConfig { args:
2019-03-25T13:00:26.406Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Request timeout type: normal, value: 600000.
2019-03-25T13:00:28.816Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Executed on IP address = XXXXXXX:XXXX
2019-03-25T13:00:28.816Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Started script Login
2019-03-25T13:00:35.322Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Accounts Page Reached
2019-03-25T13:00:35.322Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Completed script login, success: true, duration: 6506
2019-03-25T13:00:35.323Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - started discovery
2019-03-25T13:00:37.425Z - info: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - clearSessionTimeout: timer cleared.
2019-03-25T13:00:37.426Z - warn: FinicityRequestId: FIN292309034 Institution: XXXXXXX, Customer: XXXXXXX, RequestType: discovery, - Called clear session timeout for nonexisting timeout
info: processMessageAndReply completed for Request id FIN292309034 Institution Id: XXXXXXX, Partner Id: XXXXXXX. Duration=11373 Request: {"requestType":"DISCOVERY","partnerId":"XXXXXXX","customerId":"XXXXXXX","institutionId":"XXXXXXX","keys":{"PIN":"*****","ID":"*****"}}

But in NLS we are getting less logs. Please find the attachment.

Looks like a problem with parsing. Can you PM me a copy of the log as well as a copy of the logstash config? The logstash config can be gathered by going to Configure > Global (All Instances) > Global Config > View > All Files Combined.

Which input are these going to? How did you configure the logging agent on the remote machine?

If it's going to a Logstash syslog input, these logs: Are not RFC-3164/RFC-5424 compliant and will cause issues in the parsing stages. The standard expects every line to have, among other things, a timestamp.

I would suggest shipping these logs to some other sort of input rule. Perhaps the "Import Files - Raw" one that ships with Nagios Log Server by default. The change could be as simple as altering the port your logging agent on the remote machine (rsyslog, syslog-ng, nxlog, fluentd, etc) is using.

Thanks for the input, @mcapra!

@mcapra @cdienger As I mentioned in the starting, sometimes I get the full logs but some times not.

@@ysingh, as mentioned in our previous responses, there appears to be an issue with the logs not having the proper formatting. Try configuring the logging agent to send logs to port 2056 instead of 5544.