What are these numbers in the logs? “Nov 19 11:06:42 [redacted]/web.7: 10111111166611[error] 19:06:42...
up vote
0
down vote
favorite
Here are some more examples:
Nov 19 11:06:42 [redacted] app/web.7: 10111111166611[error] 19:06:42 c.TransactionController - [redacted].
Nov 19 10:50:02 [redacted] app/web.3: 110111001111111111111111016111[warn] 18:50:02 c.BrowseController - [redacted]
Nov 19 06:13:58 [redacted] app/web.2: 1101111111110[warn] 14:13:57 c.TransactionController - [redacted]
Nov 19 05:33:26 [redacted] app/web.4: 111111111111111111001011[error] 13:33:26 c.TransactionController -[redacted]
Nov 19 05:11:32 [redacted] app/web.3: 1111111111111111011[warn] 13:11:32 c.TransactionController - [redacted]
Nov 19 04:42:30 [redacted] app/web.8: 01111111110111111110110[error] 12:42:30 c.TransactionController - [redacted]
Nov 19 03:26:09 [redacted] app/web.4: 11011111006660000[error] 11:26:09 c.TransactionController - [redacted]
It started showing in my logs roughly since yesterday.
My app is deployed on Heroku, and we use slf4j and logback. The logs are sent to Papertrails.
At first, I thought it was a binary number, but then there are 6s.
Anyone has intelligent guesses what they are? Thank you.
Edit: Here's my log config:
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %date{HH:mm:ss} %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<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" />/>
<logger name="com.zaxxer.hikari" level="OFF" />
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<logger name="play.api.db.evolutions" level="DEBUG" />
<root level="INFO">
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
heroku logback slf4j
add a comment |
up vote
0
down vote
favorite
Here are some more examples:
Nov 19 11:06:42 [redacted] app/web.7: 10111111166611[error] 19:06:42 c.TransactionController - [redacted].
Nov 19 10:50:02 [redacted] app/web.3: 110111001111111111111111016111[warn] 18:50:02 c.BrowseController - [redacted]
Nov 19 06:13:58 [redacted] app/web.2: 1101111111110[warn] 14:13:57 c.TransactionController - [redacted]
Nov 19 05:33:26 [redacted] app/web.4: 111111111111111111001011[error] 13:33:26 c.TransactionController -[redacted]
Nov 19 05:11:32 [redacted] app/web.3: 1111111111111111011[warn] 13:11:32 c.TransactionController - [redacted]
Nov 19 04:42:30 [redacted] app/web.8: 01111111110111111110110[error] 12:42:30 c.TransactionController - [redacted]
Nov 19 03:26:09 [redacted] app/web.4: 11011111006660000[error] 11:26:09 c.TransactionController - [redacted]
It started showing in my logs roughly since yesterday.
My app is deployed on Heroku, and we use slf4j and logback. The logs are sent to Papertrails.
At first, I thought it was a binary number, but then there are 6s.
Anyone has intelligent guesses what they are? Thank you.
Edit: Here's my log config:
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %date{HH:mm:ss} %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<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" />/>
<logger name="com.zaxxer.hikari" level="OFF" />
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<logger name="play.api.db.evolutions" level="DEBUG" />
<root level="INFO">
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
heroku logback slf4j
1
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Here are some more examples:
Nov 19 11:06:42 [redacted] app/web.7: 10111111166611[error] 19:06:42 c.TransactionController - [redacted].
Nov 19 10:50:02 [redacted] app/web.3: 110111001111111111111111016111[warn] 18:50:02 c.BrowseController - [redacted]
Nov 19 06:13:58 [redacted] app/web.2: 1101111111110[warn] 14:13:57 c.TransactionController - [redacted]
Nov 19 05:33:26 [redacted] app/web.4: 111111111111111111001011[error] 13:33:26 c.TransactionController -[redacted]
Nov 19 05:11:32 [redacted] app/web.3: 1111111111111111011[warn] 13:11:32 c.TransactionController - [redacted]
Nov 19 04:42:30 [redacted] app/web.8: 01111111110111111110110[error] 12:42:30 c.TransactionController - [redacted]
Nov 19 03:26:09 [redacted] app/web.4: 11011111006660000[error] 11:26:09 c.TransactionController - [redacted]
It started showing in my logs roughly since yesterday.
My app is deployed on Heroku, and we use slf4j and logback. The logs are sent to Papertrails.
At first, I thought it was a binary number, but then there are 6s.
Anyone has intelligent guesses what they are? Thank you.
Edit: Here's my log config:
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %date{HH:mm:ss} %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<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" />/>
<logger name="com.zaxxer.hikari" level="OFF" />
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<logger name="play.api.db.evolutions" level="DEBUG" />
<root level="INFO">
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
heroku logback slf4j
Here are some more examples:
Nov 19 11:06:42 [redacted] app/web.7: 10111111166611[error] 19:06:42 c.TransactionController - [redacted].
Nov 19 10:50:02 [redacted] app/web.3: 110111001111111111111111016111[warn] 18:50:02 c.BrowseController - [redacted]
Nov 19 06:13:58 [redacted] app/web.2: 1101111111110[warn] 14:13:57 c.TransactionController - [redacted]
Nov 19 05:33:26 [redacted] app/web.4: 111111111111111111001011[error] 13:33:26 c.TransactionController -[redacted]
Nov 19 05:11:32 [redacted] app/web.3: 1111111111111111011[warn] 13:11:32 c.TransactionController - [redacted]
Nov 19 04:42:30 [redacted] app/web.8: 01111111110111111110110[error] 12:42:30 c.TransactionController - [redacted]
Nov 19 03:26:09 [redacted] app/web.4: 11011111006660000[error] 11:26:09 c.TransactionController - [redacted]
It started showing in my logs roughly since yesterday.
My app is deployed on Heroku, and we use slf4j and logback. The logs are sent to Papertrails.
At first, I thought it was a binary number, but then there are 6s.
Anyone has intelligent guesses what they are? Thank you.
Edit: Here's my log config:
<configuration>
<conversionRule conversionWord="coloredLevel" converterClass="play.api.libs.logback.ColoredLevel" />
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%coloredLevel %date{HH:mm:ss} %logger{15} - %message%n%xException{10}</pattern>
</encoder>
</appender>
<appender name="ASYNCSTDOUT" class="ch.qos.logback.classic.AsyncAppender">
<appender-ref ref="STDOUT" />
</appender>
<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" />/>
<logger name="com.zaxxer.hikari" level="OFF" />
<logger name="play" level="INFO" />
<logger name="application" level="INFO" />
<logger name="play.api.db.evolutions" level="DEBUG" />
<root level="INFO">
<appender-ref ref="ASYNCSTDOUT" />
</root>
</configuration>
heroku logback slf4j
heroku logback slf4j
edited Nov 20 at 17:01
asked Nov 19 at 19:20
Tanin
1,0301917
1,0301917
1
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06
add a comment |
1
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06
1
1
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
Try removing %coloredLeve. It looks like something doesn't understand the color escaping.
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
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',
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%2f53381274%2fwhat-are-these-numbers-in-the-logs-nov-19-110642-redacted-web-7-101111111%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Try removing %coloredLeve. It looks like something doesn't understand the color escaping.
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
add a comment |
up vote
1
down vote
Try removing %coloredLeve. It looks like something doesn't understand the color escaping.
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
add a comment |
up vote
1
down vote
up vote
1
down vote
Try removing %coloredLeve. It looks like something doesn't understand the color escaping.
Try removing %coloredLeve. It looks like something doesn't understand the color escaping.
answered Nov 22 at 21:14
David Roussel
4,25812129
4,25812129
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
add a comment |
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
I've changed it to %level, but the strange numbers still show. However, it only shows for the ERROR-level log now. For %coloredLevel, the strange numbers show up for the WARN- and ERROR-level logs. Do you happen to know what those numbers are? Why do they compose of 0,1,and 6?
– Tanin
Nov 24 at 23:45
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
No I don't know what it is, but I saw that %coloredLevel is the first thing in your pattern definition, which needs the numbers are either coming from %coloredLevel itself, or from the processing of the platform (heroku). What about if you remove the 'conversionRule'
– David Roussel
Nov 26 at 21:46
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53381274%2fwhat-are-these-numbers-in-the-logs-nov-19-110642-redacted-web-7-101111111%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
1
Can you show your logback configuration file?
– toancaro
Nov 20 at 4:25
I've added it. Thank you. It looks normal to me though.
– Tanin
Nov 20 at 17:01
Wait a min. This means Papertrails is the one who adds these strange numbers. Because my log config start with %coloredLevel
– Tanin
Nov 20 at 17:02
Actually, the strange numbers show up since Heroku. So, Papertrails isn't related to this issue.
– Tanin
Nov 22 at 6:06