mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
# Backport This will backport the following commits from `main` to `8.18`: - [[Stack Monitoring] New FTR for "view logs" link (#208351)](https://github.com/elastic/kibana/pull/208351) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Valentin Crettaz","email":"valentin.crettaz@elastic.co"},"sourceCommit":{"committedDate":"2025-03-12T22:35:28Z","message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","Team:Monitoring","release_note:skip","Feature:Stack Monitoring","FTR","v8.18.0","v8.17.2","v9.1.0"],"title":"[Stack Monitoring] New FTR for \"view logs\" link","number":208351,"url":"https://github.com/elastic/kibana/pull/208351","mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.2","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208351","number":208351,"mergeCommit":{"message":"[Stack Monitoring] New FTR for \"view logs\" link (#208351)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/202675\n\nA [recent bug](https://github.com/elastic/kibana/issues/199902) broke\nthe Stack Monitoring UI only if/when logs were present. Functional test\ncoverage was lacking to detect such a situation.\n\nThis PR adds some functional test coverage to make sure that the \"View\nlogs\" link in Stack Monitoring works whenever logs are available,\nwherever logs can be visible, i.e. in the cluster overview page, the\nnode details page and the index details page.\n\n### Checklist\n\n- [X] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"c218f4239a10dd7b0cd4aa24e0a627f9d779d94c"}}]}] BACKPORT--> Co-authored-by: Valentin Crettaz <valentin.crettaz@elastic.co> |
||
---|---|---|
.. | ||
action_task_params | ||
actions | ||
alerting/8_2_0 | ||
alerts | ||
alerts_legacy | ||
asset_criticality | ||
auditbeat | ||
beats/list | ||
canvas/logstash_lens | ||
cases | ||
dashboard/async_search | ||
data/search_sessions | ||
dlstest | ||
endpoint | ||
entity | ||
event_log_legacy_ids | ||
event_log_multiple_indicies | ||
filebeat | ||
fleet | ||
getting_started/shakespeare | ||
graph/secrepo | ||
hybrid | ||
infra | ||
kubernetes_security/process_events | ||
large_arrays | ||
lens | ||
lists | ||
logstash/example_pipelines | ||
logstash_functional | ||
maps/data | ||
ml | ||
monitoring | ||
observability | ||
observability_logs_explorer/data_streams | ||
packetbeat | ||
pre_calculated_histogram | ||
reporting | ||
rule_exceptions | ||
rule_keyword_family | ||
rule_registry | ||
rules_scheduled_task_id | ||
security | ||
security_solution | ||
session_view | ||
signals | ||
task_manager_removed_types | ||
task_manager_tasks | ||
upgrade_assistant/reindex | ||
uptime | ||
visualize/default |