Now that you’ve connected your data sources, it’s time to configure Relvy to access the right data and learn about your system architecture. This configuration process ensures Relvy can effectively investigate incidents and provide valuable insights tailored to your environment.The configuration process has two main phases:
Core Setup: Essential configuration steps to enable Relvy’s basic functionality
System Discovery: Optional but valuable steps where Relvy learns about your system context
First, you’ll define which logs, events, and traces Relvy should analyze. This critical step tells Relvy where to look for relevant data during incidents.
Logs datasets: Define which application logs, service logs, or security logs matter most
Events datasets: Configure which events (deployments, alerts, infrastructure changes) to track
Traces datasets: Specify which distributed trace data to analyze
Most teams already have carefully curated dashboards for system monitoring. In this step, you’ll tell Relvy which dashboards are most important for your debugging workflows.
Import your existing dashboards from Datadog
Ensure Relvy can access your key metrics visualizations
No need to rebuild what you already have - Relvy works with your existing tools
As you progress through these configuration steps, Relvy will become increasingly tailored to your environment. The more context you provide, the more effective Relvy will be at helping your team debug production incidents.Once configuration is complete, your team can start using Relvy to investigate incidents, collaborate on debugging, and reduce alert noise.Let’s get started with your first configuration step: Defining Datasets.