Skip to content
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.

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

What is the purpose of telegraf ? #7

Open
filviu opened this issue Jul 19, 2019 · 3 comments
Open

What is the purpose of telegraf ? #7

filviu opened this issue Jul 19, 2019 · 3 comments

Comments

@filviu
Copy link

filviu commented Jul 19, 2019

I'm a bit new to the docker world and I'm trying to wrap my head around it:

Wouldn't this stack only colect metrics from inside the telegraf container?

Thanks!

@thinkingerrol
Copy link

thinkingerrol commented Jan 21, 2020

Purpose of Telegraf is the scheduling of data collectors - standard and custom that you can write.

I found the free tutorial by Mark Takacs to be a great way to understand the Docker world.

By default, a containerized Telegraf would only see data inside the container it is running in. However, Docker allows the mapping of ports and volumes from the host to the container - this is also how data persistency is achieved.

I think you are right that the way docker-compose.yml is currently written, Telegraf wouldn't see anything outside its own container, because no mapping of ports or volumes has been configured (except for the volume which only gives access to the ./telegraf.conf on the host)

telegraf:
  image: telegraf:latest
  container_name: telegraf
  links:
    - influxdb
  volumes:
    - ./telegraf.conf:/etc/telegraf/telegraf.conf:ro

Depending on one's particular monitoring needs, the mapping will have to be extended.

@filviu
Copy link
Author

filviu commented Jan 21, 2020

Thank you, that makes sense.

@OneCricketeer
Copy link

Feel free to close the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants