WEBVTT

1
00:00:00.000 --> 00:00:03.545
When a transaction slows down, you need to understand where time

2
00:00:03.555 --> 00:00:07.160
is spent across services, database calls, and messaging.

3
00:00:07.915 --> 00:00:10.665
IyziTrace is an observability platform that brings

4
00:00:10.675 --> 00:00:13.080
those system relationships into the investigation.

5
00:00:13.570 --> 00:00:15.415
OpenTelemetry is the foundation.

6
00:00:16.010 --> 00:00:20.415
Metrics, logs, and traces are collected using a common standard,

7
00:00:20.610 --> 00:00:24.500
reducing dependence on a single provider at the data collection layer.

8
00:00:24.510 --> 00:00:27.780
The detail you see depends on the instrumentation

9
00:00:27.790 --> 00:00:30.655
you enable and the data your applications send.

10
00:00:30.995 --> 00:00:34.145
Start with the system context: which service runs

11
00:00:34.155 --> 00:00:38.080
on which host, who calls whom, and which resources are shared?

12
00:00:38.415 --> 00:00:40.905
Traffic and error indicators across service

13
00:00:40.915 --> 00:00:43.760
flows help you choose where to begin investigating.

14
00:00:44.355 --> 00:00:47.500
Inventory is built automatically from incoming telemetry.

15
00:00:47.715 --> 00:00:49.925
Hosts, services, databases,

16
00:00:49.935 --> 00:00:53.145
and messaging components are listed with their discovery evidence.

17
00:00:53.155 --> 00:00:55.525
You can see which signal identified

18
00:00:55.535 --> 00:00:58.380
a component and when it was first and last seen.

19
00:00:58.615 --> 00:01:03.180
A lack of recent data does not, by itself, mean a component is down.

20
00:01:03.675 --> 00:01:08.000
Trace Pulse lets you explore returned traces by duration and observed errors.

21
00:01:08.355 --> 00:01:12.600
A separate Trace Detail example shows one request with nine nested spans.

22
00:01:12.895 --> 00:01:15.740
Their durations overlap within the overall trace,

23
00:01:15.875 --> 00:01:18.560
helping you see how the request moves across services.

24
00:01:19.005 --> 00:01:21.095
In the relationships view, checkout

25
00:01:21.105 --> 00:01:23.570
publishes messages and accounting consumes them.

26
00:01:23.725 --> 00:01:28.170
These discovered relationships provide system context for the AI investigation.

27
00:01:28.525 --> 00:01:31.250
A separate investigation starts with a question:

28
00:01:31.365 --> 00:01:35.510
the accounting service has a performance problem. What is happening?

29
00:01:35.705 --> 00:01:39.210
The assistant builds a plan, consults the inventory,

30
00:01:39.245 --> 00:01:42.690
and queries connected metrics, logs, and traces.

31
00:01:42.945 --> 00:01:46.730
Those discovered relationships guide its investigation of the system.

32
00:01:46.955 --> 00:01:49.585
The assistant considers consumer processing

33
00:01:49.595 --> 00:01:52.340
or scheduling behavior among the possible causes.

34
00:01:52.455 --> 00:01:54.385
It presents supporting records

35
00:01:54.395 --> 00:01:57.120
and recommends the next checks for your team to verify.

36
00:01:57.675 --> 00:01:59.825
Your team can review findings alongside

37
00:01:59.835 --> 00:02:02.580
the evidence and decide what to investigate next.

38
00:02:02.865 --> 00:02:04.250
Explore IyziTrace.

39
00:02:04.355 --> 00:02:06.020
A product by AntrekLabs.