Why is the Google Cloud Python library adding redundant logging?











up vote
1
down vote

favorite












During from google.cloud import pubsub_v1, the Google library adds a StreamHandler to the root logger.



This means that with my own logger, each line appears twice.



INFO:thelogger:Retrieving result for miqxxgcfuv, status Pending

2018-11-18 21:17:22;INFO;Retrieving result for miqxxgcfuv, status Pending


Setting the handlers= on the root logger resolves this, but then various libraries including the Google libraries do not log at all, and I do want their logs.






python logging google-cloud-platform google-cloud-pubsub







share|improve this question
























  • How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
    – n8sty
    yesterday










  • I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
    – Joshua Fox
    yesterday










  • You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
    – n8sty
    yesterday










  • In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
    – Joshua Fox
    yesterday










  • I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
    – Joshua Fox
    yesterday















up vote
1
down vote

favorite












During from google.cloud import pubsub_v1, the Google library adds a StreamHandler to the root logger.



This means that with my own logger, each line appears twice.



INFO:thelogger:Retrieving result for miqxxgcfuv, status Pending

2018-11-18 21:17:22;INFO;Retrieving result for miqxxgcfuv, status Pending


Setting the handlers= on the root logger resolves this, but then various libraries including the Google libraries do not log at all, and I do want their logs.






python logging google-cloud-platform google-cloud-pubsub







share|improve this question
























  • How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
    – n8sty
    yesterday










  • I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
    – Joshua Fox
    yesterday










  • You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
    – n8sty
    yesterday










  • In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
    – Joshua Fox
    yesterday










  • I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
    – Joshua Fox
    yesterday













up vote
1
down vote

favorite









up vote
1
down vote

favorite











During from google.cloud import pubsub_v1, the Google library adds a StreamHandler to the root logger.



This means that with my own logger, each line appears twice.



INFO:thelogger:Retrieving result for miqxxgcfuv, status Pending

2018-11-18 21:17:22;INFO;Retrieving result for miqxxgcfuv, status Pending


Setting the handlers= on the root logger resolves this, but then various libraries including the Google libraries do not log at all, and I do want their logs.






python logging google-cloud-platform google-cloud-pubsub







share|improve this question















During from google.cloud import pubsub_v1, the Google library adds a StreamHandler to the root logger.



This means that with my own logger, each line appears twice.



INFO:thelogger:Retrieving result for miqxxgcfuv, status Pending

2018-11-18 21:17:22;INFO;Retrieving result for miqxxgcfuv, status Pending


Setting the handlers= on the root logger resolves this, but then various libraries including the Google libraries do not log at all, and I do want their logs.






python logging google-cloud-platform google-cloud-pubsub




python logging google-cloud-platform google-cloud-pubsub






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 7 hours ago

























asked yesterday









Joshua Fox

7,65595076




7,65595076












  • How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
    – n8sty
    yesterday










  • I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
    – Joshua Fox
    yesterday










  • You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
    – n8sty
    yesterday










  • In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
    – Joshua Fox
    yesterday










  • I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
    – Joshua Fox
    yesterday


















  • How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
    – n8sty
    yesterday










  • I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
    – Joshua Fox
    yesterday










  • You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
    – n8sty
    yesterday










  • In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
    – Joshua Fox
    yesterday










  • I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
    – Joshua Fox
    yesterday
















How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
– n8sty
yesterday




How are you creating your logger? Possible you're using the default configuration and then adding an additional handler on top.
– n8sty
yesterday












I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
– Joshua Fox
yesterday




I am creating it with the ordinary constructor logging.getLogger("thelogger"). You say "using the default configuration" -- how do I avoid that?
– Joshua Fox
yesterday












You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
– n8sty
yesterday




You're almost definitely adding multiple handlers. Running import logging; logger=logging.getLogger('thelogger'); logger.addHandler(logging.StreamHandler()); logger.setLevel(logging.INFO); logger.warning('hi') returns hi. If you run that same command twice, the second invocation will print hi to the console twice. The order in which a logger is created matters so it's hard to say exactly why you're getting what you're getting without you showing what you're doing.
– n8sty
yesterday












In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
– Joshua Fox
yesterday




In the line after the double-logging thelogger.info("xxx), I tried print(thelogger.handlers). It shows "[<StreamHandler <stdout> (INFO)>]" -- in other words, only one Handler. But note -- this occurs under Flask [edited main body]. When I run, e.g. a unittest, I don't get this doubling
– Joshua Fox
yesterday












I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
– Joshua Fox
yesterday




I narrowed this down to a Google library. See body. But I still don't know how to avoid it.
– Joshua Fox
yesterday

















active

oldest

votes











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
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53364595%2fwhy-is-the-google-cloud-python-library-adding-redundant-logging%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53364595%2fwhy-is-the-google-cloud-python-library-adding-redundant-logging%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

Image
28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
Read more

Does disintegrating a polymorphed enemy still kill it after the 2018 errata?

Image
up vote 13 down vote favorite 1 After the 2018 errata, the disintegrate spell description now reads: A creature targeted by this spell must make a Dexterity saving throw. On a failed save, the target takes 10d6 + 40 force damage. The target is disintegrated if this damage leaves it with 0 hit points. If you were to polymorph an enemy into a rat and then disintegrate it, would the enemy be disintegrated or would it just return to its original form? I know that for Druids, it’s not an instant kill anymore, but is this the case for polymorph as well? dnd-5e spells polymorph errata share | improve this question edited 18 hours ago
Read more

A Topological Invariant for $pi_3(U(n))$

Image
3 3 $begingroup$ Recently, I saw a construction of topological invariant for $pi_3(U(n))$ with $ngeq 2$ : $$ N=frac{1}{24pi^2}int_{S^3} d^3x epsilon^{ijk} Tr[(U^{-1}partial_{x_i}U)(U^{-1}partial_{x_j}U)(U^{-1}partial_{x_k}U)] , $$ where $Uin U(n)$ depends on $boldsymbol{x}=(x_1,x_2,x_3)in S^3$ , $epsilon^{ijk}$ is the Levi-Civita symbol, $i,j,k=1,2,3$ , and the duplicated indexes are summed over. It is claimed that $N$ is an integer, but why? Update 02/02/2019 I think I got an argument for $n=2$ . In this case, $U=e^{i varphi} q$ with $qin SU(2)$ . Due to the trace and the Levi-Civita symbol in $N$ , $varphi$ does not contribute to $N$ . As $Tr[q^{dagger}partial_i q]=0$ and $(q^{dagger}partial_i q)^{dagger}=-q^{dagger}partial_i q$ , $q^{dagger}partial_i q$ in geneeral has the form $q^{dagger}partia
Read more