Explore autocomplete helps complete the query you intended to do, taking user experience to the next level by allowing you to query events across your application quickly and uncover deeper insights.
We introduced support for the mongodb package in the Lumigo OpenTelemetry Distro for JS, with support for versions 3.6.6 to 3.7.3 and 4.0.0 to 4.9.1 (the current latest & greatest).
The only step necessary to get MongoDB tracing to containers already traced, is to update the @lumigo/opentelemetry dependency to 1.3.0.
P.S. This update does not apply to the Lambda Node.js tracer, but stay tuned :-)
Since we launched Amazon ECS support earlier this summer, we have come across many user workloads that behave like batch jobs (which, incidentally, we see often scheduled via AWS Batch and, occasionally, via AWS Step Functions). Rather than relying on long-running processes that receive request over HTTP, these workloads execute jobs pulled from the Amazon SQS or sometimes the process environment, perform computation involving databases, other services and messaging queues, and then terminate.
The most intuitive representation for such transactions consist of a "root" span representing the "main" method, with the outgoing requests to databases, messaging queues and other service nested directly under the "main" span. And this is how Lumigo will now represent these workloads, provided that you use the OpenTelemetry API to create the "root" span.
Lumigo now also supports the case where the distributed trace starts with an outgoing request, but given there is no common parent span, multiple such ongoing requests will each result in a separate transaction.
Enjoy this improved support for your containerized workloads and let us know what you think about it!
P.S. If you want a hand using the OpenTelemetry API to create root spans, we are happy to help! Let us know through the support channel, and we'll gladly arrange a call to help you out. It's usually just 5 minutes coding, and then pushing it to your environment to validate :-)
P.P.S.S. Lumigo now also shows Elastic Load Balancers that serve HTTP requests issued by containerized workflows.
Get the full Lumigo experience—even if you aren’t using every feature—with a new in-platform demo. In one-click, fill your project with demo data and see how Lumigo can debug even the most complex of environments.
You can now see and understand Lambda → SNS → SQS → Lambda transactions as one complete trace, end-to-end. This new view gives you critical context into one of the most common–but unobservable–serverless architectures so you can now troubleshoot it faster and easier, with no blindspots.
This feature is available for Node.js and Python. To see the full trace update your Node.js tracer to version +1.72.0 and Python tracer to version +1.1.199.
Cold start duration is now displayed in the timeline of your traces to make it even easier to improve latency end-to-end. Set up alerts to notify you when functions experience a high percentage of cold starts to keep an eye on critical and user-facing functions.
We extended Lumigo's support of OpenTelemetry resource attribute semantic conventions to cover the `cloud.platform` key and the Amazon ECS semantic conventions.
Our goal with implementing the OpenTelemetry semantic conventions is to enable you to get the best integration with Lumigo for your workloads even when not using the Lumigo OpenTelemetry distributions, but rather using upstream OpenTelemetry SDKs.
The Amazon ECS semantic conventions are not yet widely implemented in OpenTelemetry SDKs, but we are very much looking forward to contributing them to the community!
For more information about the OpenTelemetry semantic conventions supported by Lumigo, refer to the OpenTelemetry Supported Semantic Conventions documentation.
Lumigo Tags add dimension to your Lambda functions so that they can be organized, searched for, and filtered in Lumigo, helping you simplify the complexity of monitoring distributed applications.
Amazon Elastic Container Service (ECS) monitoring is now generally available in Lumigo.
The Clusters view gives you an overview of your ECS clusters, the trends of usage of their resources, and you can jump with a click into the traces running through those clusters.
The Services view provides you with an overview of the ECS services on a cluster, including their status, launch type, CPU or memory utilization trends, deployment configuration. With one click, you can jump to the traces involving each service.
The Tasks view offers an overview of the tasks on a cluster or a service, including their status, launch type, resource limits, and the corresponding traces.
With the arrival of containers in Lumigo, we touched up the default dashboard to show also information about your containerized workloads. These changes are visible only in the Lumigo projects that have not customized their default dashboard.
The distributed tracing of containerized applications on Amazon ECS is powered by OpenTelemetry. We published two OpenTelemetry distributions for Node.js and Python, and Lumigo can now ingest distributed-tracing data from any OpenTelemetry SDK via its new OTLP+HTTP endpoint.
Quickly isolate and understand specific performance issues (i.e. spike in failures) with enhanced zoom-in capabilities for charts and graphs. Instead of manual filters, you’ll be able to highlight what’s important and seamlessly check all relevant metrics without noise, across the entire platform.
