AWS Route53 - Getting simple metrics such as “number of requests in the last 24hrs” The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!How to account AWS cloudfront metrics if the logs are not reliiable for this?AWS Route53 Subdomain Does Not Work All The TimeGetting different number of AWS instances depending on how I countGetting the private ip address of a recently terminated ec2 instance in awsWhat happen to the REST requests inside the AWS cloud?AWS Route53 not routing the web traffic to failover serverHow to list pending route53 requests via AWS CLI?Why does the AWS console show such a high CPU usage for my Elastic Beanstalk instance?Want to see all the changes happned to aws environment during last one monthAWS Route53 & Lambda: Redirecting Naked HTTP requests to HTTPS WWW for a serverless application
Why can't devices on different VLANs, but on the same subnet, communicate?
Did the new image of black hole confirm the general theory of relativity?
Finding the path in a graph from A to B then back to A with a minimum of shared edges
University's motivation for having tenure-track positions
"... to apply for a visa" or "... and applied for a visa"?
Derivation tree not rendering
How to pronounce 1ターン?
Why can't wing-mounted spoilers be used to steepen approaches?
Are my PIs rude or am I just being too sensitive?
Relations between two reciprocal partial derivatives?
Can a 1st-level character have an ability score above 18?
I could not break this equation. Please help me
Match Roman Numerals
Working through the single responsibility principle (SRP) in Python when calls are expensive
Single author papers against my advisor's will?
When did F become S in typeography, and why?
How to grep and cut numbers from a file and sum them
Can the prologue be the backstory of your main character?
Why not take a picture of a closer black hole?
The variadic template constructor of my class cannot modify my class members, why is that so?
How to delete random line from file using Unix command?
Why did all the guest students take carriages to the Yule Ball?
What do you call a plan that's an alternative plan in case your initial plan fails?
Mortgage adviser recommends a longer term than necessary combined with overpayments
AWS Route53 - Getting simple metrics such as “number of requests in the last 24hrs”
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!How to account AWS cloudfront metrics if the logs are not reliiable for this?AWS Route53 Subdomain Does Not Work All The TimeGetting different number of AWS instances depending on how I countGetting the private ip address of a recently terminated ec2 instance in awsWhat happen to the REST requests inside the AWS cloud?AWS Route53 not routing the web traffic to failover serverHow to list pending route53 requests via AWS CLI?Why does the AWS console show such a high CPU usage for my Elastic Beanstalk instance?Want to see all the changes happned to aws environment during last one monthAWS Route53 & Lambda: Redirecting Naked HTTP requests to HTTPS WWW for a serverless application
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
My goal is to get a simple "# of requests per day" value against a Route 53 hosted zone.
I see no straightforward way to do this.
I have created the query logging as explained here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html
However this is extensive logging and it's split per global edge server. All I want is "domain example.com was queried 40,000 times in the last 24 hours" and similar metrics.
Is this possible? The logging seems overkill and I'll have to do quite a bit of parsing through all the subdirs to get that type of sum.
amazon-web-services amazon-route53 amazon-cloudwatch
asked Apr 9 at 5:22
emmdeeemmdee
3031833
This question has an open bounty worth +100
reputation from emmdee ending ending at 2019-04-18 19:03:45Z">in 5 days.
This question has not received enough attention.
|
show 2 more comments
My goal is to get a simple "# of requests per day" value against a Route 53 hosted zone.
I see no straightforward way to do this.
I have created the query logging as explained here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html
However this is extensive logging and it's split per global edge server. All I want is "domain example.com was queried 40,000 times in the last 24 hours" and similar metrics.
Is this possible? The logging seems overkill and I'll have to do quite a bit of parsing through all the subdirs to get that type of sum.
amazon-web-services amazon-route53 amazon-cloudwatch
asked Apr 9 at 5:22
emmdeeemmdee
3031833
This question has an open bounty worth +100
reputation from emmdee ending ending at 2019-04-18 19:03:45Z">in 5 days.
This question has not received enough attention.
1
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
1
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
1
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
1
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
1
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago
|
show 2 more comments
My goal is to get a simple "# of requests per day" value against a Route 53 hosted zone.
I see no straightforward way to do this.
I have created the query logging as explained here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html
However this is extensive logging and it's split per global edge server. All I want is "domain example.com was queried 40,000 times in the last 24 hours" and similar metrics.
Is this possible? The logging seems overkill and I'll have to do quite a bit of parsing through all the subdirs to get that type of sum.
amazon-web-services amazon-route53 amazon-cloudwatch
asked Apr 9 at 5:22
emmdeeemmdee
3031833
My goal is to get a simple "# of requests per day" value against a Route 53 hosted zone.
I see no straightforward way to do this.
I have created the query logging as explained here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html
However this is extensive logging and it's split per global edge server. All I want is "domain example.com was queried 40,000 times in the last 24 hours" and similar metrics.
Is this possible? The logging seems overkill and I'll have to do quite a bit of parsing through all the subdirs to get that type of sum.
amazon-web-services amazon-route53 amazon-cloudwatch
amazon-web-services amazon-route53 amazon-cloudwatch
asked Apr 9 at 5:22
emmdeeemmdee
3031833
asked Apr 9 at 5:22
emmdeeemmdee
3031833
asked Apr 9 at 5:22
emmdeeemmdee
3031833
asked Apr 9 at 5:22
emmdeeemmdee
3031833
asked Apr 9 at 5:22
emmdeeemmdee
3031833
3031833
This question has an open bounty worth +100
reputation from emmdee ending ending at 2019-04-18 19:03:45Z">in 5 days.
This question has not received enough attention.
This question has an open bounty worth +100
reputation from emmdee ending ending at 2019-04-18 19:03:45Z">in 5 days.
This question has not received enough attention.
1
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
1
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
1
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
1
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
1
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago
|
show 2 more comments
1
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
1
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
1
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
1
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
1
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago
1
1
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
1
1
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
1
1
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
1
1
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
1
1
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago
|
show 2 more comments
1 Answer
1
active
oldest
votes
There is no quick & easy solution here. Short answer, use the billing dashboard for historical metrics.
The billing dashboard is the only way to get values like this right now unless you want to write a tool to parse and analyze CloudWatch logs using the query-logs exporter, which is not a straightforward solution as the question is asking for.
answered 2 days ago
emmdeeemmdee
3031833
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962141%2faws-route53-getting-simple-metrics-such-as-number-of-requests-in-the-last-24h%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no quick & easy solution here. Short answer, use the billing dashboard for historical metrics.
The billing dashboard is the only way to get values like this right now unless you want to write a tool to parse and analyze CloudWatch logs using the query-logs exporter, which is not a straightforward solution as the question is asking for.
answered 2 days ago
emmdeeemmdee
3031833
add a comment |
There is no quick & easy solution here. Short answer, use the billing dashboard for historical metrics.
The billing dashboard is the only way to get values like this right now unless you want to write a tool to parse and analyze CloudWatch logs using the query-logs exporter, which is not a straightforward solution as the question is asking for.
answered 2 days ago
emmdeeemmdee
3031833
add a comment |
There is no quick & easy solution here. Short answer, use the billing dashboard for historical metrics.
The billing dashboard is the only way to get values like this right now unless you want to write a tool to parse and analyze CloudWatch logs using the query-logs exporter, which is not a straightforward solution as the question is asking for.
answered 2 days ago
emmdeeemmdee
3031833
There is no quick & easy solution here. Short answer, use the billing dashboard for historical metrics.
The billing dashboard is the only way to get values like this right now unless you want to write a tool to parse and analyze CloudWatch logs using the query-logs exporter, which is not a straightforward solution as the question is asking for.
answered 2 days ago
emmdeeemmdee
3031833
answered 2 days ago
emmdeeemmdee
3031833
answered 2 days ago
emmdeeemmdee
3031833
answered 2 days ago
emmdeeemmdee
3031833
3031833
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962141%2faws-route53-getting-simple-metrics-such-as-number-of-requests-in-the-last-24h%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You can probably work it out from your bill. Curious why you need this. It's largely irrelevant except for billing, given that there can be many caches between Route53 and the end user, for example an ISP cache. Would number of requests to your web server be a good enough number? With a DNS TTL probably around 5 minutes this number is going to be pretty large for a busy website.
– Tim
2 days ago
1
Main purpose is a pretty dashboard for management and to help find good TTL values. I agree it's not crazy important nor accurate just trying to fulfill tasks given to me.
– emmdee
2 days ago
1
TTL values shouldn't be set based on the number of queries that result, they should be set based on how quickly you might need to change the records' data and have it reflected everywhere.
– ceejayoz
2 days ago
1
AFAIK DNS TTL is only relevant when you want to change where your site is hosted, or other similar things. If you use a load balancer you have no choice on your TTL anyway. I suggest this isn't a good investment of your time.
– Tim
2 days ago
1
I know what TTL is. AWS charges per-million-lookups and higher TTL means overall less lookups but less change time for DNS changes, so I would like to have some insight into DAILY QUERIES sheesh it's a simple question honestly. We do logs of dns chagnes because our systems are cattle, not pets so lots of DNS changes for A/B deployments That's kind of out of the scope of this question though since I'm looking for a "quick" way to check the values and not looking to invest much time hence the simple question simple answer --- Sounds like "it can't be done" is the right answer here.
– emmdee
2 days ago