Update alerting-settings.md and add serverless value for one parameter#250842
Update alerting-settings.md and add serverless value for one parameter#250842florent-leborgne merged 4 commits intomainfrom
Conversation
|
Pinging @elastic/experience-docs (Team:Docs) |
🔍 Preview links for changed docs |
florent-leborgne
left a comment
There was a problem hiding this comment.
@kunisen let me know what you think about my suggestion, since this page is initially not for serverless
|
Thanks, @kunisen ! I think your changes look good with the exception of having the caveat that Serverless cannot be configured, which is what I believe @florent-leborgne is going for. However, it seems we may want to break that down even further for Serverless Security once we have that corrected value, and highlight that Serverless values are not user-configurable (nor are ECH for this particular setting), but for the rest of Stack it is. |
Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
|
Thanks @maggieghamry and @florent-leborgne [1]@florent-leborgne thanks for the comment
Yeah it sounds much better to call out! [2]Just in case, we say we may want to bump this up for all projects by default for security, but this is not done yet per this. So I will keep this value 400 for now. [3]@maggieghamry thanks for the reminder too.
I added one more note Quick preview screenshots: Details
Also, if we want to differentiate this between different projects, then we may need to have yet a different I will leave this to @florent-leborgne to decide what would be the best way to express in public doc. |
|
Sounds good @kunisen If that indeed does change for Security projects, we will be able to do it quite clearly as we have proper tags for the various types of serverless projects. |
…iew_cps * commit '5f7fec57cb01883038810bd735a0666683b49904': (116 commits) [Security Solution][Attacks/Alerts][Setup and miscellaneous] Advanced setting to control feature visibility (elastic#250157) (elastic#250830) Fix synthtrace `fetch` usage (elastic#250950) [APM] Add Nodes and Edges components and selection logic (elastic#250937) [Docs] Update alerting-settings.md and add serverless value for one parameter (elastic#250842) [Agent Builder] filestore: initial implementation (elastic#250043) [CPS] Support CPS in Vega ESQL (elastic#250693) Adjustments to cascade document esql helpers (elastic#250560) [Security Solutions] Trial Companion - adds ai chat and elastic agent detectors (elastic#250908) [Obs Presentation] Code Scanning Alert Fixes (elastic#250858) [performance] add return and refresh render scenarios to dashboard journeys (elastic#250939) skip failing test suite (elastic#245458) Add Cloud Forwarder onboarding tile to O11y Solution (elastic#250325) [Traces] Remove APM unified trace waterall embeddable registration (elastic#250808) [Discover] [Metrics] Fix: metrics grid titles do not update on order change (elastic#250963) [a11y] Fix Eui modal title annoucment (elastic#250459) [Cloud Security] [Fleet] Add cloud connector access scope for input or package level credential definitions (elastic#250280) [WorkplaceAI] SharePoint Online stack connector (elastic#248737) [Response Ops][Task Manager] Update functions do not handle API key invalidation (elastic#249109) [Osquery] Remove @kbn/timelines-plugin dependency from osquery plugin (elastic#250055) [One Discover][Logs UX] Update OpenTelemetry Semantic Conventions (elastic#250346) ...
…arameter (elastic#250842) ## Summary Summarize your PR. If it involves visual changes include a screenshot or gif. Context in elastic/docs-content-internal#694 cc @maggieghamry @ppf2 ## Preview / View * Before merge: [docs/reference/configuration-reference/alerting-settings.md](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/250842/reference/configuration-reference/alerting-settings) * After merge: https://www.elastic.co/docs/reference/kibana/configuration-reference/alerting-settings#:~:text=xpack.alerting.rules.maxScheduledPerMinute ### Checklist No hit as this is a doc PR. Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
Summary
Summarize your PR. If it involves visual changes include a screenshot or gif.
Context in https://github.com/elastic/docs-content-internal/issues/694
cc @maggieghamry @ppf2
Preview / View
Checklist
No hit as this is a doc PR.
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.