Count the number of request from the trace file or from log file

by Naveen   Last Updated October 09, 2019 13:00 PM

I need to find how many requests are hitting the server from trace file. My trace contains transaction id based on this transaction id we can decide how many time. But I need some solution to find how many unique transaction id is in the trace log because sometime this may repeat.

this is one request 44c26c5d271062f71ac98ba0 this is transaction id

ERROR 02/Sep/2019:09:18:28.345 [665b:44c26c5d271062f71ac98ba0] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.345 [665b:44c26c5d271062f71ac98ba0] The message [Id-44c26c5d271062f71ac98ba0] logged Failure at 09.02.2019 09:18:28,345 with log description: Failed in adding the HTTP header to the message ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] The Selector Expression representing the HTTP header value evaluated to null: ${custom.header.mtan} ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] The message [Id-44c26c5d271062f71ac98ba0] logged Failure at 09.02.2019 09:18:28,346 with log description: Failed in adding the HTTP header to the message INFO 02/Sep/2019:09:18:28.347 [665b:44c26c5d271062f71ac98ba0] No Headers to Cache!

sample trace looks

ERROR 02/Sep/2019:09:18:28.345 [665b:44c26c5d271062f71ac98ba0] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.345 [665b:44c26c5d271062f71ac98ba0] The message [Id-44c26c5d271062f71ac98ba0] logged Failure at 09.02.2019 09:18:28,345 with log description: Failed in adding the HTTP header to the message ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] The Selector Expression representing the HTTP header value evaluated to null: ${custom.header.mtan} ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.346 [665b:44c26c5d271062f71ac98ba0] The message [Id-44c26c5d271062f71ac98ba0] logged Failure at 09.02.2019 09:18:28,346 with log description: Failed in adding the HTTP header to the message INFO 02/Sep/2019:09:18:28.347 [665b:44c26c5d271062f71ac98ba0] No Headers to Cache! INFO 02/Sep/2019:09:18:28.366 [5c0e:44c26c5d2910655ce160f55b] [BizLog] request: /vsapi/state/v1/vehicles ERROR 02/Sep/2019:09:18:28.369 [5c0e:44c26c5d2910655ce160f55b] The message [Id-44c26c5d2910655ce160f55b] logged Failure at 09.02.2019 09:18:28,369 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.370 [5c0e:44c26c5d2910655ce160f55b] For an API Vehicle Shadow State API with concurrent request is 10 INFO 02/Sep/2019:09:18:28.378 [488f:44c26c5d2a10ea0f9dee0843] [BizLog] request: /vsapi/state/v1/vehicles INFO 02/Sep/2019:09:18:28.379 [5722:44c26c5d2b10108b95272fc3] [BizLog] request: /vsapi/state/v1/vehicles ERROR 02/Sep/2019:09:18:28.381 [488f:44c26c5d2a10ea0f9dee0843] The message [Id-44c26c5d2a10ea0f9dee0843] logged Failure at 09.02.2019 09:18:28,381 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.382 [488f:44c26c5d2a10ea0f9dee0843] For an API Vehicle Shadow State API with concurrent request is 11 ERROR 02/Sep/2019:09:18:28.383 [5722:44c26c5d2b10108b95272fc3] The message [Id-44c26c5d2b10108b95272fc3] logged Failure at 09.02.2019 09:18:28,383 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.383 [5722:44c26c5d2b10108b95272fc3] For an API Vehicle Shadow State API with concurrent request is 12 INFO 02/Sep/2019:09:18:28.393 [4d94:44c26c5d2f10ca2b186c4265] [BizLog] request: /vsapi/state/v1/vehicles INFO 02/Sep/2019:09:18:28.393 [4e4f:44c26c5d2e107fff50de8041] [BizLog] request: /vsapi/state/v1/vehicles INFO 02/Sep/2019:09:18:28.393 [56b5:44c26c5d2c1008e9466e49e1] [BizLog] request: /webapi/v1/user/vehicles ERROR 02/Sep/2019:09:18:28.396 [4d94:44c26c5d2f10ca2b186c4265] The message [Id-44c26c5d2f10ca2b186c4265] logged Failure at 09.02.2019 09:18:28,396 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.397 [4d94:44c26c5d2f10ca2b186c4265] For an API Vehicle Shadow State API with concurrent request is 12 ERROR 02/Sep/2019:09:18:28.397 [4e4f:44c26c5d2e107fff50de8041] The message [Id-44c26c5d2e107fff50de8041] logged Failure at 09.02.2019 09:18:28,397 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.398 [4e4f:44c26c5d2e107fff50de8041] For an API Vehicle Shadow State API with concurrent request is 13 ERROR 02/Sep/2019:09:18:28.399 [56b5:44c26c5d2c1008e9466e49e1] The message [Id-44c26c5d2c1008e9466e49e1] logged Failure at 09.02.2019 09:18:28,399 with log description: No API limit configuration found - looking for defalt value next INFO 02/Sep/2019:09:18:28.400 [56b5:44c26c5d2c1008e9466e49e1] For an API WebAPI v1.2 with concurrent request is 57 ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] The Selector Expression representing the HTTP header value evaluated to null: ${accesstoken.getAdditionalInformation().get("qid")} ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] The message [Id-44c26c5d2c1008e9466e49e1] logged Failure at 09.02.2019 09:18:28,401 with log description: Failed in adding the HTTP header to the message ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] The Selector Expression representing the HTTP header value evaluated to null: ${custom.header.mtan} ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] Cannot add a HTTP header with a null value to the message. ERROR 02/Sep/2019:09:18:28.401 [56b5:44c26c5d2c1008e9466e49e1] The message [Id-44c26c5d2c1008e9466e49e1] logged Failure at 09.02.2019 09:18:28,401 with log description: Failed in adding the HTTP header to the message INFO 02/Sep/2019:09:18:28.402 [56b5:44c26c5d2c1008e9466e49e1] No Headers to Cache!

Tags : google-chrome


Related Questions


Updated January 04, 2018 12:00 PM

Updated January 23, 2019 01:00 AM

Updated September 30, 2019 13:00 PM

Updated January 08, 2016 12:00 PM

Updated August 14, 2019 00:00 AM