diff --git a/nezha-fronted/src/assets/css/components/page/dashboard/explore/explore.scss b/nezha-fronted/src/assets/css/components/page/dashboard/explore/explore.scss index 2ed381ec0..3d0ef869d 100644 --- a/nezha-fronted/src/assets/css/components/page/dashboard/explore/explore.scss +++ b/nezha-fronted/src/assets/css/components/page/dashboard/explore/explore.scss @@ -256,7 +256,7 @@ } .doc-content > h1 { color: #e6522c; - font-size: 22px; + font-size: 24px; } .doc-content > h2 { @@ -357,6 +357,10 @@ article { padding: 5px; background-color: $--background-color-empty; } + .log-link:hover{ + cursor: pointer; + border-bottom: 1px solid #3C92F1; + } .fillbox{ display: block; line-height: 25px; @@ -369,7 +373,7 @@ article { } > h1,.page-header { color: #e6522c; - font-size: 22px; + font-size: 24px; font-weight: 600; text-transform: uppercase; margin-top: 15px; @@ -379,6 +383,13 @@ article { text-decoration: none; } } + > h1,.page-header-one { + color: #e6522c; + font-size: 22px; + font-weight: 600; + margin-top: 15px; + text-transform: none; + } > h1,.page-header-two { color: #e6522c; font-size: 20px; @@ -433,7 +444,11 @@ article { ul li{ margin: 3px 14px 3px 24px; list-style: circle; - color: #3C92F1 + color: #3C92F1; + } + span:hover{ + cursor: pointer; + border-bottom: 1px solid #3C92F1; } } } diff --git a/nezha-fronted/src/components/page/dashboard/explore/exploreItem.vue b/nezha-fronted/src/components/page/dashboard/explore/exploreItem.vue index a7fc327df..f8d57ebe1 100644 --- a/nezha-fronted/src/components/page/dashboard/explore/exploreItem.vue +++ b/nezha-fronted/src/components/page/dashboard/explore/exploreItem.vue @@ -289,17 +289,17 @@ instance_cpu_time_ns{app="fox", proc="widget", rev="4d3a513", env="prod", job="c

LogQL is Grafana Loki’s PromQL-inspired query language. Queries act as if they are a distributed grep to aggregate log sources. LogQL uses labels and operators for filtering.

There are two types of LogQL queries:

-

Log queries

+

Log queries

All LogQL queries contain a log stream selector.

-
+

Optionally, the log stream selector can be followed by a log pipeline. A log pipeline is a set of stage expressions that are chained together and applied to the selected log streams. Each expression can filter out, parse, or mutate log lines and their respective labels.

The following example shows a full log query in action:

{container="query-frontend",namespace="loki-dev"} |= "metrics.go" | logfmt | duration > 10s and throughput_mb < 500

@@ -345,9 +345,9 @@ instance_cpu_time_ns{app="fox", proc="widget", rev="4d3a513", env="prod", job="c

| line_format "{{.status_code}}"

Log pipeline expressions fall into one of three categories:

@@ -411,7 +411,7 @@ instance_cpu_time_ns{app="fox", proc="widget", rev="4d3a513", env="prod", job="c
  • Number are floating-point number (64bits), such as 250, 89.923.
  • Bytes is a sequence of decimal numbers, each with optional fraction and a unit suffix, such as “42MB”, “1.5Kib” or “20b”. Valid bytes units are “b”, “kib”, “kb”, “mib”, “mb”, “gib”, “gb”, “tib”, “tb”, “pib”, “pb”, “eib”, “eb”.
  • -

    String type work exactly like Prometheus label matchers use in log stream selector. This means you can use the same operations (=,!=,=~,!~).

    +

    String type work exactly like Prometheus label matchers use in log stream selector. This means you can use the same operations (=,!=,=~,!~).

    The string type is the only one that can filter out a log line with a label __error__.

    Using Duration, Number and Bytes will convert the label value prior to comparision and support the following comparators: