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

Added some features to the directory check #1041

Merged
merged 2 commits into from
Sep 29, 2014
Merged

Conversation

Osterjour
Copy link
Contributor

Added an individual tag for each file which matched the pattern
Added configuration params to change the tag names (directory and file)

Added configuration params to change the tag names (directory and file)
@remh
Copy link
Contributor

remh commented Jul 18, 2014

Hi @Osterjour thanks for your contribution!

You can't add an individual tag for each file as it would create different histograms from each of these files. Hence, these histograms will be only computed with a single data point and will be meaningless.

Another issue that tagging by file could raise is the fact that it could potentially create too many contexts for those metrics (let's say you have a directory with 10000 files).

Does it make sense ?
Let me know if you have any more questions.

And thanks again for your contribution!

@Osterjour
Copy link
Contributor Author

Hi @remh,

thanks for your message.
I want to achieve a monitoring of (in my case) lock files. Because of this I need to have the age of each file over the time. After your message I think that the histogram is just the wrong data type as I should use gauges per file for it. Does this make sense?
If so how should I implement it in the directory check? Add an option which could be true or false and if true sends the gauges for every file (with the tagging I already have in the code right now)?

What do you think?

Bests,
Markus

@remh
Copy link
Contributor

remh commented Jul 21, 2014

Yes that could be an option.

However you'd need to add some safeguards to prevent from using that option with a directory that has too many files as it could really collect too much data.

@remh remh added this to the 5.1.0 milestone Jul 22, 2014
…ture (default False to make sure we don't change the known behaviour)

- User needs to decide now if he wants the gauges OR the histogram of the whole directory
- Added a hard coded limitation of 20 files per directory (to limit the data)
@Osterjour
Copy link
Contributor Author

What do you think of the latest changes, @remh?
I thought about changing the metric name for the gauges to deliver the histogram always and the file specific gauges as an add-on. Right now it is an either or decision.

@remh
Copy link
Contributor

remh commented Aug 18, 2014

Yes it looks better!
Thanks a lot. I'll review it more carefully and merge.
I'm planning to release it with the Agent version 5.1.0.

@remh remh added the 1 - Ready label Aug 18, 2014
remh added a commit that referenced this pull request Sep 29, 2014
Added some features to the directory check
@remh remh merged commit 99d969f into DataDog:master Sep 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants