added GetSensorUsageHourly as this allows you to pull hourly billing based on Cloud calculated billing.#1375
Merged
Conversation
…oud based; added it to test sensor; tested it in production and works since the endpoint does work and provides hourly usage billing that is used for Cloud (reserved hourly) usage
a546e22 to
bf97863
Compare
Member
|
Merging into |
jshcodes
approved these changes
Nov 5, 2025
jshcodes
left a comment
Member
There was a problem hiding this comment.
Thank you for your contribution!!! 🙇
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add GetSensorUsageHourly
Added
GetSensorUsageHourlyto_sensor_usage.pyendpoint; tested it in production, and works by providing either hourly or weekly billing usage depending on how billing is calculated. This is part of CrowdStrike documentation and also shows in the billing dashboard how these values are pulled. This helps calculate the Cloud (reserved hourly) usage. The endpoint that is not documented, but works along with getting weekly billing information is:"/billing-dashboards-usage/aggregates/hourly-average/v1"Unit test coverage
Bandit analysis
[main] INFO running on Python 3.13.3 Working... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:01 Run started:2025-11-05 19:15:54.058193 Test results: No issues identified. Code scanned: Total lines of code: 98726 Total lines skipped (#nosec): 0 Run metrics: Total issues (by severity): Undefined: 0 Low: 0 Medium: 0 High: 0 Total issues (by confidence): Undefined: 0 Low: 0 Medium: 0 High: 0 Files skipped (0):Added features and functionality
Added support for pulling
hourlybilling data frombilling-dashboard-usageendpoint on top of the weekly-average values.