-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Fleet] Synthetics data streams do not show up in data streams list #102651
Comments
Pinging @elastic/fleet (Team:Fleet) |
@ruflin traces and synthetics are part of our search pattern:
In your testing were the data streams actually populated in ES and just missing from Fleet? |
I was able to replicate this and found that although Fleet is finding the synthetics data streams correctly, in the end they get filtered out because the documents do not contain
cc @dominiqueclarke, sending this your way per our discussion. Here is an example HTTP synthetics document I ingested, note the absence of any
|
Pinging @elastic/uptime (Team:uptime) |
It is important that heartbeat / synthetics sets the data_stream.* fields. @andrewvc can you take this on? |
@ruflin. Andrew is away for a few weeks. I am investigating the issue, but we'll likely need a beats contributor to investigate why the fields are not being indexed by heartbeat. Can we clarify the priority for this resolution? Is this needed for 7.14? That'll help us coordinate and figure out if we'll need to look for outside help while Andrew is away. |
How is synthetics currently filtering down the data? I assume as this issue did not bubble up yet, it is not prefiltering on the There are at least 2 ways to add these fields: Elastic Agent magically adds a processor or heartbeat adds the fields. As Heartbeat knows which fields with values to add, this should be right place. Who is working on heartbeat during the time Andrew is out? |
@vigneshshanmugam is this anything you'd be able to look at on the Heartbeat side (/cc @shahzad31)? Failing that, it would be if either @blakerouse or @urso have any capacity to help here? |
Did a quick look at the code and seems like Heartbeat already has support for data streams and it feels like we are missing the configuration from the integrations side. I am not a heartbeat expert and might be wrong. Here is the PR for the Data streams support - elastic/beats#24223 And I did a quick test on my local and can confirm it works as expected.
|
@vigneshshanmugam and I synced offline and confirmed that, while we do have support for data streams, the data stream documents are missing the necessary fields. These fields, as far as I am aware, will need to be indexed on the heartbeat side as the integration package is passing information for all the necessary fields within the integration policy. |
We were able to verify that the documents were missing the |
If the fields are now shipped by heartbeat directly, I don't think any changes to the integrations are needed. Can you test that also a change to the namespace works as expected? |
I did a test with the fix using an example integration policy @dominiqueclarke has sent over to me and it works as expected. Integration Policy- id: 211f80e4-1903-4cf5-aa3b-df683ab2722e
name: Sample Monitor 3/3
revision: 1
type: synthetics/http
use_output: default
meta:
package:
name: synthetics
version: 0.1.46
data_stream:
namespace: default
streams:
- id: synthetics/http-http-211f80e4-1903-4cf5-aa3b-df683ab2722e
name: Sample Monitor 3/3
type: http
data_stream:
dataset: http
type: synthetics
urls: 'http://elastic.co'
service.name: null
schedule: '@every 5s'
timeout: 1600
max_redirects: 0
proxy_url: ''
tags:
- tag1
- tag2 Also the fix is landed in master and also back ported. |
I'm using the synthetics integration and it ships data to the
synthetics-*-*
data streams. But these data streams do not show up in the data streams page in Fleet, only logs and metrics.My assumption is that it missing in the filter.
traces
from APM might also be missing.We should ensure to somehow keep this in sync with the spec supported prefixes: https://github.com/elastic/package-spec/blob/master/versions/1/data_stream/manifest.spec.yml#L121
Version: 7.13.0
The text was updated successfully, but these errors were encountered: