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

add heartbeat billable field #510

Merged
merged 1 commit into from
May 31, 2024
Merged

add heartbeat billable field #510

merged 1 commit into from
May 31, 2024

Conversation

joeypoon
Copy link
Member

Change Summary

Adds a new boolean field billable to the heartbeat mapping. This field is used to determine whether a particular heartbeat document should be included in billing calculations.

Sample values

Sample document:

{
    "@timestamp": "2023-07-18T20:40:09.279939Z",
    "agent": {
        "id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
    },
    "data_stream": {
        "dataset": "endpoint.heartbeat",
        "namespace": "default",
        "type": ".logs"
    },
    "message": "Endpoint heartbeat",
    "event": {
        "ingested": "2023-07-18T20:40:09.279939Z"
    },
    "billable": true
}

Release Target

8.15

For mapping changes:

  • I ran make after making the schema changes, and committed all changes

@joeypoon joeypoon requested a review from a team as a code owner May 31, 2024 18:23
@joeypoon joeypoon requested review from tomsonpl, paul-tavares and pzl and removed request for tomsonpl and paul-tavares May 31, 2024 18:23
@joeypoon joeypoon mentioned this pull request May 31, 2024
1 task
@joeypoon joeypoon merged commit c09efbf into main May 31, 2024
4 checks passed
@joeypoon joeypoon deleted the feature/billable-flag branch May 31, 2024 18:42
@elasticmachine
Copy link
Contributor

Package endpoint - 8.15.0 containing this change is available at https://epr.elastic.co/search?package=endpoint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants