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

[Security Solution] [Bug] A few entities fail to be assigned the values every time for asset criticality via bulk upload #196975

Open
muskangulati-qasource opened this issue Oct 19, 2024 · 4 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v8.16.0

Comments

@muskangulati-qasource
Copy link

Describe the bug
A few entities fail to be assigned the values every time for asset criticality via bulk upload

Kibana/Elasticsearch Stack version

VERSION: 8.16.0
BUILD: 79314
COMMIT: 5575428dd3aef69366cddb4ccf07a2a26d30ce48

Steps

  1. Kibana version 8.16.0 or above should exist
  2. Navigate to Stack Management >> Alerts and Insights >> Entity Store
  3. Add a file which has multiple entries atleast 21k
  4. Validate it always shows error that a few entries are not assigned the value. However, the reason is not specified

Expected Result
No entities should fail to be assigned the values every time for asset criticality via bulk upload

Screen Recording

Entity.Store.mp4

Test file used
user.txt

Error from network logs


 "errors": [
        {
            "message": "[host.name:ip-172-31-83-81]: version conflict, required seqNo [27862], primary term [2]. current document has seqNo [27871] and primary term [2]"
        },
        {
            "message": "[user.name:root]: version conflict, required seqNo [27880], primary term [2]. current document has seqNo [27882] and primary term [2]"
        },
        {
            "message": "[user.name:root]: version conflict, required seqNo [27897], primary term [2]. current document has seqNo [27902] and primary term [2]"
        },
        {
            "message": "[user.name:root]: version conflict, required seqNo [27908], primary term [2]. current document has seqNo [27912] and primary term [2]"
        },
@muskangulati-qasource muskangulati-qasource added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed labels Oct 19, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@muskangulati-qasource
Copy link
Author

@amolnater-qasource please review!

@amolnater-qasource
Copy link

Reviewed & assigned to @MadameSheema

@muskangulati-qasource muskangulati-qasource added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Entity Analytics Security Entity Analytics Team v8.16.0 labels Oct 19, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:Entity Analytics Security Entity Analytics Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed v8.16.0
Projects
None yet
Development

No branches or pull requests

4 participants