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

[ML] AIOps: Renames Explain Log Rate Spikes to Log Rate Analysis. #161764

Conversation

walterra
Copy link
Contributor

@walterra walterra commented Jul 12, 2023

Summary

Part of #161832.

This PR renames the Explain Log Rate Spikes feature to Log Rate Analysis.

  • Renamed references in docs/developer/*
  • Updated docs screenshots
  • Redirect in docs
  • Redirect urls from explain_log_rate_spikes to log_rate_analysis
  • API versioning
  • Renamed navigation links
  • Renamed variable names
  • Renamed file names
  • Renamed i18n ids
  • Renamed breadcrumbs
  • Removed hard coded AIOPS_ENABLED feature flag

Checklist

@walterra walterra self-assigned this Jul 12, 2023
@github-actions
Copy link
Contributor

Documentation preview:

@walterra walterra force-pushed the ml-aiops-rename-explain-log-rate-spikes-to-log-rate-analysis branch 2 times, most recently from 3c5678d to 886ae22 Compare July 13, 2023 08:26
@walterra walterra force-pushed the ml-aiops-rename-explain-log-rate-spikes-to-log-rate-analysis branch from bca93e1 to e60562b Compare July 14, 2023 14:12
@walterra walterra force-pushed the ml-aiops-rename-explain-log-rate-spikes-to-log-rate-analysis branch from e60562b to 69e975b Compare July 17, 2023 09:12
@walterra walterra added :ml v8.10.0 Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis labels Jul 17, 2023
@walterra walterra marked this pull request as ready for review July 17, 2023 10:50
@walterra walterra requested review from a team as code owners July 17, 2023 10:50
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

Copy link
Contributor

@szabosteve szabosteve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for handling all the docs-related changes, too! Docs LGTM!

Copy link
Contributor

@peteharverson peteharverson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from the minor comments, LGTM. Gave it a quick test and couldn't see any leftover references to 'Explain Log Rate Spikes'.

@@ -38,4 +38,4 @@ export const aiopsExplainLogRateSpikesSchema = schema.object({
sampleProbability: schema.maybe(schema.number()),
});

export type AiopsExplainLogRateSpikesSchema = TypeOf<typeof aiopsExplainLogRateSpikesSchema>;
export type AiopsLogRateAnalysisSchema = TypeOf<typeof aiopsLogRateAnalysisSchema>;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit - there is a comment in this file which refers to spikes. I assume that info on dips will be stored in it too?

@@ -170,7 +170,7 @@ export const ExplainLogRateSpikesContent: FC<ExplainLogRateSpikesContentProps> =
title={
<h2>
<FormattedMessage
id="xpack.aiops.explainLogRateSpikesPage.emptyPromptTitle"
id="xpack.aiops.logRateAnalysis.page.emptyPromptTitle"
defaultMessage="Click a spike in the histogram chart to start the analysis."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you decide to leave out drop from this one until the functionality for drops is implemented?

@@ -384,7 +383,7 @@ export const ExplainLogRateSpikesAnalysis: FC<ExplainLogRateSpikesAnalysisProps>
body={
<p>
<FormattedMessage
id="xpack.aiops.explainLogRateSpikesPage.noResultsPromptBody"
id="xpack.aiops.logRateAnalysis.page.noResultsPromptBody"
defaultMessage="Try to adjust the baseline and deviation time ranges and rerun the analysis. If you still get no results, there might be no statistically significant entities contributing to this spike in log rates."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you leaving out drop from this one until the drop functionality is implemented?

@walterra
Copy link
Contributor Author

@peteharverson Thanks for spotting those UI texts, I added a note to the meta issue (#161832) to update them once we add support for drops in the ML plugin page.

"Explain Log Rate Spikes" is an AIOps feature that uses advanced statistical methods to identify reasons for increases in log rates. It makes it easy to find and investigate causes of unusual spikes by using the analysis workflow view.
You are using "Explain Log Rate Spikes" and ran the statistical analysis on the log messages which occured during the alert.
You received the following analysis results from "Explain Log Rate Spikes" which list statistically significant co-occuring field/value combinations sorted from most significant (lower p-values) to least significant (higher p-values) that contribute to the log messages spike:
"Log Rate Analysis" is an AIOps feature that uses advanced statistical methods to identify reasons for increases in log rates. It makes it easy to find and investigate causes of unusual spikes by using the analysis workflow view.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@walterra Making a note, we might need to change prompt text once drop functionality is implemented.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I also added a note to our meta issue regarding drop support: #161832

Copy link
Contributor

@benakansara benakansara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AO changes LGTM

Copy link
Contributor

@yngrdyn yngrdyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes in x-pack/plugins/serverless_observability/public/components/side_navigation/index.tsx LGTM

Copy link
Contributor

@kpatticha kpatticha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Serverless oblt changes LGTM

@@ -63,23 +63,24 @@ const PROGRESS_STEP_GROUPING = 0.1;
const PROGRESS_STEP_HISTOGRAMS = 0.1;
const PROGRESS_STEP_HISTOGRAMS_GROUPS = 0.1;

export const defineExplainLogRateSpikesRoute = (
export const defineLogRateAnalysisRoute = (
Copy link
Member

@jgowdyelastic jgowdyelastic Jul 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think having the path passed in to a common route registering function is correct way to do this.
In the future the LOG_RATE_ANALYSIS route will probably change and have its version bumped, and the old route should not change. However as it is now, the old route is the same as the new route and so it will also change versions.

I think the correct way to do this would be to have two completely separate route registrations, and after some time we can delete the deprecated one.

Copy link
Member

@jgowdyelastic jgowdyelastic Jul 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking about this more, I'm now doubting myself.
It probably will be ok to leave as is, as users won't have this server side endpoint bookmarked. But that also makes me wonder if we need to keep the old one around at all during this rename?

In the future, just deleting deprecated code is easier than having to delete and change this function to remove the path variable. So maybe having a completely separate route registrations is cleaner? Even if it is identical code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline, I removed the deprecated API endpoint in a532e49. It was good as a dry run how this might play out in future serverless environments, but it's not necessary to keep the old endpoint around yet since it's internal and experimental.

Copy link
Member

@jgowdyelastic jgowdyelastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
aiops 834.1KB 834.0KB -53.0B
infra 2.0MB 2.0MB -21.0B
ml 3.4MB 3.4MB +355.0B
observability 1.1MB 1.1MB -18.0B
total +263.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
aiops 6.1KB 6.0KB -61.0B
ml 73.7KB 73.8KB +114.0B
serverlessObservability 26.2KB 26.2KB -6.0B
serverlessSearch 29.6KB 29.6KB -5.0B
total +42.0B
Unknown metric groups

API count

id before after diff
aiops 45 44 -1

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @walterra

@walterra walterra merged commit 11cc1e1 into elastic:main Jul 19, 2023
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Jul 19, 2023
@walterra walterra deleted the ml-aiops-rename-explain-log-rate-spikes-to-log-rate-analysis branch July 19, 2023 14:46
Ruhshan pushed a commit to Ruhshan/kibana that referenced this pull request Jul 19, 2023
…stic#161764)

## Summary

Part of elastic#161832.

This PR renames the Explain Log Rate Spikes feature to **Log Rate
Analysis**.

- [x] Renamed references in `docs/developer/*`
- [x] Updated docs screenshots
- [x] Redirect in docs
- [x] Redirect urls from `explain_log_rate_spikes` to `log_rate_analysis`
- [x] API versioning
- [x] Renamed navigation links
- [x] Renamed variable names
- [x] Renamed file names
- [x] Renamed i18n ids
- [x] Renamed breadcrumbs 
- [x] Removed hard coded `AIOPS_ENABLED` feature flag
ThomThomson pushed a commit to ThomThomson/kibana that referenced this pull request Aug 1, 2023
…stic#161764)

## Summary

Part of elastic#161832.

This PR renames the Explain Log Rate Spikes feature to **Log Rate
Analysis**.

- [x] Renamed references in `docs/developer/*`
- [x] Updated docs screenshots
- [x] Redirect in docs
- [x] Redirect urls from `explain_log_rate_spikes` to `log_rate_analysis`
- [x] API versioning
- [x] Renamed navigation links
- [x] Renamed variable names
- [x] Renamed file names
- [x] Renamed i18n ids
- [x] Renamed breadcrumbs 
- [x] Removed hard coded `AIOPS_ENABLED` feature flag
@peteharverson peteharverson changed the title [ML] AIOps: Rename Explain Log Rate Spikes to Log Rate Analysis. [ML] AIOps: Renames Explain Log Rate Spikes to Log Rate Analysis. Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:ML/AIOps ML AIOps features: Change Point Detection, Log Pattern Analysis, Log Rate Analysis :ml release_note:enhancement v8.10.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.