-
Notifications
You must be signed in to change notification settings - Fork 19
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 ecs task payload #281
add ecs task payload #281
Conversation
nit: your code uses tabs, but the rest of the file uses spaces for indentation. |
proto/process/agent.proto
Outdated
@@ -669,6 +755,7 @@ enum K8sResource { | |||
CR = 21; | |||
VERTICALPODAUTOSCALER = 22; | |||
HORIZONTALPODAUTOSCALER = 23; | |||
ECSTASK = 24; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That looks odd to add an ECS resource to a K8sResource
enum, we could rename it to OrchestratorResource
and start at a different offset for ECS tasks so we have room for new Kubernetes resources.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agent-payload/proto/process/agent.proto
Lines 742 to 769 in 7f5124f
enum OrchestratorResource { | |
OrchestratorResource_UNSPECIFIED = 0; | |
POD = 1; | |
REPLICASET = 2; | |
SERVICE = 3; | |
NODE = 4; | |
CLUSTER = 5; | |
JOB = 6; | |
CRONJOB = 7; | |
DAEMONSET = 8; | |
STATEFULSET = 9; | |
PERSISTENTVOLUME = 10; | |
PERSISTENTVOLUMECLAIM = 11; | |
ROLE = 12; | |
ROLEBINDING = 13; | |
CLUSTERROLE = 14; | |
CLUSTERROLEBINDING = 15; | |
SERVICEACCOUNT = 16; | |
INGRESS = 17; | |
DEPLOYMENT = 18; | |
NAMESPACE = 19; | |
CRD = 20; | |
CR = 21; | |
VERTICALPODAUTOSCALER = 22; | |
HORIZONTALPODAUTOSCALER = 23; | |
NETWORKPOLICY = 24; | |
ECSTASK = 150; | |
} |
88d488e
to
7f5124f
Compare
7f5124f
to
7d4963c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
string family = 6; | ||
string version = 7; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Maybe specify platformVersion
instead of version
as it may be confusing since taskVersion
exists. Same for family -> platformFamily ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll delete taskVersion
. family
and version
here stand for task definition family and version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad , actually taskVersion is a custom field that is used to track changes. I'll rename it to resource version
string family = 6; | ||
string version = 7; | ||
string availabilityZone = 8; | ||
map<string, double> limits = 9; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this field supposed to contain both memory
and cpu
limits like this?
{"cpu": 8, "memory": 4}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I feel I still prefer to use a map instead of using two dedicated fields as we can check if the value is set or not
if val, ok := limits["CPU"]; ok {
//do somthing
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should define some constants for the keys?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can't use enum type as key for a map in proto 😞
It's a usage we are already using https://github.com/DataDog/agent-payload/blob/master/proto/process/agent.proto#L996
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems it's impossible to define constant strings in protobuf3. And if we were to split the limits
field into 2 (memLimits, cpuLimits) it's not possible to check if the field has a value or not since numeric types are initialized with 0 in golang.
So leaving this as is is the best option I think
@@ -681,6 +767,7 @@ enum K8sResource { | |||
VERTICALPODAUTOSCALER = 22; | |||
HORIZONTALPODAUTOSCALER = 23; | |||
NETWORKPOLICY = 24; | |||
ECSTASK = 150; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7f472b8
to
eed77af
Compare
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/DataDog/agent-payload/v5](https://togithub.com/DataDog/agent-payload) | `v5.0.104` -> `v5.0.111` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.111?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.111?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.104/v5.0.111?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.104/v5.0.111?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-api-client-go/v2](https://togithub.com/DataDog/datadog-api-client-go) | `v2.22.0` -> `v2.24.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-api-client-go%2fv2/v2.24.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-api-client-go%2fv2/v2.24.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-api-client-go%2fv2/v2.22.0/v2.24.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-api-client-go%2fv2/v2.22.0/v2.24.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>DataDog/agent-payload (github.com/DataDog/agent-payload/v5)</summary> ### [`v5.0.111`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.111): [CWS] Udpate the CWS proto for the security profiles sliding window purpose [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.110...v5.0.111) This new proto version update the security profile proto, deprecating some fields and adding the version contexts PR needed for the [related work on security profile sliding window](https://togithub.com/DataDog/datadog-agent/pull/20506) #### What's Changed - \[CWS] Udpate the CWS proto for the security profiles sliding window purpose by [@​spikat](https://togithub.com/spikat) in [https://github.com/DataDog/agent-payload/pull/292](https://togithub.com/DataDog/agent-payload/pull/292) #### New Contributors - [@​spikat](https://togithub.com/spikat) made their first contribution in [https://github.com/DataDog/agent-payload/pull/292](https://togithub.com/DataDog/agent-payload/pull/292) **Full Changelog**: DataDog/agent-payload@v5.0.110...v5.0.111 ### [`v5.0.110`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.110) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.109...v5.0.110) #### What's Changed - add TypeCollectorECSTask by [@​kangyili](https://togithub.com/kangyili) in [https://github.com/DataDog/agent-payload/pull/296](https://togithub.com/DataDog/agent-payload/pull/296) **Full Changelog**: DataDog/agent-payload@v5.0.109...v5.0.110 ### [`v5.0.109`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.109) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.108...v5.0.109) #### What's Changed - cronjob status: add lastSuccessfultime by [@​aureleoules](https://togithub.com/aureleoules) in [https://github.com/DataDog/agent-payload/pull/295](https://togithub.com/DataDog/agent-payload/pull/295) **Full Changelog**: DataDog/agent-payload@v5.0.108...v5.0.109 ### [`v5.0.108`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.108) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.107...v5.0.108) #### What's Changed - Add repo digest field to container payload by [@​badovm](https://togithub.com/badovm) in [https://github.com/DataDog/agent-payload/pull/293](https://togithub.com/DataDog/agent-payload/pull/293) - ecs task lifecycle event by [@​kangyili](https://togithub.com/kangyili) in [https://github.com/DataDog/agent-payload/pull/282](https://togithub.com/DataDog/agent-payload/pull/282) - add ecs task payload by [@​kangyili](https://togithub.com/kangyili) in [https://github.com/DataDog/agent-payload/pull/281](https://togithub.com/DataDog/agent-payload/pull/281) #### New Contributors - [@​badovm](https://togithub.com/badovm) made their first contribution in [https://github.com/DataDog/agent-payload/pull/293](https://togithub.com/DataDog/agent-payload/pull/293) **Full Changelog**: DataDog/agent-payload@v5.0.107...v5.0.108 ### [`v5.0.107`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.107) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.106...v5.0.107) **Full Changelog**: DataDog/agent-payload@v5.0.106...v5.0.107 #### What's Changed - Add repo digest field to container payload by [@​badovm](https://togithub.com/badovm) in [https://github.com/DataDog/agent-payload/pull/293](https://togithub.com/DataDog/agent-payload/pull/293) #### New Contributors - [@​badovm](https://togithub.com/badovm) made their first contribution in [https://github.com/DataDog/agent-payload/pull/293](https://togithub.com/DataDog/agent-payload/pull/293) **Full Changelog**: DataDog/agent-payload@v5.0.106...v5.0.107 ### [`v5.0.106`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.106) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.105...v5.0.106) #### What's Changed - Add TRACE HTTP method to process payload by [@​vitkyrka](https://togithub.com/vitkyrka) in [https://github.com/DataDog/agent-payload/pull/291](https://togithub.com/DataDog/agent-payload/pull/291) #### New Contributors - [@​vitkyrka](https://togithub.com/vitkyrka) made their first contribution in [https://github.com/DataDog/agent-payload/pull/291](https://togithub.com/DataDog/agent-payload/pull/291) **Full Changelog**: DataDog/agent-payload@v5.0.105...v5.0.106 ### [`v5.0.105`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.105) [Compare Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.104...v5.0.105) #### What's Changed - Add NetworkPolicy protobuf definition by [@​aureleoules](https://togithub.com/aureleoules) in [https://github.com/DataDog/agent-payload/pull/290](https://togithub.com/DataDog/agent-payload/pull/290) #### New Contributors - [@​aureleoules](https://togithub.com/aureleoules) made their first contribution in [https://github.com/DataDog/agent-payload/pull/290](https://togithub.com/DataDog/agent-payload/pull/290) **Full Changelog**: DataDog/agent-payload@v5.0.104...v5.0.105 </details> <details> <summary>DataDog/datadog-api-client-go (github.com/DataDog/datadog-api-client-go/v2)</summary> ### [`v2.24.0`](https://togithub.com/DataDog/datadog-api-client-go/releases/tag/v2.24.0) [Compare Source](https://togithub.com/DataDog/datadog-api-client-go/compare/v2.23.0...v2.24.0) <!-- Release notes generated using configuration in .github/release.yml at v2.24.0 --> ##### What's Changed ##### Fixed - Disable additionalProperties for Downtime Schedule UpdateRequest oneOfs by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2390](https://togithub.com/DataDog/datadog-api-client-go/pull/2390) - Fix ListServiceDefinitions pagination information by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2416](https://togithub.com/DataDog/datadog-api-client-go/pull/2416) ##### Added - Adds support for `ListMetricAssets` endpoint by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2404](https://togithub.com/DataDog/datadog-api-client-go/pull/2404) - Add support for new CRUD agent rules endpoints by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2410](https://togithub.com/DataDog/datadog-api-client-go/pull/2410) - Add documentation for workflow usage attribution by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2418](https://togithub.com/DataDog/datadog-api-client-go/pull/2418) - Add Custom Destinations Public API by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2422](https://togithub.com/DataDog/datadog-api-client-go/pull/2422) ##### Deprecated - Deprecate the pattern property for SDS Standard Pattern Attributes by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2411](https://togithub.com/DataDog/datadog-api-client-go/pull/2411) - Deprecate Incident Services endpoints by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2424](https://togithub.com/DataDog/datadog-api-client-go/pull/2424) ##### New Contributors - [@​antonio-ramadas-dd](https://togithub.com/antonio-ramadas-dd) made their first contribution in [https://github.com/DataDog/datadog-api-client-go/pull/2421](https://togithub.com/DataDog/datadog-api-client-go/pull/2421) **Full Changelog**: DataDog/datadog-api-client-go@v2.23.0...v2.24.0 ### [`v2.23.0`](https://togithub.com/DataDog/datadog-api-client-go/releases/tag/v2.23.0) [Compare Source](https://togithub.com/DataDog/datadog-api-client-go/compare/v2.22.0...v2.23.0) <!-- Release notes generated using configuration in .github/release.yml at v2.23.0 --> #### What's Changed ##### Fixed - Move under common tag Case Management by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2385](https://togithub.com/DataDog/datadog-api-client-go/pull/2385) - Include user data with team membership resource by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2380](https://togithub.com/DataDog/datadog-api-client-go/pull/2380) ##### Added - Case Management Public API documentation by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2364](https://togithub.com/DataDog/datadog-api-client-go/pull/2364) - Make grpc steps available for synthetics api multisteps tests by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2384](https://togithub.com/DataDog/datadog-api-client-go/pull/2384) - Add cloud run filter to GCP v1 and v2 spec by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2361](https://togithub.com/DataDog/datadog-api-client-go/pull/2361) - add ASM serverless to usage metering API docs by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2393](https://togithub.com/DataDog/datadog-api-client-go/pull/2393) - Add new products to usage API docs by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2396](https://togithub.com/DataDog/datadog-api-client-go/pull/2396) ##### Changed - Update spec for DORA Metrics Incident endpoint by [@​api-clients-generation-pipeline](https://togithub.com/api-clients-generation-pipeline) in [https://github.com/DataDog/datadog-api-client-go/pull/2381](https://togithub.com/DataDog/datadog-api-client-go/pull/2381) **Full Changelog**: DataDog/datadog-api-client-go@v2.22.0...v2.23.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNjkuMiIsInVwZGF0ZWRJblZlciI6IjM3LjI2OS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]>
What does this PR do?
Agent PR DataDog/datadog-agent#21836
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Reviewer's Checklist
Reviewers: please see the review guidelines.