Log command of the REST API provides access just for logs of the node where
the service raised.
Logs can be retrieved from IGNITE_HOME/ or from the path defined in the log
configuration of the node.
Log configuration should be defined expliciltly when Ignite-log4j module is
enabled.
XML:
Created minor ticket IGNITE-4845
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p11325.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Sam,
This makes sense to me. Can you create a ticket and put your thoughts there?
Contributions are also very welcome ;)
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p11162.html
Sent from the Apache Ignite Users
IGNITE_HOME/work/log/ignite.log location.
I think when Ignite-log4j module is enabled it should make Ignite aware of
logging configuration.
Thanks,
-Sam
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p11158.html
Sent from the
this message in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p10164.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p10160.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Sam,
What if you does not provide the 'path' parameter? Does it work?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p10159.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
