-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update python3 fix auditbeat and dashboards #15807
Merged
jsoriano
merged 37 commits into
elastic:feature/python3
from
jsoriano:update-python3-fix-auditbeat-and-dashboards
Jan 24, 2020
Merged
Update python3 fix auditbeat and dashboards #15807
jsoriano
merged 37 commits into
elastic:feature/python3
from
jsoriano:update-python3-fix-auditbeat-and-dashboards
Jan 24, 2020
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
* Mask password is string representation of config * Rename method * Adding unit test * Use const for module config password setting name * Using common.DebugString * Simplifying * Removing now-invalid unit test * Removing now-unnecessary const * Refactoring: moving debug-related var and func to common file * Refactoring: rename from black list to mask list * Implement fmt.Formatter for common.MapStr * Reintroduce debug statement * Make MarshalLogObject always filter MapStr object for logging purposes * Refactoring: renaming to be bit more generic * Forgot to add license header to new file * Fixing verb syntax
* Adding monitoring.cloud.* settings to reference files * Missed winlogbeat somehow * Missed x-pack/winlogbeat
* Fix panic: don't send events if client is nil * Use mutex * Add CHANGELOG entry * Rename changelog entry * Fix: changelog * Temporarily use specific logstash release
* Fix changelog
it uses APM pipeline library configured in the instance
* AWS Lambda: downgrade Kibana dashboard * Downgrade other AWS dashboards * Log command error if setup dashboards fails * Another downgrade
From the README of goracle: > Goracle is deprecated because of naming (trademark) issues. From now on we are using github.com/godror/godror instead.
… to reuse (elastic#15503) * Move pdh query to shared location * Update changelog * Fix make update * mage fmt * fix changelog
Remove datasource option from SQL module. This option was intended to set the DSN of a database connection, and we were ignoring the hosts setting. In other SQL modules we are using the values in hosts as DSNs, do here the same for consistency. Host is redacted when we cannot parse it as it can contain passwords. StandardizeEvent is exposed in mbtest.Fetcher interface so we can more easily check contents of events in tests. Add integration tests of the module with MySQL and PostgreSQL. Add real data.json with data from MySQL and PostgreSQL.
…c#15643) * add service metricset to ref docs * update xpack docs
* add NaN check to docker/diskio * return 0
since 7.0 elasticsearch is using java.time style patterns. YYYY becomes yyyy
* [DOCS] Add missing config options to shared file * Add fixes from review * Run mage fmt update to fix build error
…15587) Allow for multiple status codes in config. Fixes elastic#13595
## What does this PR do? This PR updates the dependency `github.com/godror/godror` to v0.10.4. ## Why is it important? Packaging of Metricbeat fails due to the issue in the `godror` version we are currently using. See more about the problem: godror/godror#8
* Collect normalized CPU percentages by default * Adding CHANGELOG entry * Updating x-pack/metricbeat
* Add optional AWS shared_credential_file to all s3 input modules * Made AWS credential_profile_name optional for all s3 input modules Fixes elastic#15652
Mapping was defined at the metricset level, but it should be defined at the module level. Add system test to earlier detect this kind of issues. Also add validation so driver and sql_query options cannot be empty. Fetch was reusing some maps when building the event, what was causing mixed data in events and panics on queries with lots of rows. Fixes elastic#15736
…c#15586) * Building functionbeat providers with specific GOOS and GOARCH * Fix: os changed to linux for aws functionbeat provider * Disabling CGO in functionbeat because it is not used
Remove spurious strings in fields definitions of generic modules caused by how these yaml files are indented and concatenated.
…5639) * [Heartbeat] Fix excessive memory usage when parsing bodies In 7.5 we introduced a regression where we would allocate a 100MiB buffer per HTTP request. This change fixes that to stream data instead.
* Set event.outcome based on googlecloud audit log output
* ci: add apm beats update pipeline multibranch job * fix: force execution on comment trigger * Update .ci/apm-beats-update.groovy * Update .ci/apm-beats-update.groovy * Update .ci/apm-beats-update.groovy * Delete apm-server-update-beats.sh
* add redis and kafka out * add cloud output * add changelog
Documentation and sample reference configuration still states that the agent version is appended to the default policy name configured via setup.ilm.policy_name. With 7.6 the version is removed from the default.
…ic#15771) This is a tentative workaround for the problems in Auditbeat's system/socket dataset when run under 5.x kernels. On older kernels, we could rely on dereferencing a NULL or invalid pointer returning zeroed memory. However, seems that in the tested 5.x kernels is not the case. Dereferencing a NULL pointer returns bogus memory, which causes some wrong codepaths to be taken in a couple of kprobes defined by the dataset. This so far seems only to affect udp_sendmsg and udpv6_sendmsg, which caused it to attribute traffic to bogus IP addresses. In turn this caused the test-connected-udp system tests to fail.
…auditbeat-and-dashboards
This was referenced Jan 24, 2020
andrewkroh
approved these changes
Jan 24, 2020
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.
Update python3 branch with master to bring the fixes for auditbeat tests
and for versions in x-pack dashboards.