Nov 20, 2020
10:57 AM
1 Kudo
One other helpful note: the Billing Entity dimension can identify "AWS Marketplace" charges, if you want to focus on those particular Services and see the improved names.
... View more
Sep 03, 2020
08:50 AM
3 Kudos
Hi, the Adjustment Program UI is currently read-only for the most part, only the percentages are editable.
So to add new adjustments you would have to use the API: https://reference.rightscale.com/bill_analysis/ There is also a prototype editor for the JSON used by that API: https://reference.rightscale.com/bill_analysis/adj_json_editor/
... View more
May 30, 2019
02:45 PM
3 Kudos
Tips for Using AWS X-Ray Traces for Long-Running Requests
AWS X-Ray is a tool for understanding how requests flow through your microservices and identifying any issues or performance bottlenecks. A single trace can show how one request into the system flows to all of the backend services.
AWS advertises that a single trace can store up to 500 KB, which is enough to illustrate your trace in fine detail — hundreds or thousands of segments.
However, if your trace proceeds slowly, you might discover that your trace will be closed prematurely and your remaining updates will be rejected.
Why is this?
A trace can actually be open for seven days. However, there are undocumented “dynamic” limits that kick in, which may mean that you have far less than the advertised 500 KB of data to work with in your trace.
Here’s the result of a simple experiment:
In my test, I simply created a trace and sent subsegments at a steady rate. I counted the total bytes of JSON data sent to the AWS X-Ray daemon before the API returned an InvalidSegment error code, refusing to add any more segments to the trace.
When sending the data quickly, I could send in more than the advertised limit of 500 KB. But when sending data slowly, that limit quickly plummeted. For any trace lasting more than six minutes, I could only send 14 KB before the trace was closed! That was sobering to see the limit reduced by 97%.
I spoke with the AWS X-Ray team and they acknowledged the lack of documentation on these dynamic limits. They expressed an interest in eventually improving the documentation and perhaps even relaxing these limits.
Meanwhile, their general advice is to send less data — fewer segments, subsegments, annotations, or metadata. And if needed, split up a single large trace into several different traces.
... View more
Latest posts by jslattery
Subject | Views | Posted |
---|---|---|
928 | Nov 20, 2020 10:57 AM | |
983 | Sep 03, 2020 08:50 AM | |
1246 | May 30, 2019 02:45 PM |
Activity Feed
- Kudoed Creating custom spend recommendations for additional saving opportunities for cwilhelm. Sep 07, 2022 12:30 PM
- Kudoed Cloud Cost Optimization: Total Potential Savings for cwilhelm. Mar 31, 2022 11:38 AM
- Kudoed Coming Soon: Cloud Cost Optimization Recommendations Update for cwilhelm. Feb 23, 2022 09:57 AM
- Kudoed Allocate AWS discount program fees to the accounts were they were used! for James_Folmar. Dec 20, 2020 05:16 PM
- Got a Kudo for Re: Adjustment Program. Nov 26, 2020 05:05 AM
- Got a Kudo for Re: AWS Service Name Update. Nov 20, 2020 11:16 AM
- Posted Re: AWS Service Name Update on Flexera One Blog. Nov 20, 2020 10:57 AM
- Got a Kudo for Re: Adjustment Program. Sep 23, 2020 03:55 PM
- Got a Kudo for Re: Adjustment Program. Sep 03, 2020 08:57 AM
- Posted Re: Adjustment Program on Flexera One Forum. Sep 03, 2020 08:50 AM
- Kudoed Custom Dashboard Sharing is Now Live in Optima for csturgill. Jul 03, 2020 10:34 AM
- Kudoed The Perfect Software Engineer for RSimon. Jul 24, 2019 10:17 AM
- Got a Kudo for Tips for Using AWS X-Ray Traces for Long-Running Requests. Jul 09, 2019 09:21 AM
- Kudoed Announcing Goa v3.0.0 for RSimon. Jul 09, 2019 07:35 AM
- Got a Kudo for Tips for Using AWS X-Ray Traces for Long-Running Requests. Jul 08, 2019 10:36 PM
- Got a Kudo for Tips for Using AWS X-Ray Traces for Long-Running Requests. Jul 08, 2019 10:32 PM
- Posted Tips for Using AWS X-Ray Traces for Long-Running Requests on Flexera Engineering Blog. May 30, 2019 02:45 PM