CloudWatch Logs not showing up anymore after switching from Alexa-hosted to custom skill - alexa

Since I switched from building an Alexa hosted skill to building a custom skill using the ASK SDK no logs are showing up in my CloudWatch interface. Before I could simply click on Code > Logs: Amazon CloudWatch and were presented with the logs of the previous session. If I navigate now to the cloud watch console no logs for my custom skill are showing up. I am sure that this is because of wrong configuration but sadly I could not find any documentation about this online. Maybe someone had the same issue before and can help me out with his expertise. Thank you very much!

I finally found the answer to my question. All my resources like EC2 instances were running in the eu-west-1 region. I had to go through all regions in cloud watch to find out that the log files for my alexa skill are stored in the us-east-1 region. Only there, they are visible.

Related

App/website model not showing on Alexa Developer console

I am trying to connect my alexa skill with the custom android app. For that I need App/Website model in Alexa developers console. But I can't find it. Is there anything I need to do to activate that model option.
Alexa for Apps is a currently only available to select developers as part of a developer preview program. To use this feature, you must register for the preview.
For more information, please see the documentation here:
https://developer.amazon.com/en-US/docs/alexa/alexa-for-apps/use-developer-console.html

Writing azure consumption Logic app traces to App Insights

Can I send traces of steps in my consumption logic app workflow to any application insight? Is there an out of box provision for the same?
While you are linking application insight to your logic app which ever application insight you provide in logic only those traces will be sent to email.
You can go through the Microsoft Document for further information.
As far as I know, there is no out of box connector available to trace logs in Application Insights for Consumption Logic App.
There are two options available
Use Tracked Properties to send custom fields that needs to be tracked to Log Analytics Workspace.
Check this
Invoke Azure Function from Logic App to log into App Insights.
or you can use Standard LA which is recommended for enterprise production scenarios

Stackdriver logs not showing in UI

For some reason my project is not showing logs in the page https://console.cloud.google.com/logs/viewer and I'm prompted with the message:
Welcome to Cloud Logging
View, search, analyze, and download your project's log data, all in one place. This is where you will find the logs for all your projects and Cloud Platform services.
You do not have any logs in your project right now.
However I definitely have logs generated by a google app engine and cloud build, I can access them without a problem using the gcloud command:
gcloud logging read "resource.type=gae_app" --limit 10 --format json
Also, I've enabled error reporting and I can see the logs there for errors, but if I click the label "View Logs" it does nothing.
There's something broken in my project but I'm not sure how to reach support in this case, also has anyone ever experienced something similar ? Is there any action that I can perform that could fix this issue ?
Thank you for any help :)
It magically fixed itself this morning. Yesterday I've enabled stackdriver monitoring in the hope that it could fix the issue, I don't know if that is relevant.
For anyone facing the same problem, best suggestion would be to contact support. For me it fixed automatically after few days :)

"Building skill schema failed" error while deploying alexa skill using ask-cli

I have a alexa skill live on amazon skill store. The interaction model of that skill was developed using the skill builder of alexa development portal and the lambda function was uploaded seperately. The skill is live and has many users.
Recently I felt the need of making some changes to that skill. Since now I am using ask-cli for all my alexa skill development, I decided to use the same for this skill too.
Here are the steps I followed:
cloned the skill from the alexa console using command ask clone and selecting the skill I wanted to make changes in.
made the required changes in the skill. Just changed a response, nothing special.
tried deploying the skill again to alexa console using ask deploy command
But I got the following error:
[Error]: Building skill schema failed
I thought that the changes I made might be the cause of it, so I backtracked the changes and made the code as it was when cloned. Then I tried deployig the code again but the error remained the same.
I went through some answers on amazon portal, the most common cause of the issue for others there was some mistake in URI of skill icon URIs. To be sure, I also removed that line from skill.json and tried deploying it again but nothing changed.
Does anyone has any idea of the cause of the above mentioned issue?
Make sure your lambda function has Alexa Skills Kit as trigger. I solved my problem by adding back the trigger (and entering the skill ID).
This steps might able to fix that problem.
Create a new skill in the developer portal.
Create the Lambda function for that skill then add it as an endpoint.
Download the skill via ask-cli
Copy the code in the existing skill to the new skill.
Re deploy using ask-cli.
It might be due to permission error or the appropriate profile used during deployment is configured incorrectly or missing.
If the cause of the issue is your image urls in Skill.json file try this hacky solution
Goto your Alexa skill development portal and select "distribution"
tab
In that upload both small and large icon. ( Do not press save ) if its a new skill,
right click on the image and select open image in new tab and copy
the image URL. now use this URL in the skill.json
This is what i used in my skill when s3 url are all causing issue.

Unable to create project in Google Cloud: "Cloud Service disabled by admin. Please contact admin to restore service"

I try to create my first Google Project, and i got this error
Create Project: My Project
APPHOSTING_ADMIN Cloud Service disabled by admin. Please contact admin to restore service. com.google.apps.framework.request.StatusException: generic::FAILED_PRECONDITION: APPHOSTING_ADMIN Cloud Service disabled by admin. Please contact admin to restore service
Anyone any idea?
I am the admin from the GSuite account. I had checked my permission stuff in my account and I don't think there is a place for me to disable me from using GCP.
One possible reason for such error message would be the disabled G-Suite access to the Google Developers Console service.
Check in your GSuite Admin console Apps -> Additional Google services if Google Developers Console is enabled:
If it's not - enable it and re-try
Sorry to bump an old thread - but I just ran into this and wasted 20 minutes trying to figure out. Google Cloud Project (and Dev Console) were on for everyone but I could not create a project logged in as the Super Admin.
Go to Apps and click on Google Cloud Console. There's a single option 'Allow users to create projects' and for some reason in this company's tenant... It was unchecked. Checked it and project created. Bizarre. Has always been on for other clients apparently.
It seems I had the same or a similar issue- "google cloud platform service has been disabled error". Due to it, I could not create projects.
It seems the trouble was related to my university's email account
foo#mail.huji.ac.il. Once I used my gmail account the problem was solved.
This response from Google support resolved the issue for us:
To activate this service, please follow the steps:
1- Access the admin console and go to Apps -> Additional Google Services
2- Look for the service “Google Cloud Platform” and click on the box next to it
3- In to top right corner click in “ON”
4- Confirm you want to turn it on in the pop-up box.

Resources