AttributeError: module 'opencensus.stats.stats' has no attribute 'Stats'
See original GitHub issueI’m following the Python example on https://opencensus.io/stats/view/#2
>>> from opencensus.stats import stats
>>> view_manager = stats.Stats().view_manager
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
AttributeError: module 'opencensus.stats.stats' has no attribute 'Stats'
Stats
seems to have been protected as _Stats
, what’s the current recommended way to start a view manager, please?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
AttributeError: module 'statsmodels' has no attribute 'stats'
I'm running statsmodels 0.13.2 on macOS Monterey v 12.4 with M1 chip. I'm trying to do a z-test with statsmodels.stats.weightstats.ztest.
Read more >Module 'scipy' has no attribute 'stats' ( Solved )
In this entire tutorial, you will know how to solve the issue of the module 'scipy' having no attribute 'stats'. What is the...
Read more >opencensus-ext-azure - PyPI
The Azure Monitor Metrics Exporter allows you to export metrics to Azure Monitor. from opencensus.ext.azure import metrics_exporter from opencensus.stats import ...
Read more >How to use the opencensus.common.utils.to_iso_str function ...
assertRaises(AttributeError): span_data.name = 'child' with self. ... census-instrumentation / opencensus-python / tests / unit / stats / test_view_data.py ...
Read more >Monitor Python applications with Azure Monitor - Microsoft Learn
Instrument with OpenCensus Python SDK with Azure Monitor exporters ... OpenCensus.stats supports four aggregation methods but provides ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not sure if having multiple instances of
Stats
/ViewManager
would be preferable. Having a global variable and allView
s registered through that one instance makes it so that we do not have to have additional configuration api as part of the metrics pipeline. For example, if I have multiple ViewManagers, and I add different views for each of them, how would I know which ones to pull from to export metrics? I would have to “attach” ViewManagers to exporters. With only one ViewManager instance, when I export I will only need to collect metrics from only one source.@rpavlov Can you provide an example?