-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Logs UI] Shorten the logs ML job ID prefixes #47477
Copy link
Copy link
Closed
Labels
Feature:Logs UILogs UI featureLogs UI featureTeam:obs-onboardingObservability Onboarding TeamObservability Onboarding Teamimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.Addressing this issue will have a high level of impact on the quality/strength of our product.needs-refinementA reason and acceptance criteria need to be defined for this issueA reason and acceptance criteria need to be defined for this issue
Metadata
Metadata
Assignees
Labels
Feature:Logs UILogs UI featureLogs UI featureTeam:obs-onboardingObservability Onboarding TeamObservability Onboarding Teamimpact:highAddressing this issue will have a high level of impact on the quality/strength of our product.Addressing this issue will have a high level of impact on the quality/strength of our product.needs-refinementA reason and acceptance criteria need to be defined for this issueA reason and acceptance criteria need to be defined for this issue
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
The static parts log rate job IDs should be as short as possible.
Rationale
The log rate jobs are assigned human-readable IDs that contain the static parts as well as the Kibana space and logs source IDs:
kibana-logs-ui-${spaceId}-${sourceId}-log-entry-rateSince the Kibana space ID is set by the user, there is a risk of exceeding the 64-character limit on the length of the ML job ID. Reducing the lengths of the static parts can reduce that risk by leaving more room for the user-defined space ID.In the long term the space-awareness of ML jobs will remove the necessity for including the space ID in the job ID.
Because the id is used to find the jobs belonging to a source config, this will be a breaking change.
Acceptance criteria
logs-${spaceId}-${sourceId}-rate.