-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
5
-
False
-
-
False
-
-
In order to properly observe and track swatch-producer-aws we must log state changes and errors more thoroughly. When error cases occur we should alert on them from splunk.
Important fields to log:
- org_id
- billing_account_id
- billing_provider
- billing_factor
- value
- product_id
- metric_id
- remittance_uuid
- aggregate_id
- remittance timestamp
- aggregate window timestamp
Fields from aws:
- MeteredEventId
- CustomerIdentifier
- Dimension
- Value
- Timestamp
Areas to log:
Normal flow:
- Consumed billable-usage-aggregate
- Reason for not sending to marketplace if not sent(ex: metric_id invalid)
- Request to aws api
- Response from aws api
- Status changes sent to billable-usage.status topic
Error cases:
- Subscription missing
- Api failures from swatch-contracts
- Api failures from aws marketplace
Alerts:
- Customer not subscribed when no contract found
- Failed message rate increase (5 in 5 minutes?)
- clones
-
SWATCH-3120 Logging and alerting improvements for swatch-producer-azure
- New