kibana
https://github.com/elasticsearch/kibana
JavaScript
:bar_chart: Kibana analytics and search dashboard for Elasticsearch
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
JavaScript not yet supported572 Subscribers
View all SubscribersAdd a CodeTriage badge to kibana
Help out
- Issues
- Inconsistent dataview refresh for new fields across Kibana apps
- New APM telemetry collection task for EDOT SDKs
- Unclear validation error for required configuration options
- [Security Solution] Rules without customizations are marked as conflicting on rule type change
- [@kbn/config-schema] Ability to define distinct input and output types
- Scout test cases for Security
- Failing test: Chrome X-Pack UI Functional Tests.x-pack/platform/test/functional/apps/discover/group1/reporting·ts - discover - group 1 Discover CSV Export Generate CSV: new search generates a large export
- Failing test: Jest Integration Tests.x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/step_define_rule/__integration_tests__ - StepDefineRule query makes sure "threat_match" rule has "*:*" kuery when switched from "eql" rule type without user input
- Failing test: Jest Integration Tests.x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/step_define_rule/__integration_tests__ - StepDefineRule query makes sure "threat_match" rule has "*:*" kuery when switched from "esql" rule type without user input
- Failing test: Jest Integration Tests.x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation_ui/components/step_define_rule/__integration_tests__ - StepDefineRule query makes sure "threat_match" rule has "*:*" kuery when switched from "threshold" rule type without user input
- Docs
- JavaScript not yet supported