-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
-
True
-
BIZ-679 - Ansible on AWS, SaaS
-
-
Configure Infrastructure hours per [https://docs.google.com/document/d/1Uod__RKPA-ZkHNQHVdLJVz9nd_UbZkqAM3jlrQBX2to/edit]
Done
- The "infrastructure" metric for ansible-aap-managed is added to the ansible-aap-managed.yaml file
- Ansible is sending us a metric_id of "Instance-hours"
- metric type is "counter"
- AWS Dimension is already defined as "infrastructure"
- Change service_type to Ansible Infrastructure Hour instead of AAP Cluster
- The "managed nodes" metric is correct
- Ansible is sending us metric_id of "Managed-nodes"
- metric type should be "gauge", it's currently "counter"
- awsDimension should be "managed_node", it's currently "managed_nodes"
- serviceType gets set in the database based on the incoming Event message, not serviceType from the yaml file
- Remove serviceType from the yaml definition if it's not too complicate to do so. Service Type is only relevant for nightly tallies, and usage won't be collected for this product during nightly tally. Ansible is sending us different service types depending on which metric the message is for. Since serviceType is a top-level attribute in a product config file, to accommodate our config structure, it would require another file, another product tag with duplicate lookup parameters, etc. If it's not easy to remove serviceType from the ansible config file - Plan B is to leave it as
serviceType: Ansible Managed Node, define it under the "defaults" section, and add a comment that we expect usage events for this product to also have messages with serviceType: Ansible Infrastructure Hour
- Remove serviceType from the yaml definition if it's not too complicate to do so. Service Type is only relevant for nightly tallies, and usage won't be collected for this product during nightly tally. Ansible is sending us different service types depending on which metric the message is for. Since serviceType is a top-level attribute in a product config file, to accommodate our config structure, it would require another file, another product tag with duplicate lookup parameters, etc. If it's not easy to remove serviceType from the ansible config file - Plan B is to leave it as
- blocks
-
SWATCH-2755 Confirm snapshot creation and billable usage remittance behaviors for Ansible usage
- Closed