Serverless Stack

We really need to give Thundra a try, you have made so many cool features we picked the wrong provider  :man-facepalming::skin-tone-3:

It is still not too late <@U023P23G6JH> :slightly_smiling_face: we are always here to help you

Thank you for your answer.
Actually I thought that enabling it with *Asynchronous Monitoring* will be easier, because the extension needs another layer on top of each lambda, please correct me if I am wrong

it is just another layer (in addition to Thundra agent layer) which contains a Lambda extension to report collected telemetry data asynchronously after invocation

So the other option will be better, because it depends on a separated lambda which collects data, right? <@U02L3TG306N>

All what it needs is enabling `thundra_agent_lambda_report_cloudwatch_enable` in each lambda, and make sure that I have the thundra cloudformation stack

Sorry <@U02L3TG306N>
I was checking my functions, I didn't find a function named `thundra-lambda-adapters-cw`
I integrated my aws account using wizard after signup
did I miss something?

Hi <@U02DH3FQCJC>, have you applied this setup: <https://apm.docs.thundra.io/performance/zero-overhead-with-asynchronous-monitoring#1.-setup-thundra-lambda-adapters-cw>

Basically it just creates another Lambda function and that Lambda function is registered to the log groups of the target lambda functions

Unfortunately, there is not automated way of it for SST

&gt; _If you aren't using AWS integration, you'll need to install the following Lambda function:_
&gt;  _`thundra-lambda-adapters-cw.`_
due to docs, I thought that AWS integration is the process which I did on signup and created the cloudformation stack, sounds I missed something in docs

You are right, as long as you install `ThundraCloudFormation`, it (and setting `thundra_agent_lambda_report_cloudwatch_enable` env var to `true`) should be enough

Great!
Maybe this stack is creating the function in another name
Actually I got the data on Thundra console, but I wanted to make sure it is being collected asynchronously.

Hmm, sorry but I still have some confusing
I checked the cloudformation stack, it doesn't have a lambda in its resources,
it has
• Custom::ThundraCFCallBack
• AWS::CloudTrail::Trail
• AWS::S3::Bucket
• and some policies and roles


yes, in that case there won't be a lambda named _`thundra-lambda-adapters-cw.`_

but Thundra will subscribe to the logs groups of the Lambda functions

so our backend will get telemetry data from the Lambda logs

to do that, you need to subscribe Lambda functions from the APM console

<https://apm.docs.thundra.io/thundra-web-console/profile/settings-page/aws-tab>

Ok, so can you check whether Thundra subcription filter is there by checking log groups of the target Lambda functions to be monitored?

I meant, do verify by also checking that from AWS CloudWatch Logs console?

ok, thx. did you set `thundra_agent_lambda_report_cloudwatch_enable` to `true`?

Very nice!
I liked what you are working on!
Thank you and sorry for annoying

ah OK. I thought that it doesn't work :slightly_smiling_face:

Hi Bshr,
Are you using Appsync as graphql provider?

I was able to solve that by setting thundra error programmatically, on catch errors

Hello, this image is from docs about logs page, I don't have this page in my console, and I set `THUNDRA_AGENT_LOG_DISABLE: 'false'` env variable
does anyone have any idea?

By default, logs are disabled and can enable with a config but that's not stored or seen for free account. 

and another question:
I have set `THUNDRA_AGENT_APPLICATION_STAGE` env var, but in Query functions there is only `default-project` in function filters
How to use this stage to filter funcions?

Project and stage provide grouping but they meet different needs. Project has one api-key and can be used for searching, querying and creating alerting policy. Stage is a marking and can match one or more projects. And also it support searching and other capabilities if it is set. 

Hmmm, So where can I use stage to query?
And btw, I created a project manually, and get its API_KEY and set it in function environment variables, but its invokes keeps appearing in default-project, did I miss something? <@U033832BS8N>