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.

Sign up for GitHub

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

Jump to bottom

[Ingest] Expose number of policies from data source #53059

Closed
jen-huang opened this issue Dec 14, 2019 · 1 comment
Closed

[Ingest] Expose number of policies from data source #53059

jen-huang opened this issue Dec 14, 2019 · 1 comment
Assignees
@jen-huang
Labels
Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@jen-huang
Copy link
Contributor

jen-huang commented Dec 14, 2019 •
edited
Loading

Relates to #52963

In order to detect if a data source is unassigned, we should expose the number of policies a data source is assigned to. This will affect GET one data source and GET list of data sources API endpoints.
@jen-huang jen-huang added Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Feature:Fleet Fleet team's agent central management project labels Dec 14, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest (Feature:EPM)

This was referenced Dec 16, 2019
Merged
Merged
@jen-huang jen-huang self-assigned this Dec 19, 2019
@jen-huang jen-huang added the Team:Fleet Team label for Observability Data Collection Fleet team label Mar 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jen-huang jen-huang

Labels
Feature:EPM Fleet team's Elastic Package Manager (aka Integrations) project Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jen-huang @elasticmachine