In my Google Sheets API Console, there are duplicated "Read/Write requests".
First "Read requests" has real data and has options "Read requests per day" and "Read requests per minute".
Second "Read requests" has no data and has options "Read requests per day" and "Read requests per 100 seconds".
Why does second pane exist?Is it just me?
Best regards.
appearance
First pane
Second pane
All newly created projects in GCP have the same quotas in Google Sheets API. This is the default set by Google:
The 100-second quota and 60-second quota are different entities.
If you want to request changes/increase to these default quotas, please follow the steps here:
Increase the quota for an API
Depending on your resource usage, you may want to increase the quota for an API.
Go to the Google Cloud Platform Console and sign in as a G Suite super administrator.
From the Project list, select the project you're using for the migration.
On the left, click IAM & admin and then Quotas.
Using the checkboxes, select one or more quotas to edit, then click Edit Quotas.
Note: Billing must be enabled on the project in order to click the checkboxes.
In the Edit Quotas panel on the right, complete the form with your Name, Email, and Phone details, then click Next.
In the Edit Quotas panel, select the service to expand the view, then edit the quotas in that service to your requested limit. Click Done.
Click Submit request.
For more information, please check this support page: Monitor API Quotas
Related
we have an online service for integrating different services and applications with each other. We don't have enough limits. The requests are written optimally, we do not make unnecessary requests.
You can request for a quota increase through your GCP Console. Just follow the steps below:
1.) Login to your GCP Console admin account.
2.) On the navigation menu, click on IAM & Admin -> Quotas.
3.) Select the API service that you will request for an increase. Tick the checkbox on the right side of the console then click EDIT QUOTAS in the top part of the screen.
4.) Specify the new quota limit that you want and you are done with the request.
Quota increase requests usually take 2-3 days.
Reference
Increasing API Quota
We faced with testing problem on the side Google Pay.
At the current stage, we get into the GPay only after Card registration on the side of our site, when after filling out the form user is redirected to the GPay page to create a new Card.
A Card is being created : we see it with the data that is entered into the form, but the GPay doesn't send any requests to our site. A special test environment from GPay is needed?
Google Pay's support service asks: "Are you receiving the POST from GPay when you attempt the enrollment flow from the app?"
How we can apply from GPay if we can't create a Card from GP at this stage?
The process of creating a Card is described in paragraph 1 (on the site side).
How to get into the GPay for enrollment at the testing stage?
Support service writes "When you submit your user details from GPay, it sends a POST request to your server so that when your page is displayed it contains the information from the user data form. "
As we pointed, at the current stage we can't send data from the GPay.
It was expected thatGoogle Pay's support service send a POST request to our site, but we don't see POST request's body. It is empty.
Therefore, we asked earlier, What internet service we can see it with?
They answered, as we understood, that we can see it by sending from GPay.
How to send it from the GPay, if at the testing stage we can only see
newly created cards and we don’t get any requests from GPay?
Is testing take place from GPay app?
If so, why don't we have an access?
We get a request POST, but with an empty request body.
The GPay has a lot of users with the Loyalty Card.
Someone has already come across this.
We didn't find such situations on the Internet.
How anybody have handled situations like this before?
How to create a new Card from GPay and see a POST request?
We do not have access to the class settings in the account. On Russian language, we do not see the callback feature, and on English technical support sends to us a screenshot - there are settings in the account. Could there be access rights issues?
To accoding with your link from paragraph 5 https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo - we did not find the insert barcode /manually settings. Can you tell us where to find them?
At the moment, we can scan the barcode in GPay app(due to help of GPay support service ), but we do not receive a Post request after inserting bar code in GPay app.
Our Russian account settings looks like:
GPay support service see our account on English so:
We don't see these settings for barcode.
In accordance with the documentation https://developers.google.com/pay/passes/guides/overview/how-to/use-callbacks, we set up a callback feature, but we do not receive a post request in the format json (php):
$responseJson_str = file_get_contents('php://input');
$responseJson = '[' . $responseJson_str . ']';
$response = json_decode($responseJson, true);
var_dump( $response);
$file_server = "server_calback.log";
$fw = fopen($file_server, "a");
fwrite($fw, "POST " . var_export($response, true) . "\n");
fclose($fw);
What is wrong?
I show a screenshot with the request POST to our site
https://itcrk.icu/testcallback.php
from https://reqbin.com/
At the beginning of testing stage, we implemented signin / signup as you indicated in points 1-6. We did this functionality was not because we needed it, but thought that it was necessary for testing.
Then we wrote in support team that we need a barcode/manually, as users of other cards are used to. We were answered that we need settings in the account, we did not find them. Support team helped us to configure the barcode in the account of the Merchant Center - Google.We insert barcode in the GPay , but we don’t get json on the site. We assume a problem with access rights in the Merchant Center - Google. How do other cardholders usually set up a barcode in their accounts? We do not have access to the settings n the Merchant Center - Google, unfortunately. Support team writes that there should be access, but it does not.
It turned out that there are two ways to work with cards in the GPay. The first method is described in the documentation here https://developers.google.com/pay/passes/guides/enrollment-signin, the second method is to scan the card(barcode/manually) and use it as a card storage, but card data is not sent to the user’s server.
The Loyalty card is simply displayed in the GPay with its number(from barcode/manually) and that's all.
Sign up and enrollment are triggered from the google pay app: https://developers.google.com/pay/passes/guides/enrollment-signin
You will see post once a user goes into the Google Pay app and hits add pass then finds your program and hits sign up/ sign in.
See 1-2.
You have to use the account you provide to support team - its only visible for them for testing.
It may not be from Google. Google requests have the body with the user details.
Go to google pay app and sign in with user that is whitelisted by support to see the program. Hit add pass, then loyalty program then search for your program then hit sign up/ sign in and it will post to the endpoint defined here: https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo
Let me also clarify enrollment and sign in. This is what a user sees, what the Google Pay app does and finally what a merchant needs to do:
Google Pay user navigates to passes tab in Google Pay App, hits "+ Pass":
Google Pay chooses which type of pass to add, hits loyalty for this example:
User searches and presses on the specific program they want to sign up for (theres a testing phase before it goes public, in which only accounts which you tell support team can see the program in google pay app):
User then fills out information to share and consents to share their information with this merchant, then they press continue.
Google Pay Then does a POST request with user info to endpoint defined here on the loyalty class by merchant: https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo
Here is where merchant, yourself would have to be listening for POST to endpoint you defined in the setting mentioned previously and give user form to finish providing all details needed and then redirect to the JWT link to automatically save the pass.
See https://developers.google.com/pay/passes/partners/enrollment-signin for reference.
It turned out that there are two ways to work with cards in the GPay. The first method is described in the documentation here https://developers.google.com/pay/passes/guides/enrollment-signin, the second method is to scan the card(barcode/manually) and use it as a card storage, but card data is not sent to the user’s server. The Loyalty card is simply displayed in the GPay with its number(from barcode/manually) and that's all.
I'm creating some Log Analytics to collect data from Event Hub and Application Insights.
Can Log Analytics reports be viewed by users outside of Azure? For example, can I give to my client a dashboard or report? If not what is the solution?
Can Log Analytics reports be viewed by users outside of Azure?
In short, Yes.
To create a dashboard, select the New dashboard button next to the current dashboard's name.
When you create a dashboard, it is private by default, which means you are the only person who can see it. To make it visible to others, use the Share button that appears alongside the other dashboard commands.
Then go to the Log Analytics portal, enter the query Statement to return record and display in a visual chart.
Finally, pin this to the shared dashboard created earlier by selecting Pin chart to your Azure dashboard button from the middle-right corner of the page.
For more details, you could refer to this article about how to share dashboards of Log Analytics data.
To share a dashboard and be able to add others to be able to share it must be an Owner on the subscription level.
Once you have shared a dashboard, use the Unshare option to change permissions on that dashboard. Clicking on Unshare brings up a new view on the right side where you can now choose Manage users.
Summary: To effectively share and control who has access to your shared dashboard you need owner rights on the subscription. When you want to change who can see your shared dashboard use the Unshare option. Finally, you need at least reader rights to the OMS workspace, contributor rights in Azure to Log Analytics, and reader access to the dashboards resource group to view the various objects on your shared dashboard.
Please refer to this article.
When creating a new app on https://developers.google.com/mobile/add?platform=android&cntapi=gcm, I got the following to check or uncheck:
Share your Google Mobile Developer Services data with Google to help
improve Google's products and services. This includes sharing with
Google technical support, account specialists, and anonymous data for
benchmarking. If you disable this option, data can still flow to other
Google products that are explicitly added.
Unfortunately I accidentally checked the field/allowed sharing.
How can I disable/disallow it now after project is already created? Does anybody know how to do that?
Nothing is explicitly stated on which service this data sharing will be applied. However, just doing a quick search of that statement points to it being used for Analytics only.
And if you want to turn the data sharing off for Analytics, you can refer to this help doc:
Change your data sharing settings
You need edit permission to use this feature.
You must customize your data sharing settings when you sign up for an Analytics account, but you can return to the Admin section of an account and change the settings any time.
To change the data sharing settings:
Sign in to Google Analytics.
Select the Admin tab and navigate to the account you want to edit.
In the ACCOUNT column, click Account Settings.
Edit any setting and click Save.
If you just intend to use the project for GCM, I think it doesn't really matter if you allow it or not.
I am writing a four square application and after reading the push API, I realized that my users will have to authenticate and add a callback URL and all that good stuff listed below:
"To turn on real-time APIs for your consumer, access your consumer's details page by clicking on its name at https://foursquare.com/oauth. Then click the “Edit this Consumer” button in the upper right of the page.
To change your consumer's real-time API settings, pick the desired state from the drop-down menu on that page titled “Push API notifications.” Then click “Save this Consumer. ” You should now see your new notification settings reflected on the details page for your consumer.
If you have not activated a real-time API in the past, you will note that the Push URL field is blank on the details page. To actually receive real-time pushes from foursquare, you will need to edit your consumer again and add a HTTPS-compliant URL in this field."
Most of my users are not tech savvy to do this. How do I as an application provider automate or pre-poulate some fields in order to make it easy for them to register for the push api for my app?
Thanks!
When you enable the Push Api, you're doing it for all users who authorize your service. You will receive push notifications from all your authorized users... they don't have to explicitly authorize you to use the Push API