Skip to content

[Logs UI] Shorten the logs ML job ID prefixes #47477

@weltenwort

Description

@weltenwort

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-rate Since 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

  • The id assigned to jobs is shortened to logs-${spaceId}-${sourceId}-rate.
  • The id assigned to a datafeed matches the job id.
  • Jobs that were created before this change are still handled correctly.

Metadata

Metadata

Labels

Feature:Logs UILogs UI featureTeam:obs-onboardingObservability Onboarding Teamimpact:highAddressing 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 issue

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions