Skip to content

Issues: notmyname/slogging

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

15 Open 15 Closed
15 Open 15 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

check for swift_source when processing an access log line
#63 opened Feb 16, 2015 by notmyname
unify log_line_parser
#62 opened Feb 16, 2015 by notmyname
detect log type
#45 opened May 14, 2012 by notmyname
Allow filter access log delivery by swift.source
#43 opened Apr 26, 2012 by btorch
unittests don't work
#35 opened Mar 1, 2012 by dpgoetz
1
change print in log_common collate_worker to log.exception
#34 opened Feb 27, 2012 by dpgoetz
internal_proxy needs to use memcached
#32 opened Feb 17, 2012 by notmyname
refactor to remove internal_proxy
#31 opened Feb 17, 2012 by notmyname
ignore log lines without valid account name in log_processor
#30 opened Jan 31, 2012 by dpgoetz
1
duplicate entries in csv
#22 opened Nov 2, 2011 by mossburg
4
pass config section name to the implementing class
#15 opened Aug 16, 2011 by notmyname
Module netifaces was already imported
#14 opened Aug 16, 2011 by btorch
Have log uploader send Etag to verify success of upload.
#7 opened Aug 2, 2011 by dpgoetz
Add timestamps to the container and account stats
#4 opened Jul 14, 2011 by letterj
container stats are not uploaded due to one container db file can not be opened
#2 opened Jul 6, 2011 by dpgoetz
@dpgoetz
ProTip! Type g i on any issue or pull request to go back to the issue listing page.