Mixing
Why can't I see my log messages for my actors for levels other than error
So I have a play application with sub-modules like this:
/app // play app
/modules/notifications
Inside my play app I have a task module that starts up my main actor:
Logger.debug("starting main supervisor actor Iot")
val supervisor = system.actorOf(IotSupervisor.props(), "iot-supervisor")
inside of notifications I have this file:
/modules/notifications/src/main/supervisor.scala
package com.example.notifications
import akka.actor.{ Actor, ActorLogging, Props }
object IotSupervisor {
def props(): Props = Props(new IotSupervisor)
}
class IotSupervisor extends Actor with ActorLogging {
log.debug("Iot constrcutor called..")
override def preStart(): Unit = log.info("IoT Application started")
override def postStop(): Unit = log.info("IoT Application stopped")
// No need to handle any messages
override def receive = Actor.emptyBehavior
}
I can see logs in my console:
[debug] application - starting main supervisor actor Iot [info]
p.a.h.EnabledFilters - Enabled Filters (see
https://www.playframework.com/documentation/latest/Filters):
play.filters.csrf.CSRFFilter
play.filters.headers.SecurityHeadersFilter
[info] play.api.Play - Application started (Dev)
My logback.xml looks like:
<!-- https://www.playframework.com/documentation/latest/SettingsLogger -->
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<!--<appender name="FILE" class="ch.qos.logback.core.FileAppender">-->
<!--<file>${application.home:-.}/logs/application.log</file>-->
<!--<encoder>-->
<!--<pattern>%date [%level] from %logger in %thread - %message%n%xException</pattern>-->
<!--</encoder>-->
<!--</appender>-->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<!--<appender name="ASYNCFILE" class="ch.qos.logback.classic.AsyncAppender">-->
<!--<appender-ref ref="FILE" />-->
<!--</appender>-->
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<logger name="play" level="INFO" />
<logger name="application" level="DEBUG" />
<logger name="com.example.notifications" LEVEL="TRACE" />
<!-- Off these ones as they are annoying, and anyway we manage configuration ourselves -->
<logger name="com.avaje.ebean.config.PropertyMapLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.core.XmlConfigLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.lib.BackgroundThread" level="OFF" />
<logger name="com.gargoylesoftware.htmlunit.javascript" level="OFF" />
<root level="WARN">
<!--<appender-ref ref="ASYNCFILE" />-->
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
I do not see any log messages from inside my actors, unless I use log.error, why is that?
I set the level to TRACE for com.example.notifications
Am I correct in understanding that whenever I use a logger, it will use the logger defined in logback that matches the package name? i.e. com.example.notification will be used to lookup the logger in my logback.xml and use the LEVEL defined there?
scala logging akka
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
add a comment |
So I have a play application with sub-modules like this:
/app // play app
/modules/notifications
Inside my play app I have a task module that starts up my main actor:
Logger.debug("starting main supervisor actor Iot")
val supervisor = system.actorOf(IotSupervisor.props(), "iot-supervisor")
inside of notifications I have this file:
/modules/notifications/src/main/supervisor.scala
package com.example.notifications
import akka.actor.{ Actor, ActorLogging, Props }
object IotSupervisor {
def props(): Props = Props(new IotSupervisor)
}
class IotSupervisor extends Actor with ActorLogging {
log.debug("Iot constrcutor called..")
override def preStart(): Unit = log.info("IoT Application started")
override def postStop(): Unit = log.info("IoT Application stopped")
// No need to handle any messages
override def receive = Actor.emptyBehavior
}
I can see logs in my console:
[debug] application - starting main supervisor actor Iot [info]
p.a.h.EnabledFilters - Enabled Filters (see
https://www.playframework.com/documentation/latest/Filters):
play.filters.csrf.CSRFFilter
play.filters.headers.SecurityHeadersFilter
[info] play.api.Play - Application started (Dev)
My logback.xml looks like:
<!-- https://www.playframework.com/documentation/latest/SettingsLogger -->
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<!--<appender name="FILE" class="ch.qos.logback.core.FileAppender">-->
<!--<file>${application.home:-.}/logs/application.log</file>-->
<!--<encoder>-->
<!--<pattern>%date [%level] from %logger in %thread - %message%n%xException</pattern>-->
<!--</encoder>-->
<!--</appender>-->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<!--<appender name="ASYNCFILE" class="ch.qos.logback.classic.AsyncAppender">-->
<!--<appender-ref ref="FILE" />-->
<!--</appender>-->
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<logger name="play" level="INFO" />
<logger name="application" level="DEBUG" />
<logger name="com.example.notifications" LEVEL="TRACE" />
<!-- Off these ones as they are annoying, and anyway we manage configuration ourselves -->
<logger name="com.avaje.ebean.config.PropertyMapLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.core.XmlConfigLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.lib.BackgroundThread" level="OFF" />
<logger name="com.gargoylesoftware.htmlunit.javascript" level="OFF" />
<root level="WARN">
<!--<appender-ref ref="ASYNCFILE" />-->
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
I do not see any log messages from inside my actors, unless I use log.error, why is that?
I set the level to TRACE for com.example.notifications
Am I correct in understanding that whenever I use a logger, it will use the logger defined in logback that matches the package name? i.e. com.example.notification will be used to lookup the logger in my logback.xml and use the LEVEL defined there?
scala logging akka
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
add a comment |
So I have a play application with sub-modules like this:
/app // play app
/modules/notifications
Inside my play app I have a task module that starts up my main actor:
Logger.debug("starting main supervisor actor Iot")
val supervisor = system.actorOf(IotSupervisor.props(), "iot-supervisor")
inside of notifications I have this file:
/modules/notifications/src/main/supervisor.scala
package com.example.notifications
import akka.actor.{ Actor, ActorLogging, Props }
object IotSupervisor {
def props(): Props = Props(new IotSupervisor)
}
class IotSupervisor extends Actor with ActorLogging {
log.debug("Iot constrcutor called..")
override def preStart(): Unit = log.info("IoT Application started")
override def postStop(): Unit = log.info("IoT Application stopped")
// No need to handle any messages
override def receive = Actor.emptyBehavior
}
I can see logs in my console:
[debug] application - starting main supervisor actor Iot [info]
p.a.h.EnabledFilters - Enabled Filters (see
https://www.playframework.com/documentation/latest/Filters):
play.filters.csrf.CSRFFilter
play.filters.headers.SecurityHeadersFilter
[info] play.api.Play - Application started (Dev)
My logback.xml looks like:
<!-- https://www.playframework.com/documentation/latest/SettingsLogger -->
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<!--<appender name="FILE" class="ch.qos.logback.core.FileAppender">-->
<!--<file>${application.home:-.}/logs/application.log</file>-->
<!--<encoder>-->
<!--<pattern>%date [%level] from %logger in %thread - %message%n%xException</pattern>-->
<!--</encoder>-->
<!--</appender>-->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<!--<appender name="ASYNCFILE" class="ch.qos.logback.classic.AsyncAppender">-->
<!--<appender-ref ref="FILE" />-->
<!--</appender>-->
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<logger name="play" level="INFO" />
<logger name="application" level="DEBUG" />
<logger name="com.example.notifications" LEVEL="TRACE" />
<!-- Off these ones as they are annoying, and anyway we manage configuration ourselves -->
<logger name="com.avaje.ebean.config.PropertyMapLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.core.XmlConfigLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.lib.BackgroundThread" level="OFF" />
<logger name="com.gargoylesoftware.htmlunit.javascript" level="OFF" />
<root level="WARN">
<!--<appender-ref ref="ASYNCFILE" />-->
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
I do not see any log messages from inside my actors, unless I use log.error, why is that?
I set the level to TRACE for com.example.notifications
Am I correct in understanding that whenever I use a logger, it will use the logger defined in logback that matches the package name? i.e. com.example.notification will be used to lookup the logger in my logback.xml and use the LEVEL defined there?
scala logging akka
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
So I have a play application with sub-modules like this:
/app // play app
/modules/notifications
Inside my play app I have a task module that starts up my main actor:
Logger.debug("starting main supervisor actor Iot")
val supervisor = system.actorOf(IotSupervisor.props(), "iot-supervisor")
inside of notifications I have this file:
/modules/notifications/src/main/supervisor.scala
package com.example.notifications
import akka.actor.{ Actor, ActorLogging, Props }
object IotSupervisor {
def props(): Props = Props(new IotSupervisor)
}
class IotSupervisor extends Actor with ActorLogging {
log.debug("Iot constrcutor called..")
override def preStart(): Unit = log.info("IoT Application started")
override def postStop(): Unit = log.info("IoT Application stopped")
// No need to handle any messages
override def receive = Actor.emptyBehavior
}
I can see logs in my console:
[debug] application - starting main supervisor actor Iot [info]
p.a.h.EnabledFilters - Enabled Filters (see
https://www.playframework.com/documentation/latest/Filters):
play.filters.csrf.CSRFFilter
play.filters.headers.SecurityHeadersFilter
[info] play.api.Play - Application started (Dev)
My logback.xml looks like:
<!-- https://www.playframework.com/documentation/latest/SettingsLogger -->
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<!--<appender name="FILE" class="ch.qos.logback.core.FileAppender">-->
<!--<file>${application.home:-.}/logs/application.log</file>-->
<!--<encoder>-->
<!--<pattern>%date [%level] from %logger in %thread - %message%n%xException</pattern>-->
<!--</encoder>-->
<!--</appender>-->
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<!--<appender name="ASYNCFILE" class="ch.qos.logback.classic.AsyncAppender">-->
<!--<appender-ref ref="FILE" />-->
<!--</appender>-->
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<logger name="play" level="INFO" />
<logger name="application" level="DEBUG" />
<logger name="com.example.notifications" LEVEL="TRACE" />
<!-- Off these ones as they are annoying, and anyway we manage configuration ourselves -->
<logger name="com.avaje.ebean.config.PropertyMapLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.core.XmlConfigLoader" level="OFF" />
<logger name="com.avaje.ebeaninternal.server.lib.BackgroundThread" level="OFF" />
<logger name="com.gargoylesoftware.htmlunit.javascript" level="OFF" />
<root level="WARN">
<!--<appender-ref ref="ASYNCFILE" />-->
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
I do not see any log messages from inside my actors, unless I use log.error, why is that?
I set the level to TRACE for com.example.notifications
Am I correct in understanding that whenever I use a logger, it will use the logger defined in logback that matches the package name? i.e. com.example.notification will be used to lookup the logger in my logback.xml and use the LEVEL defined there?
scala logging akka
scala logging akka
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
asked Jan 1 at 15:31
BlankmanBlankman
97.7k2706641043
97.7k2706641043
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You need to read this documentation on how to enable slf4j in akka.
In summary,
add to build.sbt
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-slf4j" % "2.5.19",
"ch.qos.logback" % "logback-classic" % "1.2.3"
)
add to application.conf
akka {
loggers = ["akka.event.slf4j.Slf4jLogger"]
loglevel = "DEBUG"
logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
}
You need to enable the Slf4jLogger in the loggers element in the
configuration. Here you can also define the log level of the event
bus. More fine grained log levels can be defined in the configuration
of the SLF4J backend (e.g. logback.xml). You should also define
akka.event.slf4j.Slf4jLoggingFilter in the logging-filter
configuration property. It will filter the log events using the
backend configuration (e.g. logback.xml) before they are published to
the event bus.
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
add a comment |
Ensure that your project depends on "com.typesafe.akka" %% "akka-slf4j" and "ch.qos.logback" % "logback-classic". Otherwise akka might use a logger implentation other than logback.
If that does not solve your issue, try to explicitly use the logger of your ActorSystem:
system.log.debug("starting main supervisor actor Iot")
answered Jan 1 at 17:40
AkiAki
1,098213
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996680%2fwhy-cant-i-see-my-log-messages-for-my-actors-for-levels-other-than-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to read this documentation on how to enable slf4j in akka.
In summary,
add to build.sbt
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-slf4j" % "2.5.19",
"ch.qos.logback" % "logback-classic" % "1.2.3"
)
add to application.conf
akka {
loggers = ["akka.event.slf4j.Slf4jLogger"]
loglevel = "DEBUG"
logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
}
You need to enable the Slf4jLogger in the loggers element in the
configuration. Here you can also define the log level of the event
bus. More fine grained log levels can be defined in the configuration
of the SLF4J backend (e.g. logback.xml). You should also define
akka.event.slf4j.Slf4jLoggingFilter in the logging-filter
configuration property. It will filter the log events using the
backend configuration (e.g. logback.xml) before they are published to
the event bus.
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
add a comment |
You need to read this documentation on how to enable slf4j in akka.
In summary,
add to build.sbt
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-slf4j" % "2.5.19",
"ch.qos.logback" % "logback-classic" % "1.2.3"
)
add to application.conf
akka {
loggers = ["akka.event.slf4j.Slf4jLogger"]
loglevel = "DEBUG"
logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
}
You need to enable the Slf4jLogger in the loggers element in the
configuration. Here you can also define the log level of the event
bus. More fine grained log levels can be defined in the configuration
of the SLF4J backend (e.g. logback.xml). You should also define
akka.event.slf4j.Slf4jLoggingFilter in the logging-filter
configuration property. It will filter the log events using the
backend configuration (e.g. logback.xml) before they are published to
the event bus.
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
add a comment |
You need to read this documentation on how to enable slf4j in akka.
In summary,
add to build.sbt
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-slf4j" % "2.5.19",
"ch.qos.logback" % "logback-classic" % "1.2.3"
)
add to application.conf
akka {
loggers = ["akka.event.slf4j.Slf4jLogger"]
loglevel = "DEBUG"
logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
}
You need to enable the Slf4jLogger in the loggers element in the
configuration. Here you can also define the log level of the event
bus. More fine grained log levels can be defined in the configuration
of the SLF4J backend (e.g. logback.xml). You should also define
akka.event.slf4j.Slf4jLoggingFilter in the logging-filter
configuration property. It will filter the log events using the
backend configuration (e.g. logback.xml) before they are published to
the event bus.
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
You need to read this documentation on how to enable slf4j in akka.
In summary,
add to build.sbt
libraryDependencies ++= Seq(
"com.typesafe.akka" %% "akka-slf4j" % "2.5.19",
"ch.qos.logback" % "logback-classic" % "1.2.3"
)
add to application.conf
akka {
loggers = ["akka.event.slf4j.Slf4jLogger"]
loglevel = "DEBUG"
logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"
}
You need to enable the Slf4jLogger in the loggers element in the
configuration. Here you can also define the log level of the event
bus. More fine grained log levels can be defined in the configuration
of the SLF4J backend (e.g. logback.xml). You should also define
akka.event.slf4j.Slf4jLoggingFilter in the logging-filter
configuration property. It will filter the log events using the
backend configuration (e.g. logback.xml) before they are published to
the event bus.
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
answered Jan 3 at 8:32
Ivan StanislavciucIvan Stanislavciuc
1,55049
1,55049
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
add a comment |
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
just to make sure, is this the best practise? I was reading that logging incorrectly in akka can really slow down performance. thanks!
– Blankman
Jan 3 at 14:36
1
1
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
This is the way to enable logging in akka. Indeed, having a lot of logging can have impact on the system. Because of this you have control over level and logging-filter to limit the amount of log events in the event bus. In production environments, it's recommended to have small amount of logs.
– Ivan Stanislavciuc
Jan 3 at 14:39
add a comment |
Ensure that your project depends on "com.typesafe.akka" %% "akka-slf4j" and "ch.qos.logback" % "logback-classic". Otherwise akka might use a logger implentation other than logback.
If that does not solve your issue, try to explicitly use the logger of your ActorSystem:
system.log.debug("starting main supervisor actor Iot")
answered Jan 1 at 17:40
AkiAki
1,098213
add a comment |
Ensure that your project depends on "com.typesafe.akka" %% "akka-slf4j" and "ch.qos.logback" % "logback-classic". Otherwise akka might use a logger implentation other than logback.
If that does not solve your issue, try to explicitly use the logger of your ActorSystem:
system.log.debug("starting main supervisor actor Iot")
answered Jan 1 at 17:40
AkiAki
1,098213
add a comment |
Ensure that your project depends on "com.typesafe.akka" %% "akka-slf4j" and "ch.qos.logback" % "logback-classic". Otherwise akka might use a logger implentation other than logback.
If that does not solve your issue, try to explicitly use the logger of your ActorSystem:
system.log.debug("starting main supervisor actor Iot")
answered Jan 1 at 17:40
AkiAki
1,098213
Ensure that your project depends on "com.typesafe.akka" %% "akka-slf4j" and "ch.qos.logback" % "logback-classic". Otherwise akka might use a logger implentation other than logback.
If that does not solve your issue, try to explicitly use the logger of your ActorSystem:
system.log.debug("starting main supervisor actor Iot")
answered Jan 1 at 17:40
AkiAki
1,098213
answered Jan 1 at 17:40
AkiAki
1,098213
answered Jan 1 at 17:40
AkiAki
1,098213
answered Jan 1 at 17:40
AkiAki
1,098213
1,098213
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53996680%2fwhy-cant-i-see-my-log-messages-for-my-actors-for-levels-other-than-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
