Comments (5)
The logger's job is to accumulate the logs from the different services and send them to the azure storage.
This means that if I deploy a service and try to get the logs for one of the specific containers created because of that service, I will get the following error:
$ docker logs b8dd7af5ace8
"logs" command is supported only for "json-file" and "journald" logging drivers (got: syslog)
You could get duplicate logs, if logspout also captured the logs from the editions_logger
container, as it does print to stdout what it received for that host.
Aka doing:
$ docker logs editions_logger
Will output the logs it received from other containers on that host.
This bit from the logspout docs is interesting:
logspout will gather logs from other containers that are started without the -t option and are configured with a logging driver that works with docker logs (journald and json-file)
Since the logging driver use doesn't work for docker logs
, I'm unsure as to what you're collecting or what your setup looks like; but feel free to share how you have logspout setup to provide you with more info.
from for-azure.
I like to collect logs directly from my containers -- that way my logs have the container information as context. In order to make this happen, I start up each of my services with --log-driver=json-file
, which makes the logs collectable by logspout. This all works perfectly.
Based on your explanation, presumably everything that is being logged by every container not explicitly started with --log-driver=json-file
is being collected by editions-logger, and since editions-logger is logging to standard output and using the json-driver backend, the logs received here are also being sent by logspout to my logging backend.
So if I'm understanding correctly, the good bit is that there won't be duplicates, because containers that I have explicitly set the log driver for won't ever be seen by editions_logger. Everything else gets sent to editions_logger, and then from there it gets written to Azure storage as well (currently) to my logging backend via logspout.
I created issue gliderlabs/logspout#258 for adding container exclusions to logspout -- this would probably be the best solution to allow me to avoid sending logs collected by editions_logger to my logging backend, if I want to turn that off.
If all of the above makes sense, feel free to close this! Thanks.
from for-azure.
@rocketraman that's exactly right! I didn't know that logspout couldn't exclude certain containers.
I also opened an internal ticket to provide an option to opt-out of the storage-account logging feature.
I'll close the issue but feel free to add comments (or re-open it) if needed.
from for-azure.
Any word on the opt-out of the built in log forwarder? Seems like it's hogging the syslog daemon which makes integration with external logging services difficult.
from for-azure.
@pewallin Should be out with our next stable release
from for-azure.
Related Issues (20)
- Newly provisioned swarm is not working as swarm is not initialized. HOT 5
- Cloudstor plugin not enabled in newly provisioned swarm HOT 11
- Cannot SSH into node after VM restart - no agent container HOT 3
- waagent.log is not rotating 18.03.0-ce HOT 1
- tcp4 / tcp port not being exposed/mapped to running container after it's been in use before
- Not able to share cloudstor azure named volumes across multiple containers on same host HOT 12
- Docker logs not moving to storage accounts instead kept on Disk. HOT 3
- how to enable auto-scaling for swarm-worker-vmss on the basis of Memory usage
- Cloudstor: Prevent deletion of underlying Azure file share when docker volume is removed. HOT 2
- Fail to deploy Docker for Azure HOT 3
- Unable to SSH into Manager VMSS's after upgrading the instance(s) to the last mode on Azure portal HOT 2
- Project no longer supported? HOT 10
- Mongodb failed to run with persisted volume with cloudstor plugin. HOT 2
- Enable hard link support in cloudstor:azure
- Cannot restart docker daemon on management nodes
- VMSS restart hangs indefinitely at creating .ssh directory
- Error response from daemon: plugin cloudstor:azure already exists
- Storage account
- Can't connect to my Azure Docker Image BDD from SQL Management Studio
- Does not work at all
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from for-azure.