Um, yeah, actually, uh, this is a quick review of, uh, our, uh, application and the, sorry for interrupting you just to clear, so you may have noticed that there is a, is a latency, uh, while searching the, the blog post here. So in fact, uh, the issue is not caused by, uh, by the, by the application itself, or the Tundra itself. So basically the reason is that, uh, when we just triggers an end point, the local state just spin ups a new docker container to run the service, um, the run, the service application to run the Lambda function. So, so that was the reason that why we see some delays, uh, before we just put a button to trigger a flow. So, so basically that's, that's the reason that we, we see delays in the UI. So that is not related to the, the application logic itself or the Tundra agent itself, okay. Sorry, as you can see as a circumstance, uh, you can see how, how many, a, what is the duration of that invocation also here? Uh, yeah. Uh, thank you for the clarification. Uh, so, uh, yeah, uh, these are the, for, from, for as last words, uh, these are the lambda function functions. Actually. Uh, we are going to test today that you will, you will see these a lot with, with, uh, with these, uh, traces. So actually this is a, uh, a small, um, how can I say, uh, intro, uh, we will see these, uh, these topologies a lot today in the following examples, especially with tasks. So, um, yeah, thank you for that part. Uh, actually all some, maybe you can continue with, uh, Tundra for site, uh, explanation. So, uh, let me just, uh, talk about what, uh, what Tundra Foresight is. And before I deep dive into the concepts that we are, uh, solving, uh, I want to show you our, uh, playground environment, which is a foresight that Tundra that life. So, uh, my friends, uh, my colleagues can share links for you as well. So in this environment, uh, basically this is, this is public to everyone that we, our team is, uh, uh, succeeded, uh, carefully selected the few open source projects. Uh, so here is the list of the few created lists, like seven projects that we integrate the Tundra Foresight with. Tundra Foresight with. And apart from that in the homepage, you will see that there are many more, uh, open source projects that we try to populate the data in this, in this environment. So if we can, uh, for example, we are going to use LocalStack a lot today. So if we go into the local stack, uh, test page, I will show you a simple, a very simple test case to, uh, show how it's, how it's seen from Tundra Foresight and Tundra APM. So if we, let, let's say we select this, uh, this one has a couple of tests in it. And, uh, I want in this screen, let me just, uh, give a quick description of what's happening here. So, uh, here is the, uh, here is your projects test run overview page, which is basically if you run your test on your local or your, on your CI environment, your workflow round as a whole will show up here, and you will see the execution time, how many tests are passed, how many failed, how many skipped, et cetera, and which branch, uh, is it running? So you will have all the metadata to understand what's going on, as well, as you will see that, uh, let, let's actually selected, uh, some complex test to see, see, like, what this, uh, blocks are doing. So in this case on the left side, uh, you will have the old test suites, uh, separated from each other. And within that, you will see the specific tests and here, uh, you will see the most erroneous tests, most, uh, the slowest test suites, slowest specific tests. So this, this, uh, information board will give you, give you the ability to take action. So if your CI world is too slow, if we have, if you have a, uh, let's say a faulty tests, uh, you will immediately see. And, uh, that's for example, clicking this, uh, let us, uh, test, test suite. And, uh, for this specific test suite, we all have the information for before or after and, as well as the before and after. So, uh, let's say, let's say I want to, I want to check one of these tests and, uh, right now we are in the deep dive. So we got right into the specific tests that that's failing, that strobing a redis connection exception. And we'll see the logs here, which is, uh, which is, uh, caught by the thunder agents and you will see the, uh, that's a stack trace of the error. Here. Uh, we also have a couple of tabs here, which is the, will the other important thing, uh, type is the performance step, which shows you a histogram of the last, uh, uh, let's say, uh, 10 rounds, 14 runs within your data retention. You will see the, uh, uh, performance of the, of the specific tests, how long it took. And is it, is it failed or passed in the past in the, in the past? So, um, the, this is quite helpful to, uh, actually catching the, uh, performance effect of your changes. And here is the logs, uh, tab, uh, in the logs that if you have any logs for that, uh, specifically, which in this case, we don't have any log. Uh, you will see them here. Um, and for the second shot, uh, I have a, uh, very good demo. Uh, soon I will, we'll come to that later. Uh, but if you have a, uh, front-end test with, uh, Selenium or browser stack, uh, those sequential that you recorded through your test will show up here. Um, so let's, let's see, uh, how it's going to look on, uh, Thunder APM. I'm hoping this is a integration test and not a unit test, uh, on the left-hand side, we see a trace map button, uh, which is, uh, since you are using your account for all three product, you can click this button and go directly to the APM page for this, uh, specific test, which in this case, this is, this is a one test and we clicked that and you'll see it all the trashed chart and the spams for this, uh, for this test and what's going on with them. So if this test integrated with other services, uh, uh, you will be able to see them here, uh, which we'll show you in the upcoming, uh, demos for, for, for our sample projects. But, um, uh, let's say let's, let's say, let's go to the local state, which I know there is a very simple tests with, uh, with a rescue service, uh, attached to it. So this test success passed in the, uh, in the last, uh, I don't know how many runs here, 10 runs, I guess. And if we click the trophy button, um, we'll say that this specific does integrate, uh, actually talking to AWS, uh, SQ, SQ.
React Summit 2023
Comments