Skip to content
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

[Automatic Import] Use Data stream name for data_stream.dataset value in input manifests #201478

Open
ebeahan opened this issue Nov 22, 2024 · 1 comment
Labels
enhancement New value added to drive a business result Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team

Comments

@ebeahan
Copy link
Member

ebeahan commented Nov 22, 2024

Describe the feature:

Use the user-supplied data stream name as the data_stream.dataset value instead of a generic placeholder.

Describe a specific use case for the feature:

Custom Fleet integrations default to a generic dataset (data_stream.dataset) value - something like http_endpoint.generic. Since users configure their own options for a custom integration, this workflow makes sense.

Elastic integrations, on the other hand, default to a predetermined naming convention based on the integration package + datastream name for dataset - something like github.issues for the issues data stream from the Github package.

@ebeahan ebeahan added enhancement New value added to drive a business result Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team labels Nov 22, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-scalability (Team:Security-Scalability)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team
Projects
None yet
Development

No branches or pull requests

2 participants