Skip to content

Adds EIS info to Security billing #1070

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Apr 11, 2025
+6 −0
Merged

Adds EIS info to Security billing #1070

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
47093a6
Update security-billing-dimensions.md
jmikell821 Apr 10, 2025
ce36682
Update security-billing-dimensions.md
jmikell821 Apr 10, 2025
93b1956
Update security-billing-dimensions.md
jmikell821 Apr 11, 2025
b302f8f
Merge branch 'main' into issue-967-billing
jmikell821 Apr 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions deploy-manage/cloud-organization/billing/security-billing-dimensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,3 +67,9 @@ For [CNVM](../../../solutions/security/cloud/cloud-native-vulnerability-manageme
Logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above.

For more details about {{elastic-sec}} serverless project rates and billable assets, refer to Cloud Protection in the [{{ecloud}} pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security).

% Note: Commenting out this section until this is ready to be published.

% ## Elastic-managed LLM
Copy link

Choose a reason for hiding this comment

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

@jmikell821, the PLI, or what is shown on the billing usage page is still called 'Elastic Inference Service'. Only the dropdown for Elastic LLM when selecting the LLM in AI Assistant or Attack Discovery is now called Elastic Managed LLM (or Elastic-managed LLM, until James or Shubha confirm). So I recommend that the title of this section be called something like 'Elastic Inference Service - Elastic Managed LLM'. In the body we could replace "default LLM" with "default Elastic Managed LLM."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @gaurav-elastic. Since I've merged the PR, I've added a note to #967 as a reminder for when we're ready to publish this.


% The default LLM enables you to leverage AI-powered search as a service without deploying a model in your serverless project. It's configured by default to use with the Security AI Assistant, Attack Discovery, and other applicable AI features as a part of your "Complete" tier subscription. Using the default LLM will use tokens and incur related token-based add-on billing for your serverless project.
Loading