How CtrlB works?

Architecture

CtrlB platform comprises of three components:

• Backend server [codenamed: Atlas] This is the backbone of CtrlB which is offered as a SaaS solution.

• IDE extensions [codenamed: Plugins] These extensions allow you to add, remove or modify tracepoints from the comfort of your IDE.

• Application agents [codenamed: Heimdall agents] Our agents run alongside your applications and return dynamic snapshots and log events based on the trace points you've set from IDE extensions.

In Norse mythology, Heimdall has incredibly acute senses, particularly his sight and hearing. He can perceive nearly all that occurs within the Nine Realms, allowing him to detect the presence of individuals, even across great distances. Our agents are also great at sensing exceptions and obtaining stack traces from everywhere in the system.

How do CtrlB's components interact?

As you integrate the Heimdall agent with your application, it connects via HTTPS to the Atlas server, which allows for secure communication.

Using the IDE extensions, you can interact with the Heimdall agents running with your applications again via the Atlas backend server. This includes things like creating trace points and log points. These requests get sent to the Atlas backend, which further relays them to appropriate Heimdall agents.

When a tracepoint gets triggered, the associated Heimdall agent sends an event to the Atlas backend, which further relays this to the appropriate IDE extension which created this trace point so that you can see this data directly in your IDE.