Frequently asked questions (FAQ)
What is Lightrun?
Traditionally, exceptions, logs, performance metrics and traces have always been defined during the development stage. With the advent of the cloud, followed by microservices and serverless architectures, a gap was created between development and the production environment, making it nearly impossible to anticipate production-only issues or reproduce them.
Lightrun is the first platform to shift observability left, empowering developers with 100% visibility into their code regardless of environment or deployment type, from monolith to microservices. With Lightrun, developers have easy access to exceptions as they occur, and they securely add logs, metrics and traces to production and staging in real time, on demand.
Lightrun is integrated into the developer workflow, from the IDE to APMs and logging tools; all instrumentation is added from the IDE you’re already using and directly to your running application, eliminating the need to predict every edge case imaginable or reproduce environments that can’t be reproduced, by enabling you to check issues on the fly.
How does the agent work?
The stateless Lightrun agent is the heart of the Lightrun product. Attach the agent to your application when you launch it. This small library then connects your application process to the Lightrun Management Server, interacting with your application.
When user actions are received, the Lightrun Management Server sends the request to the agent. The agent uses HTTPS for all communication. The agent checks the requested actions through our proprietary sandbox, and once integrity, stability and security are verified, it adds instrumentation to your application during runtime, immediately.
We guarantee stability, integrity and a negligible footprint.
How does the sandbox work?
Whenever a Lightrun action is sent, the inserted code is run in a dedicated sandbox before being added to your application. The Lightrun Sandbox validates there are no side effects to your application’s behavior, and it verifies integrity, stability and security of the instrumentation. Lightrun Sandbox guarantees no exceptions, system I/O, system calls or state/flow changes, and only read-only code is ever added to your running application.
What integrations do you currently support?
Using filebeats, fluentd or other similar data handlers, you can receive all Lightrun logs to your logging tool. Your metrics can be pushed to StatsD and we can export them to Prometheius for scraping. Additionally, we integrate with Slack, Datadog alerts and Sentry.
Sign up for our beta program and be the first to know when we add more.
What languages does Lightrun currently support?
Lightrun currently supports Java, Kotlin and Scala, and we have a bunch of additional leading languages on our immediate roadmap. We’ll also be supporting Node.js and Python soon as well – let us know if this is important to you! Want to get updates and join our beta program for new features and languages?
Sign up for our beta program and be the first to know.
What IDEs do you support?
We currently offer a plugin for IntelliJ and will be adding new plugins as part of our roadmap. Want to get updates when we add new languages? Sign up for our beta program and be the first to know.
Does Lightrun change the state of my code?
We guarantee that our agent does not lead to or cause the execution of syscalls, exceptions or state modifications.
Using our secret sauce and our proprietary sandbox, we ensure application integrity and never write nor change state at the bytecode level.
For more information about security issues, we invite you to download our Security datasheet.
How does Lightrun affect our application server performance? How much of our resources does Lightrun consume?
Our agent is lazy and when idle, its consumption is negligible. Resources are only used when Lightrun actions have been added to the agent and are invoked. When invoked, performance footprint typically hovers around 10s of microseconds per log invocation. In any case, managers can limit agent consumption by customizing configurations.
How is information transferred between the different parts of the architecture?
The communication between all Lightrun components and the Lightrun
server is always established over industry-standard TLS 1.2 encrypted channels.
Certificate pinning is utilized both in the agent and the client. See the Security datasheet for more details.
Is Lightrun read-only?
Does Lightrun support audit trails and RBAC?
Yes, all the actions in the system are audited; additionally you can manage users with more granular out-of-the-box roles.
Do you support PII redaction and Blocklisting?
Yes. You can configure PII redaction for specific regular expressions, and you can customize blocklists for files, member variables, packages etc. in order to limit Lightrun from accessing those objects.
What privacy and security certifications does Lightrun have?
Lightrun is currently ISO-27001 compliant.
Our security policies are approved by Lightrun management at least annually and communicated to employees on a regular basis as part of the security awareness program, which covers various types of security-related training modules.
See our Security datasheet for more information.
Can we store all data on our servers?
Lightrun offers a self-hosted deployment option. With this option, Lightrun is installed within your organizational network or through a private cloud, via Docker or Kubernetes. Your IT or DevOps team is responsible for the ongoing maintenance, as is the case for any other internal/local resource. In addition, all of your existing organizational security controls and policies automatically apply to all of Lightrun’s components.
See our Security datasheet for more information.
Do you have cloud instances in Europe so that the entire data flow can be geographically managed in Europe when needed?
How does Lightrun compare to production debuggers?
Lightrun is a full observability platform, made by developers for developers, that covers all of the developer’s observability needs – debugging, code level alerting, feature verification, pinpoint profiling, context level logs and metrics.
We seamlessly integrate into the developers’ native environments, and make it easy for them to resolve issues quickly throughout all stages of the application lifetime.
What's the difference between Lightrun and reliability and exception monitoring tools?
Lightrun offers line-by-line visibility into your live code and not just exception data enrichment. This is a complete observability platform that covers all of the developer’s observability needs – debugging, code-level alerting, feature verification, pinpoint profiling, context level logs and metrics.
Lightrun is fully integrated into the developers’ workflow, with a plugin native to their IDE and a CLI tool, empowering them to observe and debug their live applications.
Is Community actually free?
The Community plan is absolutely free, no strings attached including one plugin and one agent. No credit card is needed.
Is support included?
We offer chat and self-service support for Community customers. For Professional plan subscribers, we offer dedicated support for technical questions. Additionally, a support SLA is defined to guarantee you get the attention you deserve.
Do you offer a plan based on usage?
We offer customized plans based on your organization’s specific needs, typically based on the number of virtual machines, CPU, number of agents, the number of hosts etc.
Do I need a credit card to get started?
No. You can join the Community subscription without a credit card.