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

"Global" values calculation #2504

Closed
noamgal opened this issue Jan 1, 2015 · 4 comments
Closed

"Global" values calculation #2504

noamgal opened this issue Jan 1, 2015 · 4 comments
Labels
Feature:elasticsearch Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed

Comments

@noamgal
Copy link

noamgal commented Jan 1, 2015

Currently it's possible to get "global" metrics values (Such as unique locations or num of unique users for example).
But if I can't do any calculations of different global values (For example I would like to calculate average locations num for all users: sum of unique locations / sum of unique users), only possible getting some average value of number of documents.
This calculated statistics is missing and is very important.
Above relates to metrics and data tables.
@rashidkpc
Copy link
Contributor

This feature is not supported by elasticsearch, thus we can not provide it in Kibana

@noamgal
Copy link
Author

noamgal commented Jan 5, 2015

Not sure if I was clear enough in my previous description:
My desired calculation is based upon 2 different supported elasticsearch calculations:
just division of 2 values (such as sum or count of unique field).

Both values are supported in elasticsearch (and kibana), can't kibana wait to get both values and do the division?

Thanks,
Noam

@rashidkpc
Copy link
Contributor

Kibana does not perform calculations of this nature, this is something we would want to see supported in Elasticsearch. At that point we could look into bringing support for it into Kibana.

@thomasneirynck thomasneirynck added Feature:Visualizations Generic visualization features (in case no more specific feature label is available) triage_needed labels Aug 14, 2018
@timroes timroes added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Sep 16, 2018
@timroes
Copy link
Contributor

timroes commented Mar 4, 2021

Superseeded by #91087

@timroes timroes closed this as completed Mar 4, 2021
e40pud added a commit that referenced this issue Dec 1, 2023
@e40pud @marshallmain
@XavierM @kibanamachine @semd
[Security Solution][Alerts] Alert (+Investigation) User Assignment (#…
1ebdbc3 
…2504) (#170579)

## Summary

With this PR we introduce a new Alert User Assignment feature:
- It is possible to assign a user/s to alert/s
- There is a new "Assignees" column in the alerts table which displays
avatars of assigned users
- There is a bulk action to update assignees for multiple alerts
- It is possible to see and update assignees inside the alert details
flyout component
- There is an "Assignees" filter button on the Alerts page which allows
to filter alerts by assignees

We decided to develop this feature on a separate branch. This gives us
ability to make sure that it is thoroughly tested and we did not break
anything in production. Since there is a data scheme changes involved we
decided that it will be a better approach. cc @yctercero

## Testing notes

In order to test assignments you need to create a few users. Then for
users to appear in user profiles dropdown menu you need to activate them
by login into those account at least once.


https://github.com/elastic/kibana/assets/2700761/8eeb13f3-2d16-4fba-acdf-755024a59fc2

Main ticket elastic/security-team#2504

## Bugfixes
- [x] elastic/security-team#8028
- [x] elastic/security-team#8034
- [x] elastic/security-team#8006
- [x] elastic/security-team#8025

## Enhancements
- [x] elastic/security-team#8033

### Checklist

- [x] Functional changes are hidden behind a feature flag. If not
hidden, the PR explains why these changes are being implemented in a
long-living feature branch.
- [x] Functional changes are covered with a test plan and automated
tests.
  - [x] #171306
  - [x] #171307
- [x] Stability of new and changed tests is verified using the [Flaky
Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner).
- [x]
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4091
- [x] Comprehensive manual testing is done by two engineers: the PR
author and one of the PR reviewers. Changes are tested in both ESS and
Serverless.
- [x] Mapping changes are accompanied by a technical design document. It
can be a GitHub issue or an RFC explaining the changes. The design
document is shared with and approved by the appropriate teams and
individual stakeholders.
   * elastic/security-team#7647
- [x] Functional changes are communicated to the Docs team. A ticket or
PR is opened in https://github.com/elastic/security-docs. The following
information is included: any feature flags used, affected environments
(Serverless, ESS, or both). **NOTE: as discussed we will wait until docs
are ready to merge this PR**.
   * elastic/security-docs#4226
* elastic/staging-serverless-security-docs#232

---------

Co-authored-by: Marshall Main <marshall.main@elastic.co>
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:elasticsearch Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@timroes @rashidkpc @thomasneirynck @noamgal