forked from elastic/beats
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updating fork from remote master #1
Merged
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
* Stop following symlinks. Previously symlinks were followed. This had the consequence if a symlink and the file itself existed, the file was read twice. Now symlinks are not followed anymore. This closes #1686 * Add symlink for windows * Turn around params * Remove symlink comment * Fix for windows symlink
The issue with the trailing slash is that the code considers that a "path", so the real path is ignored when configured. Fixes #1779.
* Add generation script for packer files These script can be used in all community beats to generate the dev-tools folder with the docker files. This allows to also use these scripts in the generator in a second step. This simplifies getting started with a beat (less files) but still offers all the possibilities. In addition, it allows us to update / improve these files over time and external beats can fetch the updates again through overwriting if needed. * Fix docs about packer
The generator is now split up in two parts. First part just creates the empty beat, in a second step the metricset set is created with the metricset generator script. * create_metricset.py script was updated to fulfill the new requirements. Paths were added * Beat now expects beats to be in the GOPATH * dev-tools were added * Build added to travis * Updated python build commands with virtualenv * Extend README with new commands
* Introduce dialer collecting transport stats * Output IO stats introduce counters (bytes send/received and errors) to elasticsearch, logstash and redis outputs
This reduces the duplicated content and uses links instead. This should also reduce the number of conflicts in PRs.
The dev-tools folder is now not shipped by default with the generator anymore. To created it and run the packaging process, `make pack` must be used. Further changes: * Remove GO15VENDOREXPERIMENT as not needed anymore with 1.6 * Remove not needed files in generators because now repo is in the beats repo * For beat generator, separate test and test-build * Add beat template tests to travis build * Remove glide.yml from metricset generator as it will be generated automatically * Temporarely remove versioning from generated beats as required for tests to have most recent version
* Create MetricSet guide is based on generator * Simplified guide for module files * Update Metricbeat dev guide with README linking
It was set to use snapshots as a temporary (heh) workaround for the time when squeeze got removed from the main repos but wasn't yet added to the archive.
This separates the config options from prospector and harvester and uses ucfg for it. Further changes: * Only start new harvester if offset changed -> more efficient if file didn't change
Like this the beat generated by beats generator and metricset generator is the same. This also gives an example on how state should be handled in a metricset. The docs were updated with more details on how to create a Metricset. FAQ was added
* Combine separate es bulk api implementations Until now (*Connection).Bulk and (*Client).PublishEvents seem to be based on different implementations for dealing with bulk API. Only the former being tested by unit and integration tests. This refactoring removes duplicate logic.
Some nfs clients (osx) do not set machinename in rpc credentials. As a result, visualizations based on it will show empty value. Set nfs client's ip address as machinename if not provided. Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Implement ucfg for prospector and harvester
Automatically convert all fields which were defined as integer to long to prevent potential overflow issues with integer. This should not have an affect on storage need.
* Add dashboard screenshot for Apache server status
I have found following changes very useful while playing with exporting of dashboards: - update requirements for python env (elasticsearch) - fix typo and add python env for export-dashboards target in makefile - fix 'print' call in export_dashboards script
* Update to most recent LS build * Update builds to alpha3
I quick went through the TODO's and fixed the easy ones or removed unnecessary ones. * Remove debug log messages as it spams the log file. This happens every time an event or update is published
It was temporary disabled because of outdated kibana files. * Old redis and mysql dashboards were now removed * Add Dashboard screenshot for apache to docs
packetbeat: nfs: set rpc machinename to ip address if not set
* Fixes #1808. * x86_64 is more common in config management tools, so it is easier to work with. * The DEB/RPM still use their recommended arch names.
This makes it easier for external runners (like gradle) to report progress on our builds.
* Update changelog
* Contains the status metricset, reporting parts of the `db.serverStatus()` output. The locks and metrics sections are not yet reported. * Includes docs, basic integration tests, and basic system tests
Quick Cleanup
Fix doc build because of missing [float]
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.