Highlights
- Arctic Code Vault Contributor
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign upPinned
1,298 contributions in the last year
Activity overview
Contribution activity
November 2020
Created 12 commits in 3 repositories
Created a pull request in elastic/integrations that received 11 comments
Updating dependency on elastic-package
What does this PR do?
This PR updates the dependency on elastic-package for changing the location of where test reports are stored (elastic/elastic…
Opened 13 other pull requests in 3 repositories
elastic/elastic-package
6
merged
1
open
elastic/beats
5
merged
- Cherry-pick to 7.10: Add documentation for CloudFoundry application metadata persistent cache (#22669)
- Cherry-pick to 7.x: Add documentation for CloudFoundry application metadata persistent cache (#22669)
- Add documentation for CloudFoundry application metadata persistent cache
- Cherry-pick to 7.10: Adding Kafka version 2.2 (#22328)
- Cherry-pick to 7.x: Adding Kafka version 2.2 (#22328)
elastic/package-spec
1
open
Reviewed 32 pull requests in 4 repositories
elastic/elastic-package 10 pull requests
- Update Elastic stack
- README: remind about GOPATH/PATH
- Defer cleanup flag
- Build command: render README files
- Export dashboards from Kibana
- Add support for dynamic fields
- Add pattern matching to field values
- Update package-spec (validate Kibana filenames)
- Fix: do not stop other containers than selected
- Store test reports in build/test-results/ folder
elastic/package-spec 9 pull requests
- Validate JSON properties with relative-path format
- Define README file template in _dev
- Add ignored_fields to test config
- Add data stream type "traces".
- Add pattern property to field
- Add support for top level configuration
- Fix: invalid fields file regex
- Verify: no ECS suffix for Kibana object filenames
- Add `metric_type` and `unit` to fields.yml spec
elastic/beats 8 pull requests
- [Metricbeat/Kibana/stats] Enforce `exclude_usage=true`
- Avoid sending non-numeric floats in cloud foundry integrations
- Make elasticsearch/ccr metricset work for Stack Monitoring without xpack.enabled flag
- Modify HTTP helper to not require a base Metricset
- Make elasticsearch/index_recovery metricset work for Stack Monitoring without xpack.enabled flag
- Make elasticsearch/cluster_stats metricset work for Stack Monitoring without xpack.enabled flag
- Make elasticsearch/enrich metricset work for Stack Monitoring without xpack.enabled flag
- Make elasticsearch/index metricset work for Stack Monitoring without xpack.enabled flag
Created an issue in elastic/beats that received 7 comments
Investigate which fields can be dropped from `logstash-xpack` events
We have been seeing a few issues with memory consumption in Metricbeat when the logstash-xpack module attempts to monitor very large Logstash pipel…