[Observability Onboarding] Show existing data callout in Firehose flow #203072
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
botelastic
bot
added
the
ci:project-deploy-observability
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
mykolaharmash
added
release_note:skip
|
Pinging @elastic/obs-ux-onboarding-team (Feature: Observability Onboarding) |
|
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
|
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
History
|
flash1293
approved these changes
Dec 10, 2024
| return callApi('GET /internal/observability_onboarding/firehose/has-data', { | ||
| params: { | ||
| query: { | ||
| logsStreamName: FIREHOSE_LOGS_STREAM_NAME, |
There was a problem hiding this comment.
This is only checking for cloudwatch logs - are we sure those will always exist if the user went through the flow?
There was a problem hiding this comment.
That's a good catch, thank you! The split in two streams came later and I forgot to update this endpoint. Though, with the latest template there will again be only one stream, I've created a follow up task to use the latest template and adopt the code to use a single firehose stream.
|
Starting backport for target branches: 8.15, 8.16, 8.17, 8.x https://github.com/elastic/kibana/actions/runs/12256747990 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 10, 2024
elastic#203072) Closes elastic#190795 Adds the logic to display a message to the user in case there is already an existing Firehose data in their cluster and to show the identified AWS services in the "Visualize Data" step right away without waiting for the window to loose focus first.  ## How to test 1. Open the Firehose flow 2. Make sure there is no callout and the third step is not active 3. Go to Kibana dev console and ingest some dummy data (see examples bellow) 4. Refresh the page with the Firehose flow 5. make sure there is a callout and the third steps shows the identified AWS service ``` POST logs-aws.apigateway_logs-default/_doc { "@timestamp": "2024-11-25T13:32:01.000Z", "some": 111, "aws.kinesis.name": "Elastic-CloudwatchLogs" } POST metrics-aws.apigateway_metrics-default/_doc { "@timestamp": "2024-11-25T13:31:01.000Z", "agent": { "type": "firehose" }, "aws": { "cloudwatch": { "namespace": "AWS/ApiGateway" }, "exporter": { "arn": "arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J" } }, "cloud": { "account": { "id": "975050175126" }, "provider": "aws", "region": "us-west-2" } } ``` (cherry picked from commit 6cb1430)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 10, 2024
elastic#203072) Closes elastic#190795 Adds the logic to display a message to the user in case there is already an existing Firehose data in their cluster and to show the identified AWS services in the "Visualize Data" step right away without waiting for the window to loose focus first.  ## How to test 1. Open the Firehose flow 2. Make sure there is no callout and the third step is not active 3. Go to Kibana dev console and ingest some dummy data (see examples bellow) 4. Refresh the page with the Firehose flow 5. make sure there is a callout and the third steps shows the identified AWS service ``` POST logs-aws.apigateway_logs-default/_doc { "@timestamp": "2024-11-25T13:32:01.000Z", "some": 111, "aws.kinesis.name": "Elastic-CloudwatchLogs" } POST metrics-aws.apigateway_metrics-default/_doc { "@timestamp": "2024-11-25T13:31:01.000Z", "agent": { "type": "firehose" }, "aws": { "cloudwatch": { "namespace": "AWS/ApiGateway" }, "exporter": { "arn": "arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J" } }, "cloud": { "account": { "id": "975050175126" }, "provider": "aws", "region": "us-west-2" } } ``` (cherry picked from commit 6cb1430)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 10, 2024
elastic#203072) Closes elastic#190795 Adds the logic to display a message to the user in case there is already an existing Firehose data in their cluster and to show the identified AWS services in the "Visualize Data" step right away without waiting for the window to loose focus first.  ## How to test 1. Open the Firehose flow 2. Make sure there is no callout and the third step is not active 3. Go to Kibana dev console and ingest some dummy data (see examples bellow) 4. Refresh the page with the Firehose flow 5. make sure there is a callout and the third steps shows the identified AWS service ``` POST logs-aws.apigateway_logs-default/_doc { "@timestamp": "2024-11-25T13:32:01.000Z", "some": 111, "aws.kinesis.name": "Elastic-CloudwatchLogs" } POST metrics-aws.apigateway_metrics-default/_doc { "@timestamp": "2024-11-25T13:31:01.000Z", "agent": { "type": "firehose" }, "aws": { "cloudwatch": { "namespace": "AWS/ApiGateway" }, "exporter": { "arn": "arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J" } }, "cloud": { "account": { "id": "975050175126" }, "provider": "aws", "region": "us-west-2" } } ``` (cherry picked from commit 6cb1430)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 10, 2024
…ose flow (#203072) (#203566) # Backport This will backport the following commits from `main` to `8.17`: - [[Observability Onboarding] Show existing data callout in Firehose flow (#203072)](#203072) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-10T13:07:11Z","message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding"],"title":"[Observability Onboarding] Show existing data callout in Firehose flow","number":203072,"url":"https://github.com/elastic/kibana/pull/203072","mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203072","number":203072,"mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Dec 10, 2024
…ose flow (#203072) (#203565) # Backport This will backport the following commits from `main` to `8.16`: - [[Observability Onboarding] Show existing data callout in Firehose flow (#203072)](#203072) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-10T13:07:11Z","message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding"],"title":"[Observability Onboarding] Show existing data callout in Firehose flow","number":203072,"url":"https://github.com/elastic/kibana/pull/203072","mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203072","number":203072,"mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Dec 10, 2024
…se flow (#203072) (#203567) # Backport This will backport the following commits from `main` to `8.x`: - [[Observability Onboarding] Show existing data callout in Firehose flow (#203072)](#203072) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-10T13:07:11Z","message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","ci:project-deploy-observability","Team:obs-ux-logs","Feature: Observability Onboarding"],"title":"[Observability Onboarding] Show existing data callout in Firehose flow","number":203072,"url":"https://github.com/elastic/kibana/pull/203072","mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/203072","number":203072,"mergeCommit":{"message":"[Observability Onboarding] Show existing data callout in Firehose flow (#203072)\n\nCloses https://github.com/elastic/kibana/issues/190795\r\n\r\nAdds the logic to display a message to the user in case there is already\r\nan existing Firehose data in their cluster and to show the identified\r\nAWS services in the \"Visualize Data\" step right away without waiting for\r\nthe window to loose focus first.\r\n\r\n\r\n\r\n\r\n## How to test\r\n\r\n1. Open the Firehose flow\r\n2. Make sure there is no callout and the third step is not active\r\n3. Go to Kibana dev console and ingest some dummy data (see examples\r\nbellow)\r\n4. Refresh the page with the Firehose flow\r\n5. make sure there is a callout and the third steps shows the identified\r\nAWS service\r\n\r\n```\r\nPOST logs-aws.apigateway_logs-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:32:01.000Z\",\r\n \"some\": 111,\r\n \"aws.kinesis.name\": \"Elastic-CloudwatchLogs\"\r\n}\r\n\r\nPOST metrics-aws.apigateway_metrics-default/_doc\r\n{\r\n \"@timestamp\": \"2024-11-25T13:31:01.000Z\",\r\n \"agent\": {\r\n \"type\": \"firehose\"\r\n },\r\n \"aws\": {\r\n \"cloudwatch\": {\r\n \"namespace\": \"AWS/ApiGateway\"\r\n },\r\n \"exporter\": {\r\n \"arn\": \"arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J\"\r\n }\r\n },\r\n \"cloud\": {\r\n \"account\": {\r\n \"id\": \"975050175126\"\r\n },\r\n \"provider\": \"aws\",\r\n \"region\": \"us-west-2\"\r\n }\r\n}\r\n```","sha":"6cb14302a1a3fd157d1e1947493a0d0d5f4980f6"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
elastic#203072) Closes elastic#190795 Adds the logic to display a message to the user in case there is already an existing Firehose data in their cluster and to show the identified AWS services in the "Visualize Data" step right away without waiting for the window to loose focus first.  ## How to test 1. Open the Firehose flow 2. Make sure there is no callout and the third step is not active 3. Go to Kibana dev console and ingest some dummy data (see examples bellow) 4. Refresh the page with the Firehose flow 5. make sure there is a callout and the third steps shows the identified AWS service ``` POST logs-aws.apigateway_logs-default/_doc { "@timestamp": "2024-11-25T13:32:01.000Z", "some": 111, "aws.kinesis.name": "Elastic-CloudwatchLogs" } POST metrics-aws.apigateway_metrics-default/_doc { "@timestamp": "2024-11-25T13:31:01.000Z", "agent": { "type": "firehose" }, "aws": { "cloudwatch": { "namespace": "AWS/ApiGateway" }, "exporter": { "arn": "arn:aws:cloudwatch:us-west-2:975050175126:metric-stream/Elastic-CloudwatchLogsAndMetricsToFirehose-CloudWatchMetricStream-Nhb4NhzPdL4J" } }, "cloud": { "account": { "id": "975050175126" }, "provider": "aws", "region": "us-west-2" } } ```
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.
Closes #190795
Adds the logic to display a message to the user in case there is already an existing Firehose data in their cluster and to show the identified AWS services in the "Visualize Data" step right away without waiting for the window to loose focus first.
How to test