Listing Thumbnail

    Lumigo - Monitoring & Troubleshooting for Microservices

     Info
    Sold by: Lumigo 
    Deployed on AWS
    Free Trial
    AWS Free Tier
    Lumigo is a troubleshooting and observability platform that autonomously deploys tracing in under 5 minutes with a single click. Automatically capture and contextualize all of the data your developers need to troubleshoot microservice issues in production.
    4.8

    Overview

    Play video

    Lumigo is a troubleshooting and observability platform specifically designed for serverless and containerized environments.

    Observability - Get a comprehensive overview of your entire system's health. See transactions, functions, and managed services in a single view to quickly identify necessary configuration or performance optimizations to keep your microservices performing optimally.

    Troubleshooting and Debugging - Understand the story of every transaction from beginning to end. Get alerted as soon as an issue occurs and instantly drill down to see the issue in the context of an end-to-end transaction. Quickly reduce business impact and find the root cause of any issue.

    Log Management- Seamlessly search and analyze logs at half the cost of current solutions. Lumigo automatically correlates log data with distributed tracing, turbocharging resolution times for unparalleled performance.

    Alerts - With preconfigured smart alerting that works straight out of the box, you can remove that task from your dev backlog, confident that you will always be the first to know about critical issues in your application.

    Live architecture map - With an auto-generated, always up-to-date system map based on real-time execution, team managers and architects have a powerful visual tool for monitoring system architecture, driving architectural discussions, and aiding new employee onboarding.

    Cost analysis - Take full advantage of serverless computing's cost-effectiveness with a granular cost breakdown of every application component. Quickly identify areas of inefficiency and optimize system resources.

    Highlights

    • Identify issues, understand their business impact, and quickly get to resolution.
    • Monitor the health of your distributed environment. Receive real-time alerts when something is not working, along with a link to troubleshooting information.
    • Gain control over your observability expenses without compromising visibility. Lumigo offers a premium logging experience at half the cost.

    Details

    Sold by

    Delivery method

    Deployed on AWS

    Features and programs

    Buyer guide

    Gain valuable insights from real users who purchased this product, powered by PeerSpot.
    Buyer guide

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    Free trial

    Try this product free according to the free trial terms set by the vendor.

    Lumigo - Monitoring & Troubleshooting for Microservices

     Info
    Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
    Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator  to estimate your infrastructure costs.

    1-month contract (4)

     Info
    Dimension
    Description
    Cost/month
    Free Community
    150k invocations traced per month
    $0.00
    Standard
    1M invocations traced per month
    $119.00
    Plus
    5M invocations traced per month
    $359.00
    Professional
    10M invocations traced per month
    $528.00

    AI Insights

     Info

    Dimensions summary

    You choose a plan based on how many invocations you trace each month. The four tiers scale by traced volume: Free Community covers up to 150k invocations, Standard covers 1M, Plus covers 5M, and Professional covers 10M. Each tier is a fixed contract commitment tied to that monthly tracing capacity. You move up a tier as your monthly invocation volume grows. Pricing is not usage-metered within a tier; you commit to the capacity level that matches your expected tracing needs.

    Top-of-mind questions for buyers

    An invocation is a single execution of a monitored service or function that the platform traces end-to-end. Each traced execution counts once toward your monthly limit. The tier you pick sets that monthly cap: 150k, 1M, 5M, or 10M invocations.
    The platform notifies you in advance when you approach your limit. To raise your capacity before your billing cycle ends, contact vendor support to discuss moving to a higher tier. Your tier sets a fixed monthly tracing cap rather than metering each extra invocation.
    Tier changes are not automatic. You commit to one capacity level per contract. If your monthly invocation volume grows past your current cap, you contact support to move to a higher tier before your billing cycle ends.
    lumigo.io
    Helpful?

    Vendor refund policy

    How can we make this page better?

    Tell us how we can improve this page, or report an issue with this product.
    Tell us how we can improve this page, or report an issue with this product.

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Software as a Service (SaaS)

    SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.

    Resources

    Vendor resources

    Support

    Vendor support

    support@lumigo.io  Contact our Support Engineering Team, 24/7 via email or in-app messaging

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Comparison

     Info
    Updated weekly

    Accolades

     Info
    Top
    10
    In Issue & Bug Tracking, Monitoring and Observability
    Top
    100
    In Log Analysis
    Top
    10
    In Generative AI, Log Analysis

    Customer reviews

     Info
    Sentiment is AI generated from actual customer reviews on AWS and G2
    Reviews
    Functionality
    Ease of use
    Customer service
    Cost effectiveness
    Positive reviews
    Mixed reviews
    Negative reviews

    Overview

     Info
    AI generated from product descriptions
    Distributed Tracing
    Autonomous deployment of tracing across microservices and serverless environments with automatic capture and contextualization of transaction data from beginning to end.
    Log Management and Correlation
    Automatic correlation of log data with distributed tracing to enable seamless search and analysis of logs across the system.
    Real-time Alerting
    Preconfigured smart alerting system that provides real-time notifications for critical issues in applications with direct links to troubleshooting information.
    System Architecture Visualization
    Auto-generated, continuously updated visual system map based on real-time execution data showing transactions, functions, and managed services in a single view.
    Cost Analysis and Optimization
    Granular cost breakdown analysis of every application component to identify inefficiencies and optimize resource allocation in serverless environments.
    In-Stream Data Processing Architecture
    Leverages in-stream analytics to investigate data and provide actionable insights without relying on storage or indexing, combining stateless speed and scale with stateful correlation capabilities.
    Machine Learning-Based Anomaly Detection
    Continuous machine learning algorithms monitor data patterns and flows between system components to trigger dynamic alerts based on pattern deviations from the norm without requiring static thresholds or pre-configurations.
    Multi-Source Data Ingestion
    Supports ingestion of logs, metrics, tracing, and security data from any source in any format for aggregated system health visibility with automatic pattern recognition across millions of events.
    Auto-Scaling Infrastructure
    Advanced auto-scaling techniques enable seamless scaling up and down to meet environment demands at any scale with minimal configuration changes, currently processing 3M+ events per second.
    Multi-Interface Query and Visualization
    Provides data access and insights through multiple interfaces including purpose-built UI, SQL clients, Tableau integration, CLI, and full API support for flexible querying and visualization.
    AI-Powered Root Cause Analysis
    Automatically investigates alerts and pinpoints root causes with 5x faster analysis capabilities.
    Natural Language Query Interface
    Enables querying of observability data using conversational natural language to identify issues and receive actionable insights.
    Real-Time Anomaly Detection
    Detects system anomalies in real-time to prevent incidents before they impact users.
    OpenTelemetry Integration
    Supports standardized OpenTelemetry integration for unified data collection across logs, metrics, and traces in cloud-native environments including Kubernetes, serverless, and microservices.
    Multi-Tiered Storage Architecture
    Implements multi-tiered storage and data management capabilities to optimize telemetry data retention and reduce storage costs.

    Contract

     Info
    Standard contract
    No
    No
    No

    Customer reviews

    Ratings and reviews

     Info
    4.8
    86 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    85%
    15%
    0%
    0%
    0%
    3 AWS reviews
    |
    83 external reviews
    External reviews are from G2 .
    Hardik Murdia

    Advanced AI observability has reduced incident investigation time and improves trace-based insights

    Reviewed on Nov 17, 2026
    Review from a verified AWS customer

    What is our primary use case?

    Our main use case for Lumigo is as an integrated observability platform within our existing systems. We use it extensively for monitoring as well as distributed traces from applications, and we currently manage them in Lumigo.

    The biggest advantage I have seen in how traces help our team investigate and resolve issues in practice is that the tracing solution of Lumigo is excellent, and it helps identify issues during P0 or P1 incidents. When an incident comes in, we can see the journey of the document, the issue, or the error, and what happened at that point in time, and we can correlate it with the application-level logs. We can then check exactly what happened. The search time during the complete investigation of an issue is very low when you have Lumigo as your observability platform. We were using Honeycomb in the past, but the overall subscription rates are a little higher now, so we switched to Lumigo.

    There is one more aspect of practical investigation during issues, which is the monitoring of each and every box we have, in terms of VMs or EC2. When I say pods, I mean Kubernetes pods. All of these are integrated in such a way that they send metrics to OpenTelemetry collectors, and these OpenTelemetry collectors send the metrics to Lumigo. That way, we manage everything properly. The overall outcome is a complete AI observability experience, which helps us locate problems beforehand, and it is a good solution for us.

    How has it helped my organization?

    Lumigo has definitely had a positive impact on our organization. The standard plan we have right now, which is a 1 million trace plan, has helped us reach many solutions beforehand. There were latency problems coming from the code, which we were able to investigate further. In AWS Lambda, we have something called a cold start problem, but in this case it was not actually a cold start problem. There is a Boto library which is used to connect to AWS services. If you run that inside a Lambda function, you have to provide enough memory for that Lambda. If you do not provide enough memory, it leads to bloating of that particular dependency inside the Lambda code, and that leads to a latency of almost three to four seconds before the Lambda actually performs the action. That causes a lot of latency during the overall operations.

    What I have understood during the whole exercise is that the traces were already being sent via OpenTelemetry collectors to Honeycomb before we started using Lumigo, but Lumigo has given us more in-depth details about which memory setting would be a better fit for our Lambda. That has given us proper T-shirt sizing during our investigations.

    Once we identified the memory sizing issue, we reduced latency significantly. I have documented it on my website, where you can check the traces and screenshots. The overall time of the landing page was around seven seconds, and we brought it down to 500 milliseconds. That is a huge saving in the latency of the overall Lambda function. The memory configuration in the Lambda function had been left at the default of 128 MB, which was taking a lot of time. Later, when we moved it to 560 MB+, the Lambdas performed well, and we were able to identify and resolve that issue right away.

    What is most valuable?

    The best features Lumigo offers include AI agent observability, which they do very well. I also love the Kubernetes observability, and they have a solution for serverless systems as well. One use case I have seen is during Lambda integrations, covering whatever traces or metrics we had at that point in time. These are not system metrics but application metrics. We fetched them via an OpenTelemetry collector and sent them to the Lumigo platform, and that helped us correlate things very well. These are short-lived serverless systems where you do not have access to the underlying infrastructure in any way or form, so you have to rely extensively on the metrics, the logs, and the traces you receive. It has helped us correlate things well there. The AI agent, alongside the overall experience, is extremely good, and it correlates things properly.

    The AI agent helps connect signals and narrow down problems faster. We do not have to look into metrics. It provides a short detail on what happened and what the root cause is before we even go there. The best part is the troubleshooting with the graph or service map it provides. In that map, it even provides an error message on what happened in which service. It is extremely useful. We also have the log details, and we can have metrics from any of the infrastructure or platform solutions we use, and we can correlate those metrics very well. We already have OpenTelemetry collectors, which are very essential for us. The Copilot, which runs on the platform itself, is very helpful because it provides the root causes right there, and you can apply the fix directly on your system and the problem is solved.

    The accuracy and reliability of Lumigo's AI output is reasonably reliable, particularly when there is sufficient telemetry and context. If you have the information of a complete trace, you will definitely get good results, and you would have to observe a trace. The AI will do its job and give you the complete response summary. The biggest advantage is that it does not rely on generic AI responses. They have their own harness engineer or agent, so it uses the application traces, logs, metrics, and request-response payloads to understand what is happening across the distributed trace or the services. It shows how things are moving, how the data is moved from the very first point to the database, and how the response has gone from the database back to the service which requested it. For this kind of information, you do not even have to open any dashboard. You can see it on the AI dashboard itself when you are doing question-answering with the Copilot they provide. That is a good overall experience for us.

    What needs improvement?

    The best part about Lumigo is that it has connected OpenTelemetry collectors, so you can send everything there and have whatever you need. The challenge I faced, and the improvement I see, relates to organizations that operate thousands of microservices across geographical regions, where scalability and ingestion cost become a concern. The current data sampling is very important because you cannot have each and every data point. We use and filter via OpenTelemetry collectors, so we do not have any problem. However, if someone is using your own interface, they will see a problem. I would like to see broader OpenTelemetry protocol support and more comprehensive integrations across all the observability signals, be it traces, metrics, or logs. The only improvement needed as of now is the lack of certain protocol integrations. I want to have richer traces and richer metrics around it.

    That is the only improvement I need. If that integration part is there, then it is definitely good.

    For how long have I used the solution?

    We have been using Lumigo for almost eight months now.

    What do I think about the stability of the solution?

    Lumigo is quite stable. We have not faced any outage or any problem as of now.

    What do I think about the scalability of the solution?

    Scalability is good. We are sending good amounts of traces, and we have not seen a lot of problems, to be honest.

    How are customer service and support?

    Honestly, I do not need customer support. I generally do debugging on my own, and we do not have a very complex case, so we do not need specialized service or specialized support from the customer team. Overall, I think it is okay.

    Which solution did I use previously and why did I switch?

    Our previous solution for traces was Honeycomb, and right now we are using Lumigo for traces. Honeycomb was very good, but the cost suddenly increased. They previously had a $130 offering, which had a 1 million event ingestion cap, and I think they have moved it to something around $290. Lumigo, on the other hand, is on the market as one of the cheapest options.

    For metrics, we are using SigNoz, and there is a reason for that. We have invested a lot of money as well as engineering hours, so we do not want to move out of SigNoz. It provides a great dashboard overall in terms of metrics, and it is cheaper for us because we have a lot of events that get ingested directly.

    What was our ROI?

    We have definitely seen a return on investment. You do not have to look at the dashboard every time, and you do not have to correlate manually. The AI takes care of correlating things. Because they have their own harness engineering at the back end, it does not give you generic AI responses. It provides a complete biopsy, or a complete breakdown, of how things work and how things move. That is a good, relevant ROI for us. I can also share certain metrics which show how much time was previously spent during the Lambda processing and how the response time came down when the latency got down. That is an effective metric for us.

    I am the only person managing the observability platform, along with one more engineer in the UK, or rather, on the US shift. We are both managing it, and we do not have any other engineer to manage it. It is definitely good.

    We frequently get incidents, and the volume of incidents is fairly high. I will not say that this particular correlation alone has saved us time, but it has given us at least a 30-40% time saving during the whole investigation process, because we do not have to do anything manually. If you have the traces, the logs, and the metrics ingested into the same platform, the correlation is extensively good. That is where I think 30% of the time has been saved. However, we are not sending a lot of metrics there, which I think is a problem, so better correlation is not there right now.

    What's my experience with pricing, setup cost, and licensing?

    As per my understanding, the starting cost of Lumigo is definitely low. We started with a $99 plan. I remember we even started with a $0 plan in the beginning, and then we switched to $99 because we need at least 1 million events ingestion for the traces. We are not sending the metrics to Lumigo right now because the number of events is very high and huge in volume. We are doing that on our on-prem systems, where we send everything to SigNoz and make sense of it there. Larger deployments will definitely require a lot of cost and other things. The setup is very simple to manage.

    Which other solutions did I evaluate?

    I have been working with observability for quite some time, so we have definitely evaluated a lot of solutions before choosing Lumigo. Previously we were thinking of using SigNoz itself as our core tool, but its tracing is not that great, to be honest. We also tried to ingest certain parts into Datadog, but Datadog is extremely expensive when you have a lot of VMs and deployments. For systems that are very extensive to use, we were using Prometheus and Grafana, but these are more self-managed services. We did not want that headache, which is why we opted for Lumigo. It is an okay solution for us to move forward with.

    What other advice do I have?

    Overall, on a scale of 1 to 10, I rate Lumigo a solid eight. Everything has room for improvement, so it is a solid eight. One thing I missed in the previous question is that gRPC is not directly configured. You have to use OpenTelemetry collectors, which export all of those traces or metrics. Currently they do not support it, and the OTLP metrics endpoints are also not there. Other than that, it supports most things, including the auto-instrumentation aspects. Overall, I think 7.5 to eight is a reasonable number for Lumigo.

    I would give Lumigo an eight because it does the job, but it is similar to other platforms. I am also not sure whether Lumigo is getting shut down. It seems they are shutting it down, I think in January or December this year.

    Lumigo's AI governance and security are good. Security-wise, they have a good overall setup. Whatever we send is not very high-volume or very sensitive in nature, so we do not worry much about it. For both metrics and traces, we are not sending a lot of information. The tags we are sending are very generic, such as the resources and other information which are not very sensitive in nature. We are not sending any passwords, and everything is redacted, so we do not concern ourselves much about security aspects. I do not see any problem with the governance aspect either, and it is good. I think Lumigo has recently been acquired by Dash0, and they have HIPAA and other protocols integrated. If they are functional in the UK market, then they are probably compliant enough to handle the dataset.

    Our deployment model for Lumigo is public cloud, and we manage everything via AWS. We use AWS as our cloud provider.

    The reason for the doubt is that Lumigo has recently been acquired by Dash0, and I am not sure how well they will offer Lumigo to other people, because Lumigo is getting shut down. It will soon be integrated with Dash0, so this is something very near. I think 31st December 2026 is the date the website says, as I was told to check. So Lumigo is about to end.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Vinay Lal

    Distributed tracing has transformed our testing workflows and now uncovers hidden failures fast

    Reviewed on Nov 01, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for Lumigo involves operating a high throughput machine learning inference pipeline and asynchronous microservices combining AWS Lambda, EKS containers, DynamoDB, API gateways, and event-driven queues. As the head of testing, my primary challenge was diagnosing non-deterministic failures, latency spikes, and silent drops during the automated end-to-end testing and regression and performance test suite.

    Lumigo has helped across our staging, pre-production, and production environments to achieve end-to-end distributed transaction tracing, and it has allowed our QA and SDET teams to immediately pinpoint the root cause down to specific payloads broken down, stream the API contract, and the database queries timeouts. It has also helped in digging through the fragmented logs and providing us the information we needed.

    Lumigo fits into my daily workflow by utilizing zero-code and auto-instrumentation, which has helped us to roll out the distributed tracing in literally minutes, so we did not have to mandate the tedious SDK boilerplates or manual scan creations across dozens of microservices repos. Lumigo helped to inject itself natively on the cloud with OpenTelemetry integration.

    How has it helped my organization?

    Lumigo has positively impacted our organization with transformative ROI for our quality engineering and delivery cycles, where the meantime to defect and resolve due to debugging failed end-to-end integration test runs has dropped over 68.3%. What previously took an SDET two to four hours of log plunking is now identified within three to five minutes directly via the Lumigo trace, representing a huge improvement on numbers. Additionally, the release velocity with blocked QA pipelines due to flaky or non-reproducible asynchronous microservices errors has decreased by 73.5%, directly accelerating our sprint release cycles. I have seen the infrastructure defect production catch dozens of silent failure states that led to queue overflows and third-party API rate limits during pre-prod load testing before they hit production, which has reduced the infrastructure defect rate by 73.88%.

    The improvements in my team's workflow and morale are evident, as the velocity of both the engineering and QA teams has improved, leading to a 48% improvement in internal collaboration, which is a game changer for our overall project, allowing us to collaborate better, understand each other better, and work better.

    What is most valuable?

    The best features Lumigo offers include the live stream architecture and transaction mapping, which helps to automatically generate and update the visual execution topology for every single test transaction. After seeing the exact flow from the edge API through intermediate queues and containerized microservices down to managed storage, it gives our QA engineers instant context. Additionally, I love the request-response payload inspection feature, which captures input and output parameters, request headers, and invocation payload safely. When an automated integration test fails, the exact offending payload is visible right inside the trace, helping to save our QA and engineering teams a lot of time, leading to at least a 48.33% drop in wasted time previously spent finding the root cause.

    With automation saved, automated root cause correlation has helped to correlate logs, metrics, and trace spans across asynchronous boundaries, which is notoriously difficult to debug in event-driven AI pipelines. The live stream architecture and transaction mapping make such a difference for my team, as it generates updates regularly via visual execution and the topology for every single test transaction, providing us with a view through intermediate queues and microservices to managed storage, giving engineers instant context of transactions and payloads, which saves at least 49% of our time and allows overall resources to be used more effectively.

    Regarding Lumigo's AI capabilities, I find the governance of security to be really good, and we have seen a positive impact due to the AI capabilities alongside strict compliance regulations such as SOC 2 and ISO 27001, proving it is compliant with applicable regulations and policies. Lumigo's accuracy is close to 100%, making it very reliable. Lumigo integrates seamlessly with other AWS services we use, and we have not faced any issues.

    What needs improvement?

    Everything works as expected with Lumigo, so I do not have any challenges to report.

    For how long have I used the solution?

    I have been using Lumigo for almost two and a half years.

    What do I think about the stability of the solution?

    Lumigo is a 100% stable solution, and I have not faced any challenges or lags.

    What do I think about the scalability of the solution?

    Lumigo's scalability is impressive, as during high stress testing where our system scales up to tens of millions of invocations in hours, it ingests and processes telemetry without dropped traces or noticeable latency lag in the dashboard UI, making it a great scalable solution.

    How are customer service and support?

    Customer support is really great, and when I had a query regarding optimizing the tracing rules or simplifying sampling behaviors, their engineering team responded within 45 minutes and resolved my queries. I rate customer support a 10 on a scale of one to ten.

    Which solution did I use previously and why did I switch?

    I did not use a different solution before choosing Lumigo.

    How was the initial setup?

    The initial deployment of Lumigo was straightforward and frictionless, as it was onboarded via our AWS account using CloudFormation, taking less than an hour. From a testing perspective, I was able to link trace IDs into my Playwright, Cypress, and Postman automated testing reports within the very first week, making the initial deployment really easy to do.

    I was able to configure Lumigo within a week, so it was easy to integrate into the environment we have.

    Which other solutions did I evaluate?

    Before choosing Lumigo, I evaluated AWS X-Ray, New Relic, and Datadog.

    What other advice do I have?

    I rate Lumigo a five. I choose a five for my rating because it is a great solution. My advice for others looking into using Lumigo is that anyone looking for an exceptional solution should definitely get them on board.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    reviewer2900247

    Proactive microservice monitoring has improved alerts while support still needs to grow

    Reviewed on Sep 18, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for Lumigo is microservice monitoring in my day-to-day experience.

    A specific example of how I use Lumigo for microservice monitoring involves comparing it to other tools such as Dynatrace and CloudWatch. Lumigo is different, particularly in terms of the UI, which works well for me. The tool can alert us when Lambda functions have errors, and it works not only with Lambda but also with agents and other integrations.

    In my current role as a DevOps engineer, I have been deploying agents, and my main responsibility is troubleshooting and monitoring. I need to receive alerts in the appropriate place, and Lumigo helps us more effectively than Dynatrace or other tools we have. The version upgrades you have been working with are good.

    What is most valuable?

    The best features Lumigo offers are troubleshooting and alerts.

    What I appreciate about the troubleshooting and alerts is that while they are similar to other tools, I prefer Lumigo from the UI perspective. Any new member, whether from the development side or business team, finds the user-friendly UI easy to understand. This is the reason I have been recommending it.

    Lumigo has impacted my organization positively, but we are in a starting phase and have not explored it deeply. Our people need to use this tool more, and we have not yet fully adapted to it.

    What needs improvement?

    I think support needs to be improved.

    Lumigo can be improved particularly in support. When comparing it with AWS monitoring, Dynatrace, or other solutions, if we encounter any trouble, everyone looks for support. If your team could improve support, it will be valuable for any company.

    For how long have I used the solution?

    I have been using Lumigo for a few months, and it has been very interesting.

    What do I think about the stability of the solution?

    Lumigo is stable in my experience so far.

    What do I think about the scalability of the solution?

    The scalability of Lumigo is very good.

    How are customer service and support?

    Customer support is good. I would rate customer support on a scale of one to ten as ten out of ten.

    Which solution did I use previously and why did I switch?

    Before Lumigo, I previously used Dynatrace.

    I have not yet switched from Dynatrace to Lumigo because we are planning to adapt to the new UI.

    How was the initial setup?

    My experience with pricing, setup cost, and licensing was good, and I rate it ten out of ten.

    What was our ROI?

    In terms of return on investment, I have seen time saved, and I rate this ten out of ten.

    What's my experience with pricing, setup cost, and licensing?

    My experience with pricing, setup cost, and licensing was good, and I rate it ten out of ten.

    Which other solutions did I evaluate?

    Before choosing Lumigo, I did not evaluate any other options.

    What other advice do I have?

    Since we are still in the early stages, the main things I hope to achieve with Lumigo as my team starts using it more are ongoing based on requirements. Integration is not a direct process with our application; there is a specific process involved. When we integrate with an enterprise solution, there are specific needs to be met. It is not simply about using the tool; it needs to be adapted to the enterprise system. I rate this review seven out of ten overall.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Martin W.

    Very useful tool

    Reviewed on Dec 12, 2023
    Review provided by G2
    What do you like best about the product?
    It cumulates all serverless functions over all regions and accounts, perfect for monitoring.
    What do you dislike about the product?
    It takes very long until new errors appear
    What problems is the product solving and how is that benefiting you?
    A very good overview
    Arootin A.

    Easy to setup, amazing monitoring features

    Reviewed on Dec 02, 2023
    Review provided by G2
    What do you like best about the product?
    Ease of setup and integration
    Features
    Quick to respond customer support
    Very easy to learn and use
    What do you dislike about the product?
    Customization needs a little improvement
    What problems is the product solving and how is that benefiting you?
    Lumigo helped us with monitoring our serverless applications running in the cloud. The transparency provided by Lumigo is unmatched in the industry. Without having to change much in the codebase, we were able to get a complete monitoring platform provided to us.
    View all reviews