Helix
Triumph TechLava DocsRock Styling
  • Getting Started
    • 👋Welcome
    • Overview
    • Customizing Rock
    • Plugin Installation
    • FAQ
    • Roadmap
    • 🚨Security
  • HTMX
    • Learning More
    • Syntax Style Guide
  • Lava Applications
    • Overview
    • Applications
    • Endpoints
    • Content Block
    • Magnus
    • Observability
  • Lava Commands
    • Delete Entity
    • Modify Entity
    • DB Transaction
    • HTTP Response
    • Render Lava Endpoint
  • Forms & Controls
    • Understanding Forms
    • Using Form Controls
    • Creating New Controls
    • Form Validation
    • Loading Indicator
  • Strategies
    • Tips
    • Related Entities
    • Limitations
Powered by GitBook
On this page
  1. Lava Applications

Observability

PreviousMagnusNextDelete Entity

Last updated 1 year ago

We expect our applications to be fast. Embracing the principle of "inspect what you expect," we've integrated observability into each Lava Endpoint call. Activities for each endpoint are named using the pattern: LavaEndpoint: {LavaEndpoint.Name} | {LavaEndpoint.LavaApplication.Name}.

Additionally, we add the following attributes to the root activity:

  • rock.lava_endpoint: the name of the endpoint.

  • rock.lava_application: the name of the application.

The HTTP method for the call is already an attribute on the observability activity.

As you develop your Lava Applications, it's crucial to monitor this observability data to ensure your endpoints are efficient and minimize excessive database calls.

Be sure to sign-up for the non-profit plan at New Relic. More information on Rock's Observability features can be found in the .

Admin Hero Guide