Create Backends

A backend is a database or a remote service such as a message queue, HTTP service, or cache service that your application uses. A backend component is not itself monitored by the application agent, but the agent monitors calls to it from instrumented servers. You need to create backends in the instrumented environment so that the agent registers them. Creating and adding the backend to the instrumented application involves:

  • Naming the backend
  • Setting its identifying properties
  • Optionally, configuring how the backend is presented in the Controller UI

Identifying Properties

A backend has identifying properties. These vary depending on the type of the backend and the types of information that you want to display. The Controller displays identifying properties in backend dashboards. You must set at least one identifying property for the type of any backend that you plan to add.

The following shows the backend properties in the Controller UI for an MySQL database:

Resolve to a Tier

By default the Controller doesn't display a detected backend as a separate entity in flow maps, but the agent reports its metrics as part of the downstream tier. If you want to display the backend as a separate component and not resolved to the tier, set resolve to false. See Resolve Remote Services to Tiers.

Backend Example

The following listing shows an example of setting up a database backend.

backendName := "Cart Product Database"
backendType := "DB"
backendProperties := map[string]string {
"DATABASE": "sqlite3",
}
resolveBackend := false
appd.AddBackend(backendName, backendType, backendProperties, resolveBackend)