-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Actions] Fixed actions telemetry for multiple namespaces usage #114748
[Actions] Fixed actions telemetry for multiple namespaces usage #114748
Conversation
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
@YulNaumenko I'm not able to reproduce this. I have three rules, each with a server log connector in three separate spaces and I'm not seeing any errors in the Kibana server log when I access https://localhost:5601/api/stats?extended. I even changed the telemetry task to run over and over (instead of once a day) Rule SOs
Kibana server log
|
I am seeing this error: |
Yes , exactly! I'm sorry I didn't include the clarification for this. |
Ah I see. This only happens for non preconfigured connectors |
It's my bad, I didn't put more details on the error you expect to see. @ymao1 described above the error in the console log which appears as the result.
|
For preconfigured it is not relevant because they are space agnostic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great work!
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @YulNaumenko |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This doesn't need to be backported right? Because rules & connectors are still 'single' namespace type in 7.x? I would update the labels to remove v7.16.0
and add backport-skip
After some thinking about it, probably that's better to backport it to be safe the error won't happened in 7.16. The logic was not changed, just the way it is implemented. |
…tic#114748) * [Actions] Fixed actions telemetry for multiple namespaces usage * fixed tests
) (#114923) * [Actions] Fixed actions telemetry for multiple namespaces usage * fixed tests
…mple/introduce-baseline-tests * 'master' of github.com:elastic/kibana: (55 commits) [Fleet] Improve Functionality around Managed Package Policies (elastic#114526) cleanup (elastic#114902) remove stray semicolon (elastic#114969) [Security Solution] Edit host isolation exception IP UI (elastic#114279) [ML] APM Correlations: Round duration values to be used in range aggregations. (elastic#114833) [Index Management] Added `data-test-subj` values to the index context menu buttons (elastic#114900) [Stack monitoring] Fix logstash functional tests for react (elastic#114819) Implement hybrid approach to writing rule execution event logs (elastic#114852) [Detection Rules] Add 7.16 rules (elastic#114939) Fixing exceptions export format (elastic#114920) Clean up inaccurate comments (elastic#114935) chore(NA): fixes a typo on persist_bazel_cache.sh comment (elastic#114943) [ci] Fixes Bazel cache writes (elastic#114915) fix package.json: (elastic#114936) [Controls] Redux Toolkit and Embeddable Redux Wrapper (elastic#114371) [APM] Fixes incorrect index config names (elastic#114901) (elastic#114904) [Workplace Search] Fix button order and remove extra source name label (elastic#114899) [Actions] Fixed actions telemetry for multiple namespaces usage (elastic#114748) docs: fix config names (elastic#114903) Update kibana to EMS 7.16 (elastic#114865) ...
Summary
Current PR fixing the bug in actions telemetry, when connectors and actions were created in multiple spaces.
After making actions saved object 'multiple-isolated', we didn't change the action telemetry task, which used SavedObjects bulkGet method, which has next restrictions for the namespaces search:
That's why for the objects created in non default space, the error message in console was appeared each time the telemetry task was executed.
Steps to reproduce:
Error executing actions telemetry task: TypeError: Cannot read property 'actionTypeId' of undefined.