Merge upstream changes #5
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Case corrections. This way it also works with Latin1_General_BIN collation SQL Server.
Various CentOS/Redhat flavours require a tty to be allocated when using sudo. Document how to by-pass this requirement per user.
Also add safeguards in case of crazy amount of queues/topics/subscribers
The builds must not rely on sudo from now on. That means either fetching pre-compiled binaries from upstream or fetching the sources and compiling directly on the build machine. However, as the released upstream sources do not change we can benefit from the caching system and cache the binaries once we have them. All these software are in $INTEGRATIONS_DIR Introduction also of running the integration tests against different versions of the software described in the build matrix. Also a bit of documentation on how to use the new test system. + Several more fixes of the test suite codebase
Adjust the test to conditions for postgres needed to be >= 9.1 and >= 9.2
Add proxy settings on agent info display
When using an external Elasticsearch cluster, we should tag the hostname by the node's given hostname in the stats output. Otherwise we end up using only the last node's values because each subsequent gauge metric will stomp on the one before it. The test is updated to make sure the hostname given in the stats (which should be the FQDN) matches what we output at the end. Finally, this change also splits the cluster health metrics into a seperate dict. This has two benefits: (a) it will clean up a lot of debugging logging and extra work for `_process_health_data` and (b) makes it easy to check against just the stats metrics for tests.
[elasticsearch] Fix host tagging for external clusters.
…oring Refactor activemq_xml check
[ci/tests] New build. New Infrastructure. New Flavors
subprocess.PIPE is limited in size because the data is buffered in memory. When running the Agent on a host that has many containers, the number of mountpoints can be very large. Because of this buffer limit, the shell call can hang for these huge outputs. To workaround this, we will write the output to a temporary file and read it from there. This is a "quick" fix for a specific case and there might be a better general approach. But either way, we will still need to handle the case of large outputs from our subprocess commands otherwise the whole Agent collector simply hangs. ref: http://thraxil.org/users/anders/posts/2008/03/13/Subprocess-Hanging-PIPE-is-your-enemy/
Use a temporary file for df output to avoid PIPE limits.
[snmp] configuration option to ignore non-increasing OIDs
[marathon] service checks and improvements
Update sqlserver.py
[leo@datadoghq.com: Rebased to pass CI, cosmetic changes]
[netowrk] freebsd: '-W' in netstat for full names
[leo@datadoghq.com] rebased for new CI skeleton and no sudo use Squashed a bunch of commits too
Add check for fluentd
[postfix] Document requiretty requirement on Redhat/Centos for using sudo.
Merge upstream changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.