LogViewer
A modern log viewer with AI-assisted analysis (Qt 6)
Loading...
Searching...
No Matches
ui::qt::anonymous_namespace{DashboardPanel.cpp} Namespace Reference

Functions

bool FieldOccurs (db::EventsContainer &events, const std::string &key)
 True if any of the first events carries key.
 
std::string ResolveTypeField (db::EventsContainer &events, const std::string &configured)
 
std::vector< std::string > ResolveActorFields (db::EventsContainer &events)
 

Variables

constexpr size_t kFieldProbeEvents = 200
 

Function Documentation

◆ FieldOccurs()

bool ui::qt::anonymous_namespace{DashboardPanel.cpp}::FieldOccurs ( db::EventsContainer &  events,
const std::string &  key 
)

True if any of the first events carries key.

Here is the call graph for this function:
Here is the caller graph for this function:

◆ ResolveActorFields()

std::vector< std::string > ui::qt::anonymous_namespace{DashboardPanel.cpp}::ResolveActorFields ( db::EventsContainer &  events)

Columns whose values are actor names: those of the best exchange pattern (source + destination, actor, ...), or the legacy "actor" field.

Here is the call graph for this function:
Here is the caller graph for this function:

◆ ResolveTypeField()

std::string ui::qt::anonymous_namespace{DashboardPanel.cpp}::ResolveTypeField ( db::EventsContainer &  events,
const std::string &  configured 
)

The configured type field when the log has it; otherwise the first common severity/kind column the log does have (e.g. "event_type" in safeAPI logs).

Here is the call graph for this function:
Here is the caller graph for this function:

Variable Documentation

◆ kFieldProbeEvents

constexpr size_t ui::qt::anonymous_namespace{DashboardPanel.cpp}::kFieldProbeEvents = 200
constexpr