content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
just one of several ways to decode kernel stack traces. Sometimes different steps will be required to retrieve the relevant details. Don't worry about that, if that's needed in your case, developers will tell you what to do. Special care for regressions ---------------------------- \*If your problem is a regression, tr... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.030721794813871384,
-0.0450625978410244,
0.012352097779512405,
0.059845536947250366,
0.11612976342439651,
-0.06116969510912895,
-0.10477954149246216,
0.0663728415966034,
0.055400848388671875,
0.030337998643517494,
0.03754309192299843,
0.06630544364452362,
-0.08498185873031616,
-0.039042... | 0.091061 |
as explained in more detail by Documentation/admin-guide/reporting-regressions.rst; that document also provides a good deal of other information about regressions you might want to be aware of. Write and send the report ------------------------- \*Start to compile the report by writing a detailed description about the ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.016953879967331886,
-0.04813847690820694,
0.0180419459939003,
0.09160443395376205,
0.10426416993141174,
-0.05508032441139221,
-0.05183764174580574,
0.14152176678180695,
-0.011871885508298874,
-0.00922510214149952,
-0.0018124961061403155,
0.026325015351176262,
0.002214335836470127,
0.0220... | 0.11543 |
that you get from ``dmesg`` written to a file. Make sure that it starts with a line like 'Linux version 5.8-1 (foobar@example.com) (gcc (GCC) 10.2.1, GNU ld version 2.34) #1 SMP Mon Aug 3 14:54:37 UTC 2020' If it's missing, then important messages from the first boot phase already got discarded. In this case instead co... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.02048514038324356,
0.02047842927277088,
0.0068940939381718636,
0.04510010778903961,
0.09519603103399277,
-0.06709735840559006,
-0.020878290757536888,
0.08063608407974243,
-0.011056439951062202,
0.0308073740452528,
0.002907414687797427,
-0.01807083562016487,
0.02711358293890953,
0.007205... | -0.009355 |
example help others to identify what hardware you use. If you have a problem with hardware you even might want to make the output from ``sudo lspci -vvv`` available, as that provides insights how the components were configured. For some issues it might be good to include the contents of files like ``/proc/cpuinfo``, ``... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.005175215657800436,
-0.04620913788676262,
-0.08706231415271759,
-0.0398971252143383,
0.05993418022990227,
-0.001852977555245161,
-0.016120612621307373,
0.10669253766536713,
-0.07178232073783875,
-0.053542740643024445,
0.021629581227898598,
-0.04832141101360321,
-0.06922248005867004,
-0.... | 0.128538 |
the URL to the ticket. When mailing or forwarding the report, in case of a successful bisection add the author of the culprit to the recipients; also CC everyone in the signed-off-by chain, which you find at the end of its commit message. \*\*Security issues\*\*: for these issues your will have to evaluate if a short-t... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.02428005263209343,
0.10215935856103897,
-0.02520335465669632,
0.05400751531124115,
0.03639599680900574,
0.0258356761187315,
-0.010512235574424267,
0.0426032729446888,
-0.07710686326026917,
0.046449024230241776,
-0.025669431313872337,
-0.0857471451163292,
0.0747004896402359,
0.0040447916... | 0.044962 |
sure the public mailing list(s) and everyone else that gets involved over time stays in the loop; it also keeps the mail thread intact, which among others is really important for mailing lists to group all related mails together. There are just two situations where a comment in a bug tracker or a 'Reply-all' is unsuita... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.093910813331604,
-0.01865416206419468,
-0.0036460149567574263,
-0.00556678231805563,
0.10945194959640503,
-0.06438705325126648,
0.05843698978424072,
0.0424211360514164,
-0.07364780455827713,
-0.025958316400647163,
0.008328579366207123,
-0.001963262213394046,
-0.009186607785522938,
-0.06... | 0.044386 |
point participated in the discussion). This will show your commitment and that you are willing to help. It also tells developers if the issue persists and makes sure they do not forget about it. A few other occasional retests (for example with rc3, rc5 and the final) are also a good idea, but only report your results i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.06390172988176346,
0.06040402501821518,
-0.04271651804447174,
0.06588680297136307,
0.04650053754448891,
0.03746188059449196,
0.007241301238536835,
0.08157367259263992,
-0.054169248789548874,
-0.002494754269719124,
-0.08374735713005066,
-0.07339860498905182,
0.00738892937079072,
0.041682... | 0.034882 |
all the recipients will have the details at hand immediately in the proper order. After the reminder wait three more weeks for replies. If you still don't get a proper reaction, you first should reconsider your approach. Did you maybe try to reach out to the wrong people? Was the report maybe offensive or so confusing ... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.00027240239433012903,
-0.011030544526875019,
0.0063992575742304325,
0.03247823938727379,
0.10409606248140335,
-0.021773958578705788,
-0.03792906925082207,
0.10785644501447678,
-0.01873786933720112,
-0.013104477897286415,
0.017087001353502274,
-0.022151073440909386,
0.006973136682063341,
... | -0.002287 |
within a stable and longterm kernel line. Make sure the particular version line still gets support ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ \*Check if the kernel developers still maintain the Linux kernel version line you care about: go to the front page of kernel.org and make sure it mentions the lates... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.010226561687886715,
-0.07928161323070526,
0.029310481622815132,
-0.048761870712041855,
0.10303795337677002,
-0.07282264530658722,
-0.13833582401275635,
0.04398326203227043,
-0.040796585381031036,
-0.0606219507753849,
0.054283689707517624,
0.034552186727523804,
-0.09305174648761749,
-0.0... | 0.094278 |
from 5.10.4 to 5.10.5) a brief report is enough for the start to get the issue reported quickly. Hence a rough description to the stable and regressions mailing list is all it takes; but in case you suspect the cause in a particular subsystem, CC its maintainers and its mailing list as well, because that will speed thi... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.022751787677407265,
-0.08101804554462433,
0.10061953216791153,
0.04720577597618103,
0.16348302364349365,
-0.09909277409315109,
-0.08788104355335236,
0.010597854852676392,
-0.05732063949108124,
-0.003922943025827408,
0.043178968131542206,
0.04999423772096634,
-0.10320768505334854,
0.0013... | -0.036811 |
this guide. Those steps will let you: \* Check if the kernel developers still maintain the Linux kernel version line you care about. \* Search the Linux stable mailing list for exiting reports. \* Check with the latest release. Check code history and search for existing discussions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.002745953854173422,
-0.07826407253742218,
-0.013299275189638138,
0.026539966464042664,
0.08227149397134781,
-0.025492388755083084,
-0.11411775648593903,
0.01670963503420353,
-0.07590772956609726,
-0.01142767071723938,
0.06616419553756714,
0.05779262259602547,
-0.057287365198135376,
-0.0... | 0.056071 |
left: ask for advice. Do that in a mail you sent to the maintainers for the subsystem where the issue seems to have its roots; CC the mailing list for the subsystem as well as the stable mailing list (stable@vger.kernel.org). Why some issues won't get any reaction or remain unfixed after being reported ================... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.0578153170645237,
-0.038135748356580734,
-0.010897736065089703,
0.034705232828855515,
0.0884685143828392,
-0.07264363020658493,
-0.08599454909563065,
0.10821188241243362,
-0.05641227960586548,
0.0018469090573489666,
0.009756742976605892,
0.023772740736603737,
-0.05411200225353241,
-0.03... | 0.099555 |
if a driver is working nearly perfectly. To not get completely stuck, the programmer thus might have no other choice than to prioritize issue reports and reject some of them. But don't worry too much about all of this, a lot of drivers have active maintainers who are quite interested in fixing as many issues as possibl... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.04569244384765625,
0.10500282049179077,
0.018483484163880348,
0.05265612155199051,
0.09962427616119385,
-0.029119862243533134,
-0.022151201963424683,
0.11232823878526688,
-0.05115983635187149,
-0.03231498971581459,
0.042679041624069214,
0.05267937853932381,
-0.026387713849544525,
-0.092... | 0.191403 |
.. SPDX-License-Identifier: GPL-2.0 ====================== The SGI XFS Filesystem ====================== XFS is a high performance journaling filesystem which originated on the SGI IRIX platform. It is completely multi-threaded, can support large files and large filesystems, extended attributes, variable block sizes, i... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
-0.0005866177380084991,
-0.03675688058137894,
-0.04416633024811745,
-0.010245964862406254,
0.1053646132349968,
-0.1250295788049698,
0.00020925466378685087,
0.060980163514614105,
0.02651146799325943,
-0.06495991349220276,
-0.006072806194424629,
0.08933742344379425,
-0.001628537429496646,
0.... | 0.090801 |
as if ``nolargeio`` was specified. logbufs=value Set the number of in-memory log buffers. Valid numbers range from 2-8 inclusive. The default value is 8 buffers. If the memory cost of 8 log buffers is too high on small systems, then it may be reduced at some cost to performance on metadata intensive workloads. The ``lo... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
0.057587455958127975,
0.022329283878207207,
-0.06950841099023819,
-0.012627641670405865,
0.05993233248591423,
-0.10828736424446106,
-0.002989158034324646,
0.090424545109272,
0.033985644578933716,
0.06485777348279953,
-0.01860770210623741,
0.02829803340137005,
-0.04853559657931328,
0.035070... | 0.149748 |
disk quota accounting enabled and limits (optionally) enforced. Refer to \*\*xfs\_quota(8)\*\* for further details. sunit=value and swidth=value Used to specify the stripe unit and width for a RAID device or a stripe volume. "value" must be specified in 512-byte block units. These options are only relevant to filesyste... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
-0.020087506622076035,
0.005493018310517073,
-0.10199657082557678,
-0.035135067999362946,
0.0298702921718359,
-0.1100023090839386,
-0.0024040716234594584,
0.029041601344943047,
0.010402738116681576,
-0.04252505302429199,
0.030795341357588768,
0.015522295609116554,
0.04289187490940094,
0.03... | -0.005712 |
the free pool. fs.xfs.error\_level (Min: 0 Default: 3 Max: 11) A volume knob for error reporting when internal errors occur. This will generate detailed messages & backtraces for filesystem shutdowns, for example. Current threshold values are: XFS\_ERRLEVEL\_OFF: 0 XFS\_ERRLEVEL\_LOW: 1 XFS\_ERRLEVEL\_HIGH: 5 fs.xfs.pa... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
0.03383230045437813,
-0.005272701382637024,
-0.04481871798634529,
0.0037420245353132486,
0.15516729652881622,
-0.09653684496879578,
0.05420917272567749,
0.07491570711135864,
0.0407683439552784,
-0.01731799729168415,
0.021442914381623268,
-0.0419284887611866,
0.04254790022969246,
-0.0219722... | 0.068927 |
(e.g. during unmount). The configuration files are organized into the following hierarchy for each mounted filesystem: /sys/fs/xfs//error/// Where: The short device name of the mounted filesystem. This is the same device name that shows up in XFS kernel error messages as "XFS(): ..." The subsystem the error configurati... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
0.03085060603916645,
-0.025328321382403374,
0.03544272854924202,
0.018403377383947372,
0.13744287192821503,
-0.07770466059446335,
-0.04740167781710625,
0.08769895136356354,
-0.0021254324819892645,
-0.06862425059080124,
0.0833236426115036,
-0.01065014023333788,
0.05438448488712311,
0.009675... | 0.087879 |
fatal, unrecoverable error no matter how many times the metadata IO is retried. Workqueue Concurrency ===================== XFS uses kernel workqueues to parallelize metadata update processes. This enables it to take advantage of storage hardware that can service many IO operations simultaneously. This interface expose... | https://github.com/torvalds/linux/blob/master//Documentation/admin-guide/xfs.rst | master | linux | [
-0.03255489096045494,
-0.05032429099082947,
-0.060922008007764816,
-0.0009755401406437159,
0.018494226038455963,
-0.15545977652072906,
0.09192924946546555,
0.022496940568089485,
0.020601844415068626,
0.02520674467086792,
0.04576561227440834,
-0.018696540966629982,
0.05941743403673172,
-0.0... | 0.150198 |
# Send log data to Loki There are a number of different clients available to send log data to Loki. While all clients can be used simultaneously to cover multiple use cases, which client is initially picked to send logs depends on your use case. {{< youtube id="xtEppndO7F8" >}} ## Grafana Clients The following clients ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/_index.md | main | loki | [
-0.10421773791313171,
-0.00901786144822836,
-0.047943491488695145,
-0.015687301754951477,
-0.011655010282993317,
-0.11514159291982651,
0.04519868642091751,
0.07386258989572525,
0.0006115540163591504,
0.0189436636865139,
-0.03775201365351677,
-0.07781996577978134,
0.023560358211398125,
0.06... | 0.268982 |
# Docker driver client configuration The Docker daemon on each machine has a default logging driver and each container will use the default driver unless configured otherwise. ## Installation Before configuring the plugin, [install or upgrade the Grafana Loki Docker Driver Client](../) ## Change the logging driver for ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/configuration.md | main | loki | [
-0.013032960705459118,
0.023277344182133675,
-0.03453982621431351,
0.02873494289815426,
-0.012504272162914276,
-0.10702768713235855,
-0.015508651733398438,
-0.02693370170891285,
-0.0022056601010262966,
0.07699573040008545,
-0.018063858151435852,
-0.07810966670513153,
-0.010653818026185036,
... | 0.054032 |
is written to on disk - `host`: the hostname where the log has been generated - `swarm\_stack`, `swarm\_service`: added when deploying from Docker Swarm. - `compose\_project`, `compose\_service`: added when deploying with Docker Compose. Custom labels can be added using the `loki-external-labels`, `loki-pipeline-stages... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/configuration.md | main | loki | [
0.004055547062307596,
-0.026422888040542603,
-0.05891232565045357,
-0.00875264871865511,
-0.012859459035098553,
0.00579074677079916,
0.003999331500381231,
0.06431663036346436,
0.02008930779993534,
0.01073154341429472,
0.028573784977197647,
-0.09879161417484283,
0.0026045823469758034,
0.010... | 0.146291 |
| | `loki-min-backoff` | No | `500ms` | The minimum amount of time to wait before retrying a batch. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". | | `loki-max-backoff` | No | `5m` | The maximum amount of time to wait before retrying a batch. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/configuration.md | main | loki | [
-0.0006799419061280787,
-0.008219847455620766,
-0.030566276982426643,
0.008286644704639912,
-0.0575471967458725,
-0.05472155660390854,
-0.08875362575054169,
0.02043573185801506,
-0.013116966933012009,
0.00435055885463953,
0.001367126009427011,
-0.045670658349990845,
-0.019459862262010574,
... | 0.077827 |
Both options add additional fields to the labels of a logging message. | ### `no-file` and `keep-file` interactions The `no-file` and `keep-file` options control whether JSON log files are created and how long they are kept: | `no-file` | `keep-file` | JSON log file created? | Deleted on container stop? | `docker logs`... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/configuration.md | main | loki | [
-0.027257325127720833,
0.10025560110807419,
-0.026075467467308044,
0.0486011877655983,
0.08310835808515549,
-0.057189200073480606,
0.008779233321547508,
-0.035884108394384384,
0.10617908090353012,
0.015841256827116013,
0.06749837845563889,
-0.017900101840496063,
-0.024565421044826508,
0.05... | 0.101379 |
# Docker driver client Grafana Loki officially supports a Docker plugin that will read logs from Docker containers and ship them to Loki. The plugin can be configured to send the logs to a private Loki instance or Grafana Cloud. {{< admonition type="note" >}} Docker plugins are not supported on Windows; see the [Docker... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/_index.md | main | loki | [
-0.05736861750483513,
0.016150973737239838,
-0.039485570043325424,
0.02541278675198555,
-0.012700957246124744,
-0.0892040953040123,
-0.031855713576078415,
-0.02474757842719555,
-0.02657478302717209,
0.09294692426919937,
-0.02517211250960827,
-0.10226033627986908,
-0.048222046345472336,
0.0... | 0.059647 |
the main flow of an application or service due to logging issues, but it can also lead to loss of log messages if the buffer overflows or if Loki is unavailable for a long time. To avoid this issue, use the Alloy [`loki.source.docker`](https://grafana.com/docs/alloy/latest/reference/components/loki/loki.source.docker/)... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/docker-driver/_index.md | main | loki | [
-0.07625246793031693,
0.015527097508311272,
-0.029979756101965904,
0.027339445427060127,
-0.017143188044428825,
-0.11463715136051178,
-0.001798111479729414,
-0.01845511980354786,
-0.014901582151651382,
0.01980057917535305,
-0.05939558520913124,
-0.06598607450723648,
-0.015603364445269108,
... | 0.106819 |
# Fluentd client The [Fluentd output plugin](https://www.fluentd.org/) for Grafana Loki is called `fluent-plugin-grafana-loki` that enables shipping logs to a private Loki instance or [Grafana Cloud](/products/cloud/). The plugin source code is in the [fluentd directory of the repository](https://github.com/grafana/lok... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentd/_index.md | main | loki | [
-0.05632905289530754,
-0.036813147366046906,
-0.02798171527683735,
-0.02044832892715931,
0.0003237142809666693,
-0.027640895918011665,
-0.07163303345441818,
-0.020884329453110695,
-0.03445766493678093,
0.11787362396717072,
0.04014015197753906,
-0.06953989714384079,
-0.040611643344163895,
0... | 0.007081 |
loki by fluentd always have increasing times for their unique label sets. This plugin automatically adds a `fluentd\_thread` label with the name of the buffer flush thread when `flush\_thread\_count` > 1. ## Configuration ### `url` The URL of the Loki server to send logs to. When sending data, the publish path (`../ref... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentd/_index.md | main | loki | [
-0.091352678835392,
-0.07556065917015076,
-0.06373514235019684,
0.003502210834994912,
-0.05917807295918465,
-0.06757597625255585,
-0.030144156888127327,
-0.04484620317816734,
0.06996260583400726,
0.06129304692149162,
0.0448780357837677,
-0.026777222752571106,
0.005322977434843779,
0.039118... | 0.097918 |
of needless record keys to remove. All other keys will be placed into the log line. You can use [record\_accessor syntax](https://docs.fluentd.org/plugin-helper-overview/api-plugin-helper-record\_accessor#syntax). - line\_format (default:key\_value): format to use when flattening the record to a log line. Valid values ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentd/_index.md | main | loki | [
-0.03330650180578232,
0.03275289013981819,
0.04451709985733032,
0.02955402433872223,
-0.00047760846791788936,
-0.023555580526590347,
0.03783804923295975,
-0.013198097236454487,
0.02495288848876953,
0.048094239085912704,
0.0949082300066948,
-0.05319155007600784,
-0.0032447560224682093,
0.04... | 0.034214 |
# Ingesting logs to Loki using Alloy Grafana Alloy is a versatile observability collector that can ingest logs in various formats and send them to Loki. We recommend Alloy as the primary method for sending logs to Loki, as it provides a more robust and feature-rich solution for building a highly scalable and reliable o... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/_index.md | main | loki | [
-0.08402737230062485,
-0.02056233212351799,
-0.027387531474232674,
0.008062470704317093,
-0.02555607259273529,
-0.07844400405883789,
0.011903015896677971,
0.033606819808483124,
-0.07707011699676514,
0.04962065815925598,
-0.06187049299478531,
-0.08391569554805756,
-0.021640585735440254,
0.1... | 0.192169 |
# Sending Logs to Loki via Kafka using Alloy Alloy natively supports receiving logs via Kafka. In this example, we will configure Alloy to receive logs via Kafka using two different methods: - [loki.source.kafka](https://grafana.com/docs/alloy/latest/reference/components/loki.source.kafka): reads messages from Kafka us... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-kafka-logs.md | main | loki | [
-0.10085669904947281,
0.005657407455146313,
-0.04531986638903618,
0.03974751755595207,
-0.01856967993080616,
-0.07115516066551208,
0.014823240227997303,
0.004593674559146166,
0.019106514751911163,
0.045898403972387314,
-0.04762968420982361,
-0.11580590158700943,
-0.01953175850212574,
0.013... | 0.128099 |
an inbuilt Code editor which can be accessed via the `Editor` tab.\*\* 1. Expand the `loki-fundamentals` directory in the file explorer of the `Editor` tab. 1. Locate the `config.alloy` file in the `loki-fundamentals` directory (Top level directory). 1. Click on the `config.alloy` file to open it in the code editor. {{... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-kafka-logs.md | main | loki | [
-0.12090663611888885,
-0.06010137498378754,
-0.08473969250917435,
0.06558123975992203,
0.02074931189417839,
0.0026646358892321587,
-0.039116792380809784,
0.07561594992876053,
-0.0586305633187294,
-0.00960924569517374,
0.000038335663703037426,
-0.06912610679864883,
0.022201769053936005,
-0.... | 0.190354 |
following configuration to the `config.alloy` file: ```alloy loki.write "http" { endpoint { url = "http://loki:3100/loki/api/v1/push" } } ``` In this configuration: - `endpoint`: The endpoint to send the logs to. In this case, we are sending the logs to the Loki HTTP endpoint. For more information on the `loki.write` c... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-kafka-logs.md | main | loki | [
-0.10416106879711151,
-0.03234199807047844,
-0.05335230007767677,
0.04302757978439331,
-0.016721047461032867,
-0.06113283336162567,
-0.059818901121616364,
-0.020458510145545006,
-0.02655642107129097,
0.03762698918581009,
-0.012997424229979515,
-0.04946565255522728,
0.020606236532330513,
0.... | 0.115408 |
`config.alloy` file: ```alloy otelcol.exporter.otlphttp "default" { client { endpoint = "http://loki:3100/otlp" } } ``` In this configuration: - `client`: The client configuration for the exporter. In this case, we are sending the logs to the Loki OTLP endpoint. For more information on the `otelcol.exporter.otlphttp` c... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-kafka-logs.md | main | loki | [
-0.1258571892976761,
-0.004523085430264473,
-0.048456043004989624,
0.04805896803736687,
-0.04368022829294205,
-0.062311798334121704,
-0.027133768424391747,
-0.0123303746804595,
-0.011270309798419476,
-0.02774013765156269,
-0.0075295912101864815,
-0.07548738270998001,
0.013225533068180084,
... | 0.128531 |
# Sending OpenTelemetry logs to Loki using Alloy Alloy natively supports receiving logs in the OpenTelemetry format. This allows you to send logs from applications instrumented with OpenTelemetry to Alloy, which can then be sent to Loki for storage and visualization in Grafana. In this example, we will make use of 3 Al... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-otel-logs.md | main | loki | [
-0.06973132491111755,
0.010467231273651123,
-0.029515011236071587,
0.013393930159509182,
-0.042668845504522324,
-0.13525988161563873,
-0.00040182654629461467,
0.03638532757759094,
-0.0469781756401062,
0.037540730088949203,
-0.00260735722258687,
-0.09378354996442795,
0.002169906161725521,
0... | 0.222126 |
file to define the components and their relationships. The configuration file is written using Alloy configuration syntax. We will build the entire observability pipeline within this configuration file. To start, we will open the `config.alloy` file in the code editor: {{< docs/ignore >}} \*\*Note: Killercoda has an in... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-otel-logs.md | main | loki | [
-0.07641668617725372,
-0.04459284618496895,
-0.09831683337688446,
0.0167433712631464,
-0.008310346864163876,
-0.016220608726143837,
-0.028895298019051552,
0.11566410213708878,
-0.13025367259979248,
-0.055423736572265625,
-0.0018467530608177185,
-0.04508718103170395,
0.05414959043264389,
0.... | 0.167368 |
configuration, you can copy and replace the entire `config.alloy` using the completed configuration file: ```bash cp loki-fundamentals/completed/config.alloy loki-fundamentals/config.alloy curl -X POST http://localhost:12345/-/reload ``` ## Step 3: Start the Carnivorous Greenhouse In this step, we will start the Carniv... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/alloy/examples/alloy-otel-logs.md | main | loki | [
-0.015292475000023842,
0.03778793290257454,
-0.0049467068165540695,
-0.007027763873338699,
0.020217683166265488,
-0.00018969755910802633,
-0.059163954108953476,
0.03796227276325226,
-0.05139940604567528,
-0.005529642570763826,
-0.03135319799184799,
-0.14359760284423828,
0.04441673681139946,
... | 0.022736 |
# Logstash plugin Grafana Loki has a [Logstash](https://www.elastic.co/logstash) output plugin called `logstash-output-loki` that enables shipping logs to a Loki instance or [Grafana Cloud](/products/cloud/). {{< admonition type="warning" >}} Grafana Labs does not recommend using the Logstash plugin for new deployments... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/logstash/_index.md | main | loki | [
-0.057594336569309235,
-0.03866274654865265,
-0.04117739573121071,
0.03309572488069534,
-0.008510634303092957,
-0.056548722088336945,
-0.04793202504515648,
-0.039764657616615295,
-0.006118896417319775,
0.07573165744543076,
-0.0010464339284226298,
-0.06924420595169067,
-0.022930527105927467,
... | 0.194362 |
300(s) | required=false] [retries => number | default = 10 | required=false] [username => string | default = nil | required=false] [password => secret | default = nil | required=false] [cert => path | default = nil | required=false] [key => path | default = nil| required=false] [ca\_cert => path | default = nil | requi... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/logstash/_index.md | main | loki | [
0.017737003043293953,
0.025028686970472336,
-0.037009816616773605,
-0.003150754841044545,
0.005495807155966759,
-0.08071902394294739,
0.03348071500658989,
-0.023038329556584358,
0.07961878180503845,
0.08419390767812729,
-0.05339682102203369,
-0.10168412327766418,
0.03968377783894539,
0.082... | 0.158171 |
Loki](/products/cloud/), the username needs to be set to your instance/user id and the password should be a Grafana.com api key. #### message\_field Message field to use for log lines. You can use logstash key accessor language to grab nested property, for example : `[log][message]`. #### include\_fields An array of fi... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/logstash/_index.md | main | loki | [
-0.046478934586048126,
0.018346650525927544,
-0.07025952637195587,
-0.00397426076233387,
-0.07264535129070282,
-0.07886888831853867,
0.021245773881673813,
0.0134733896702528,
0.024939412251114845,
0.06883315742015839,
-0.007298133801668882,
-0.06922797858715057,
0.04147673770785332,
0.0302... | 0.126082 |
# Kubernetes Monitoring Helm tutorial One of the primary use cases for Loki is to collect and store logs from your [Kubernetes cluster](https://kubernetes.io/docs/concepts/overview/). These logs fall into three categories: 1. [\*\*Pod logs\*\*](https://kubernetes.io/docs/concepts/cluster-administration/logging/#basic-l... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k8s-monitoring-helm/_index.md | main | loki | [
0.05890849977731705,
0.013241015374660492,
0.040697406977415085,
0.030141081660985947,
0.10059337317943573,
-0.02239593304693699,
0.0037136212922632694,
-0.031249582767486572,
0.10235854983329773,
0.07956696301698685,
-0.02145206369459629,
-0.07815144956111908,
-0.02128414995968342,
0.0151... | 0.216276 |
tutorial repository by running the following command: ```bash git clone https://github.com/grafana/alloy-scenarios.git ``` Then change directories to the `alloy-scenarios/k8s/logs` directory: ```bash cd alloy-scenarios/k8s/logs ``` \*\*The rest of this tutorial assumes you are in the `alloy-scenarios/k8s/logs` director... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k8s-monitoring-helm/_index.md | main | loki | [
-0.03840184584259987,
0.05252823233604431,
0.02371821366250515,
0.021099772304296494,
-0.008452899754047394,
-0.0352509431540966,
-0.03566235676407814,
0.06493651866912842,
0.012715484946966171,
0.08267446607351303,
-0.038176801055669785,
-0.07544093579053879,
0.02948898822069168,
0.045472... | 0.182991 |
and Kubernetes events. To deploy the Kubernetes Monitoring Helm chart run the following command: ```bash helm install --values ./k8s-monitoring-values.yml k8s grafana/k8s-monitoring -n meta ``` Within the configuration file `k8s-monitoring-values.yml` we have defined the following: ```yaml --- cluster: name: meta-monit... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k8s-monitoring-helm/_index.md | main | loki | [
0.05113804712891579,
-0.00984819233417511,
0.02501312643289566,
0.02620837278664112,
0.050003018230199814,
0.0032109252642840147,
-0.009642536751925945,
-0.01289425976574421,
0.08582473546266556,
0.06818436831235886,
-0.01375880278646946,
-0.09817808121442795,
-0.0281213391572237,
-0.01156... | 0.179723 |
queries: [http://localhost:3000/a/grafana-lokiexplore-app](http://localhost:3000/a/grafana-lokiexplore-app) {{< figure max-width="100%" src="/media/docs/loki/k8s-logs-explore-logs.png" caption="Logs Drilldown view of K8s logs" alt="Logs Drilldown view of K8s logs" >}} ## (Optional) View the Alloy UI The Kubernetes Moni... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k8s-monitoring-helm/_index.md | main | loki | [
-0.07613413035869598,
0.025106841698288918,
0.001626663375645876,
-0.002177436137571931,
-0.055091965943574905,
-0.05924797058105469,
-0.052663348615169525,
0.05389225855469704,
0.00043204176472499967,
0.045054033398628235,
-0.032909855246543884,
-0.10890351235866547,
-0.011662651784718037,
... | 0.238443 |
# Promtail agent {{< admonition type="warning" >}} Promtail is end of life (EOL) as of March 2, 2026. Commercial support has ended. No future support or updates will be provided. All future feature development will occur in Grafana Alloy. Note that the deprecation of Promtail does NOT include the lambda-promtail client... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/promtail/_index.md | main | loki | [
-0.11365900188684464,
0.018516909331083298,
-0.06815194338560104,
0.003841967787593603,
-0.0320192314684391,
-0.02323245443403721,
0.0009064913610927761,
0.002263445872813463,
-0.0939008891582489,
-0.0049406918697059155,
-0.03924466297030449,
-0.09043750911951065,
0.014758679084479809,
0.0... | 0.097929 |
# Getting started with the OpenTelemetry Collector and Loki tutorial The OpenTelemetry Collector offers a vendor-agnostic implementation of how to receive, process, and export telemetry data. With the introduction of the OTLP endpoint in Loki, you can now send logs from applications instrumented with OpenTelemetry to L... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/otel-collector-getting-started.md | main | loki | [
-0.00026220179279334843,
0.01809767819941044,
-0.0293781328946352,
0.0033840015530586243,
-0.02345549874007702,
-0.1383531093597412,
-0.020951246842741966,
0.05379611626267433,
-0.028028754517436028,
0.024985279887914658,
0.00986152421683073,
-0.08227585256099701,
-0.035781145095825195,
-0... | 0.204645 |
After we've finished configuring the OpenTelemetry Collector and sending logs to Loki, we will be able to view the logs in Grafana. To check if Grafana is up and running, navigate to the following URL: [http://localhost:3000](http://localhost:3000) ## Step 2: Configuring the OpenTelemetry Collector To configure the Col... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/otel-collector-getting-started.md | main | loki | [
-0.08878238499164581,
-0.005057367961853743,
-0.07607241719961166,
-0.007019441109150648,
-0.06223724037408829,
-0.11232160031795502,
-0.09761861711740494,
-0.010279138572514057,
-0.03669562563300133,
0.04851311817765236,
0.020914174616336823,
-0.10271628946065903,
-0.026604121550917625,
0... | 0.140619 |
are using the `otlphttp/logs` exporter. - `otlphttp/logs`: The OpenTelemetry exporter that accepts telemetry data from other `otelcol` components and writes them over the network using the OTLP HTTP protocol. - `endpoint`: The URL to send the telemetry data to. In this case, we are sending the logs to the Loki native O... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/otel-collector-getting-started.md | main | loki | [
-0.010293824598193169,
0.044378336519002914,
0.013784802518785,
0.009233563207089901,
-0.01215474121272564,
-0.1937282234430313,
-0.025558147579431534,
-0.031293340027332306,
0.09682338684797287,
0.00784275121986866,
0.032798752188682556,
-0.024089094251394272,
-0.015211453661322594,
0.052... | 0.043871 |
Container greenhouse-db-1 Started ✔ Container greenhouse-websocket\_service-1 Started ✔ Container greenhouse-bug\_service-1 Started ✔ Container greenhouse-user\_service-1 Started ✔ Container greenhouse-plant\_service-1 Started ✔ Container greenhouse-simulation\_service-1 Started ✔ Container greenhouse-main\_app-1 Start... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/otel-collector-getting-started.md | main | loki | [
-0.047896891832351685,
0.006358725018799305,
-0.04753802716732025,
-0.01260625571012497,
0.03185378387570381,
-0.08064024895429611,
-0.05035712197422981,
-0.016918106004595757,
-0.013783427886664867,
0.05817301943898201,
0.023640206083655357,
-0.11555883288383484,
-0.011553006246685982,
0.... | 0.099516 |
# How is native OTLP endpoint different from Loki Exporter ## Introduction OpenTelemetry (OTel) is quickly becoming an industry standard with increasing adoption. Prior to the Loki 3.0 release, there was no native support for ingesting OTel logs to Loki, which led to creation of the [LokiExporter](https://github.com/op... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/native_otlp_vs_loki_exporter.md | main | loki | [
-0.029793718829751015,
-0.04197217524051666,
0.03209668770432472,
0.00962527934461832,
0.015411106869578362,
-0.12551923096179962,
-0.012285812757909298,
0.018445463851094246,
0.01604444719851017,
0.019490452483296394,
0.004496397450566292,
-0.05938292667269707,
-0.04087909311056137,
0.036... | 0.190594 |
Ingested with LokiExporter: `{job="dev/auth"} | json | line\_format "{{.body}}"` - Ingested with Loki’s native OTel endpoint: `{service\_name="auth", service\_namespace="dev"}` \*\*Count login events in the last hour by email\*\* - Ingested with LokiExporter: `sum(count\_over\_time({job="dev/auth"} |= "user logged in" ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/native_otlp_vs_loki_exporter.md | main | loki | [
-0.030486444011330605,
-0.016000250354409218,
0.054481443017721176,
0.001008185325190425,
0.0145594272762537,
-0.07907404005527496,
0.1239057332277298,
0.004026385489851236,
0.06502728164196014,
0.006436586380004883,
0.004083429928869009,
-0.06337793171405792,
0.033501286059617996,
0.08961... | 0.174766 |
[//]: # 'Shared content for configuring the OTEL collector to import logs to Loki' [//]: # 'This content is located in /loki/docs/sources/shared/otel.md' # Ingesting logs to Loki using OpenTelemetry Collector {{< docs/shared source="loki" lookup="otel.md" version="">}} Here are some example configs to change the defaul... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/otel/_index.md | main | loki | [
-0.019275158643722534,
0.0032821872737258673,
-0.03790324181318283,
0.023824740201234818,
0.01818980649113655,
-0.07270898669958115,
0.017871271818876266,
-0.030638068914413452,
0.011982631869614124,
0.02242143265902996,
0.05171990767121315,
-0.0767047107219696,
0.02551225945353508,
0.0406... | 0.147101 |
# Fluent Bit community plugin {{< admonition type="warning" >}} We recommend using the official [Fluent Bit Loki plugin](https://grafana.com/docs/loki//send-data/fluentbit/fluent-bit-plugin/). The official plugin is more feature-rich and has better support for features such as structured metadata. The community plugin ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/community-plugin.md | main | loki | [
-0.028636524453759193,
-0.04222426190972328,
-0.04289233312010765,
-0.005119255743920803,
0.02579418569803238,
-0.0845501646399498,
-0.041196852922439575,
-0.013409595005214214,
-0.05306599289178848,
0.08994264155626297,
0.02271926961839199,
-0.09732776880264282,
-0.03560268506407738,
0.11... | 0.134591 |
### Local First, you need to follow the [instructions](https://github.com/grafana/loki/blob/main/clients/cmd/fluent-bit/README.md) in order to build the plugin dynamic library. Assuming you have Fluent Bit installed in your `$PATH` you can run the plugin using: ```bash fluent-bit -e /path/to/built/out\_grafana\_loki.so... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/community-plugin.md | main | loki | [
-0.027982493862509727,
-0.04929185286164284,
-0.06079842895269394,
0.0035751916002482176,
-0.08145978301763535,
-0.01210513710975647,
-0.044710081070661545,
0.039176516234874725,
-0.05523216724395752,
0.047392625361680984,
0.010198410600423813,
-0.10669233649969101,
-0.059686727821826935,
... | -0.009957 |
indexed, so you should be cautious when choosing them. High cardinality label values can have drastic impact on query performance. You can use the config parameters `Labels`, `RemoveKeys` , `LabelKeys` and `LabelMapPath` to instruct the output plugin how to perform labels extraction from your log entries or to add stat... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/community-plugin.md | main | loki | [
0.01813778653740883,
0.006512683350592852,
-0.02294183149933815,
0.007566027343273163,
-0.02549610286951065,
0.033566318452358246,
0.0610249787569046,
0.024899719282984734,
0.042669862508773804,
-0.03759574890136719,
0.0034509694669395685,
-0.07672210782766342,
-0.010121697559952736,
0.014... | 0.115914 |
the same fluent-bit process, for example if you want to push to different Loki servers or route logs into different Loki tenant IDs. To do so, add additional `[Output]` sections. | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/community-plugin.md | main | loki | [
0.06217145919799805,
-0.07117561250925064,
-0.031533803790807724,
-0.011574024334549904,
0.0015884849708527327,
-0.07861511409282684,
-0.07695431262254715,
-0.033233948051929474,
-0.020348962396383286,
0.004844042006880045,
0.04393275827169418,
-0.06096688285470009,
-0.021777058020234108,
... | 0.082141 |
# Sending logs to Loki using Fluent Bit tutorial In this tutorial, you will learn how to send logs to Loki using Fluent Bit. Fluent Bit is a lightweight and fast log processor and forwarder that can collect, process, and deliver logs to various destinations. We will use the official Fluent Bit Loki output plugin to sen... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/fluent-bit-loki-tutorial.md | main | loki | [
0.04574546590447426,
-0.023993201553821564,
0.03353103622794151,
-0.012294878251850605,
0.03372484818100929,
-0.12162390351295471,
-0.026930682361125946,
0.020147955045104027,
-0.024201424792408943,
0.10906434804201126,
-0.0016392202815040946,
-0.13004329800605774,
-0.03660052269697189,
0.... | 0.103341 |
tab. 1. Locate the `fluent-bit.conf` file in the top level directory, `loki-fundamentals`. 1. Click on the `fluent-bit.conf` file to open it in the code editor. {{< /docs/ignore >}} 1. Open the `loki-fundamentals` directory in a code editor of your choice. 1. Locate the `fluent-bit.conf` file in the `loki-fundamentals`... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/fluent-bit-loki-tutorial.md | main | loki | [
0.028193539008498192,
-0.009480648674070835,
-0.025819042697548866,
-0.028648972511291504,
0.03241364285349846,
-0.08044881373643875,
-0.032244980335235596,
0.012152819894254208,
-0.06886550784111023,
0.07203905284404755,
0.04346314072608948,
-0.10978644341230392,
-0.03697296231985092,
0.0... | 0.114505 |
or need help creating the configuration, you can copy and replace the entire `config.alloy` using the completed configuration file: ```bash cp loki-fundamentals/completed/fluent-bit.conf loki-fundamentals/fluent-bit.conf docker restart loki-fundamentals-fluent-bit-1 ``` ## Step 3: Start the Carnivorous Greenhouse In th... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/fluent-bit-loki-tutorial.md | main | loki | [
0.015008662827312946,
0.027541054412722588,
0.009360411204397678,
-0.015128702856600285,
0.02002350240945816,
-0.03196057304739952,
-0.05172005668282509,
0.029654372483491898,
-0.06504899263381958,
0.015682896599173546,
-0.016251888126134872,
-0.16687697172164917,
0.02480238303542137,
0.06... | 0.026989 |
# Fluent Bit Loki output plugin [Fluent Bit](https://fluentbit.io/) is a fast and lightweight logs and metrics processor and forwarder that can be configured with the [Fluent-bit Loki output plugin](https://docs.fluentbit.io/manual/pipeline/outputs/loki) to ship logs to Loki. You can define which log files you want to ... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/fluent-bit-plugin.md | main | loki | [
-0.0022797761484980583,
-0.00852760300040245,
0.0007728804484941065,
-0.008392204530537128,
-0.040752243250608444,
-0.061554666608572006,
-0.007665060926228762,
0.028387578204274178,
-0.03571716323494911,
0.032928552478551865,
-0.01565379649400711,
-0.12706972658634186,
-0.0688411295413971,
... | 0.138577 |
Helm chart provided by the Fluent Bit project. The Helm chart is available at [https://github.com/fluent/helm-charts](https://github.com/fluent/helm-charts). Here is an example of how to deploy the Fluent Bit Helm chart to collect logs from Kubernetes and send them to Loki: 1. Add the Fluent Bit Helm repository: ```bas... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/fluent-bit-plugin.md | main | loki | [
0.06065678596496582,
0.037765949964523315,
0.021287627518177032,
-0.06551308929920197,
0.02784411422908306,
-0.048573438078165054,
-0.051636096090078354,
-0.01762252487242222,
0.05631433054804802,
0.07447405159473419,
0.02622007019817829,
-0.1140962690114975,
0.025680068880319595,
0.052421... | 0.03353 |
# Fluent Bit [Fluent Bit](https://fluentbit.io/) is a fast, lightweight logs and metrics agent. It is a CNCF graduated sub-project under the umbrella of Fluentd. Fluent Bit is licensed under the terms of the Apache License v2.0. When using Fluent Bit to ship logs to Loki, you can define which log files you want to coll... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/fluentbit/_index.md | main | loki | [
0.006855115294456482,
-0.02959357388317585,
-0.0215230043977499,
-0.0289128590375185,
-0.03682830557227135,
-0.08774818480014801,
-0.014418810606002808,
-0.0021446922328323126,
-0.04176643118262291,
0.051594506949186325,
-0.030170293524861336,
-0.12432453036308289,
-0.031261805444955826,
0... | 0.163248 |
# Use k6 to load test the write path There are multiple considerations when load testing a Loki cluster's write path. The most important consideration is the setup of the target cluster. Keep these items in mind when setting up your load test for the target cluster. - Deployment mode. The cluster might be deployed as a... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/write-scenario.md | main | loki | [
0.0067770523019135,
-0.04898126423358917,
-0.01925470493733883,
0.04941483214497566,
-0.0215530376881361,
-0.07700886577367783,
-0.05960690602660179,
0.04444633796811104,
-0.014706598594784737,
0.03697975352406502,
-0.04574736952781677,
-0.019464097917079926,
-0.00902491807937622,
-0.01659... | 0.221756 |
If tenant is omitted, xk6-loki runs in multi-tenant mode, \* and every VU will use its own ID. \* @constant {string} \*/ const TENANT\_ID = "my\_org\_id" /\*\* \* URL used for push and query requests \* Path is automatically appended by the client \* @constant {string} \*/ const BASE\_URL = `${TENANT\_ID}@${HOST}`; /\*... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/write-scenario.md | main | loki | [
0.017734596505761147,
0.07415212690830231,
-0.05074826627969742,
0.04106559976935387,
-0.02358301356434822,
-0.05292278528213501,
-0.0628897100687027,
0.024032963439822197,
0.03446311503648758,
-0.03556519001722336,
0.027319762855768204,
-0.05715810880064964,
-0.03230038657784462,
0.033982... | 0.047147 |
# Use k6 to load test log queries When designing a test scenario for load testing the read path of a Loki installation, it is important to know what types of queries you expect. ## Supported query types Loki has 5 types of queries: \* instant query \* range query \* labels query \* label values query \* series query In... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/query-scenario.md | main | loki | [
-0.08083666861057281,
-0.007696899119764566,
-0.08202241361141205,
0.04065655916929245,
-0.06381531804800034,
-0.06624191999435425,
-0.05791459605097771,
0.008435256779193878,
0.011935519054532051,
-0.020452402532100677,
0.011083274148404598,
-0.06177255138754845,
-0.03925785422325134,
-0.... | 0.155784 |
}, ]; ``` This configuration would execute approximately - 10% labels requests - 15% label values requests - 5% requests for series - 50% range queries - 20% instant queries during a test run. | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/query-scenario.md | main | loki | [
-0.0187118761241436,
0.023375844582915306,
-0.14337696135044098,
0.007888241671025753,
-0.10229910165071487,
-0.029205212369561195,
0.0565439835190773,
0.03973310440778732,
-0.03190022334456444,
-0.04110896959900856,
0.0489315465092659,
-0.00708402507007122,
0.024312051013112068,
-0.061867... | 0.17451 |
# Using k6 for load testing Grafana [k6](https://grafana.com/oss/k6/) is a modern load-testing tool. Its clean and approachable scripting [API](https://grafana.com/docs/k6/latest/javascript-api/) works locally or in the cloud. Its configuration makes it flexible. The [xk6-loki extension](https://github.com/grafana/xk6-... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/_index.md | main | loki | [
-0.08186331391334534,
0.02033541351556778,
-0.02607819065451622,
-0.013839848339557648,
-0.06103597953915596,
-0.09339461475610733,
-0.06487502157688141,
0.008855783380568027,
-0.03865129128098488,
0.017345743253827095,
-0.0021799542009830475,
-0.03748501464724541,
-0.05030450224876404,
0.... | 0.188478 |
# Generating log data for testing You can use k6 to generate log data for load testing. ## Using `pushParameterized` Push logs to Loki with `pushParameterized`. This method generates batches of streams in a random fashion. This method requires three arguments: | name | description | | ---- | ----------- | | `streams` |... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/log-generation.md | main | loki | [
-0.024349160492420197,
-0.010318044573068619,
0.0020915274508297443,
0.017895644530653954,
-0.05114474147558212,
-0.09186354279518127,
-0.008659235201776028,
0.06717008352279663,
-0.011260266415774822,
-0.011084375903010368,
-0.019619155675172806,
-0.06643198430538177,
-0.006030288990586996,... | 0.109029 |
and Protobuf. While JSON is easier for humans to read, Protobuf is optimized for performance and should be preferred when possible. To define the ratio of Protobuf to JSON requests, the client configuration accepts values of 0.0 to 1.0. 0.0 means 100% JSON encoding, and 1.0 means 100% Protobuf encoding. The default val... | https://github.com/grafana/loki/blob/main//docs/sources/send-data/k6/log-generation.md | main | loki | [
-0.02601989544928074,
0.002906678942963481,
-0.031092051416635513,
-0.04068535566329956,
-0.0483119823038578,
-0.09136171638965607,
-0.08902206271886826,
0.08955240994691849,
-0.00850206520408392,
-0.01688213460147381,
-0.016061920672655106,
-0.038748640567064285,
-0.06101429834961891,
0.0... | 0.079327 |
# Storage Unlike other logging systems, Grafana Loki is built around the idea of only indexing metadata about your logs: labels (just like Prometheus labels). Log data itself is then compressed and stored in chunks in object stores such as S3 or GCS, or even locally on the filesystem. A small index and highly compresse... | https://github.com/grafana/loki/blob/main//docs/sources/configure/storage.md | main | loki | [
-0.06835612654685974,
-0.024583779275417328,
-0.07829722762107849,
0.07097979635000229,
-0.032130368053913116,
-0.061057787388563156,
-0.014225922524929047,
0.021284306421875954,
0.019518675282597542,
0.0749858096241951,
-0.024861175566911697,
0.022758372128009796,
-0.006878056563436985,
0... | 0.200384 |
IBM Cloud hosted object store. It is a good candidate for a managed object store, especially when you're already running on IBM Cloud, and is production safe. #### Baidu Object Storage (BOS) [BOS](https://intl.cloud.baidu.com/product/bos.html) is the Baidu Cloud hosted object storage. #### Alibaba Object Storage Servic... | https://github.com/grafana/loki/blob/main//docs/sources/configure/storage.md | main | loki | [
-0.056674741208553314,
-0.019397731870412827,
-0.049120187759399414,
0.026228170841932297,
0.009637271985411644,
-0.016434475779533386,
-0.08779774606227875,
0.032169073820114136,
0.02072967402637005,
0.0728958249092102,
-0.00453903479501605,
0.02046883851289749,
0.043737608939409256,
0.00... | 0.179059 |
to the more effective TSDB with the v13 schema. This dramatically simplifies upgrading, ensuring it's simple to take advantage of new storage optimizations. These configs should be immutable for as long as you care about retention. ## Table Manager (deprecated) One of the subcomponents in Loki is the `table-manager`. I... | https://github.com/grafana/loki/blob/main//docs/sources/configure/storage.md | main | loki | [
-0.049732938408851624,
-0.036172036081552505,
-0.022021835669875145,
0.044196635484695435,
0.03567923605442047,
-0.01663249544799328,
-0.036362141370773315,
-0.005948862060904503,
-0.013479629531502724,
0.0565202496945858,
0.03210725262761116,
0.029580675065517426,
0.025780223309993744,
-0... | 0.116658 |
must be handled operationally outside of Loki. Loki also supports targeted deletion at the tenant or stream level. For more information, see the [retention configuration](https://grafana.com/docs/loki//operations/storage/retention/) documentation. ## Examples ### Single machine/local development (tsdb+filesystem) [The ... | https://github.com/grafana/loki/blob/main//docs/sources/configure/storage.md | main | loki | [
-0.053982242941856384,
-0.06308846920728683,
-0.03299172967672348,
-0.010228648781776428,
-0.029597816988825798,
-0.046957217156887054,
0.011712477542459965,
-0.028742920607328415,
0.025401702150702477,
0.0892830640077591,
0.03750867396593094,
0.006243328098207712,
0.021127628162503242,
0.... | 0.077663 |
to authenticate via a SAS token. Or if you use the Azurite emulator. connection\_string: tsdb\_shipper: active\_index\_directory: /loki/index cache\_location: /loki/index\_cache cache\_ttl: 24h filesystem: directory: /loki/chunks ``` #### Using a service principal ```yaml schema\_config: configs: - from: "2020-12-11" i... | https://github.com/grafana/loki/blob/main//docs/sources/configure/storage.md | main | loki | [
-0.01800878532230854,
-0.013988960534334183,
-0.09454677253961563,
0.0332041010260582,
-0.03078405186533928,
0.022418241947889328,
0.08802428096532822,
0.04874983802437782,
0.06369709968566895,
0.12503734230995178,
-0.007193078752607107,
-0.007125972770154476,
0.1072455644607544,
0.0484063... | 0.066554 |
# Configuration best practices Grafana Loki is under active development, and the Loki team is constantly working to improve performance. But here are some of the most current best practices for configuration that will give you the best experience with Loki. ## Configure authentication Grafana Loki does not come with an... | https://github.com/grafana/loki/blob/main//docs/sources/configure/bp-configure.md | main | loki | [
-0.07628963142633438,
-0.0077901738695800304,
-0.03008926287293434,
-0.01300061121582985,
-0.08127514272928238,
-0.09983738511800766,
-0.05678286775946617,
0.0012430544011294842,
-0.006262718699872494,
0.056910306215286255,
-0.023139623925089836,
0.046121902763843536,
-0.009428855031728745,
... | 0.093792 |
responses. `LZ4` is a good compromise of speed and compression performance. While compression is slightly slower than `snappy`, the compression ratio is higher, resulting in smaller chunks in object storage. ## Use `chunk\_target\_size` Using `chunk\_target\_size` instructs Loki to try to fill all chunks to a target \_... | https://github.com/grafana/loki/blob/main//docs/sources/configure/bp-configure.md | main | loki | [
0.0026994463987648487,
0.014141312800347805,
0.010641537606716156,
-0.00902694184333086,
0.08813122659921646,
-0.09898576140403748,
-0.05766978859901428,
0.08023624867200851,
-0.0016954480670392513,
0.04816574975848198,
-0.06929025799036026,
0.04442980885505676,
-0.051231272518634796,
0.05... | 0.068687 |
# Query frontend example ## Disclaimer This aims to be a general purpose example; there are a number of substitutions to make for it to work correctly. These variables take the form of . You should override them with specifics to your environment. ## Use case It's a common occurrence to start running Grafana Loki as a ... | https://github.com/grafana/loki/blob/main//docs/sources/configure/examples/query-frontend.md | main | loki | [
-0.031186018139123917,
-0.03776009380817413,
-0.03862815722823143,
0.04332806542515755,
-0.08235836774110794,
-0.0919254869222641,
-0.04282142221927643,
0.04829123616218567,
-0.06317034363746643,
0.04216257110238075,
-0.071503646671772,
-0.027104908600449562,
0.004549146629869938,
-0.07540... | 0.067397 |
The query frontend operates in one of two ways: - Specify `--frontend.downstream-url` or its YAML equivalent, `frontend.downstream\_url`. This proxies requests over HTTP to the specified URL. - Without `--frontend.downstream-url` or its yaml equivalent `frontend.downstream\_url`, the query frontend defaults to a pull s... | https://github.com/grafana/loki/blob/main//docs/sources/configure/examples/query-frontend.md | main | loki | [
-0.04826371744275093,
-0.07444291561841965,
0.021972132846713066,
-0.007821082137525082,
-0.10557518154382706,
-0.031092161312699318,
0.023012356832623482,
-0.056143615394830704,
0.05025710165500641,
0.041563358157873154,
-0.034724414348602295,
0.02888997457921505,
-0.031117236241698265,
-... | 0.021715 |
# Configuration ## 1-Local-Configuration-Example.yaml ```yaml # This is a complete configuration to deploy Loki backed by the filesystem. # The index will be shipped to the storage via tsdb-shipper. auth\_enabled: false server: http\_listen\_port: 3100 common: ring: instance\_addr: 127.0.0.1 kvstore: store: inmemory re... | https://github.com/grafana/loki/blob/main//docs/sources/configure/examples/configuration-examples.md | main | loki | [
0.00016841877368278801,
-0.06914880871772766,
-0.04734897240996361,
0.008026840165257454,
0.034763459116220474,
0.011868307366967201,
-0.05566151440143585,
0.03901546075940132,
-0.023873839527368546,
0.0614139586687088,
0.038078323006629944,
-0.01047493889927864,
0.03269428387284279,
0.037... | 0.149041 |
s3.endpoint.com region: s3\_region access\_key\_id: s3\_access\_key\_id secret\_access\_key: s3\_secret\_access\_key insecure: false http\_config: idle\_conn\_timeout: 90s response\_header\_timeout: 0s insecure\_skip\_verify: false s3forcepathstyle: true ``` ## 11-COS-HMAC-Example.yaml ```yaml # This partial configurat... | https://github.com/grafana/loki/blob/main//docs/sources/configure/examples/configuration-examples.md | main | loki | [
-0.07351113855838776,
0.013018299825489521,
-0.09055917710065842,
-0.06354660540819168,
0.030981270596385002,
-0.04869059473276138,
-0.025159796699881554,
-0.0331437848508358,
0.05908428877592087,
0.040357474237680435,
0.035622917115688324,
-0.015264485031366348,
0.009221642278134823,
0.00... | 0.075283 |
# Configuration examples for using Thanos-based storage clients Use these examples as a starting point for configuring [Thanos based object storage clients](https://grafana.com/docs/loki//configure/#thanos\_object\_store\_config) in Grafana Loki. ## GCS example ```yaml storage\_config: use\_thanos\_objstore: true objec... | https://github.com/grafana/loki/blob/main//docs/sources/configure/examples/thanos-storage-configs.md | main | loki | [
-0.1263212114572525,
0.01258337777107954,
-0.053877152502536774,
-0.045458078384399414,
-0.07266541570425034,
-0.050158724188804626,
-0.010756803676486015,
0.009252042509615421,
0.0011618571588769555,
0.08117051422595978,
0.020772891119122505,
-0.046490125358104706,
0.031894564628601074,
0... | 0.005756 |
# Alerting There are two types of alerts in Grafana: - \*\*Grafana-managed alerts:\*\* The recommended alert rule type in Grafana Alerting. These alert rules can query a wide range of backend data sources, including multiple data sources in a single alert rule. They support expression-based transformations, advanced al... | https://github.com/grafana/loki/blob/main//docs/sources/alert/_index.md | main | loki | [
-0.07880720496177673,
-0.0012392738135531545,
-0.06923163682222366,
0.06167976185679436,
0.04909727722406387,
-0.12549521028995514,
0.025749461725354195,
-0.06219002604484558,
0.021016409620642662,
0.0075646028853952885,
-0.02219025045633316,
-0.060449324548244476,
0.07533685117959976,
-0.... | 0.151185 |
its cardinality by the number of tenants). Creating these alerts in LogQL is attractive because these metrics can be extracted at \_query time\_, meaning we don't suffer the cardinality explosion in our metrics store. {{< admonition type="note" >}} As an example, we can use LogQL v2 to help Loki to monitor \_itself\_, ... | https://github.com/grafana/loki/blob/main//docs/sources/alert/_index.md | main | loki | [
0.050782009959220886,
-0.004099514335393906,
-0.027179470285773277,
0.08271825313568115,
0.010128194466233253,
-0.09604984521865845,
0.08521123230457306,
-0.018436769023537636,
0.10549965500831604,
-0.012300316244363785,
0.006877261679619551,
-0.09502880275249481,
0.06749390810728073,
0.04... | 0.15715 |
(job) > 0.05 for: 10m labels: severity: page annotations: summary: High request latency - record: nginx:requests:rate1m expr: | sum( rate({container="nginx"}[1m]) ) labels: cluster: "us-central1" ``` ### Remote-Write With recording rules, you can run these metric queries continually on an interval, and have the resulti... | https://github.com/grafana/loki/blob/main//docs/sources/alert/_index.md | main | loki | [
-0.09432943910360336,
-0.0006979745230637491,
-0.044784728437662125,
0.03918427973985672,
-0.034954529255628586,
-0.0916731208562851,
-0.045798659324645996,
-0.03675591200590134,
0.012999015860259533,
0.010893432423472404,
-0.0572255477309227,
-0.04639342799782753,
-0.01168701983988285,
0.... | 0.207771 |
(job) (http\_inprogress\_requests)" record = "job:http\_inprogress\_requests:sum" } } ``` ### Cortex rules action The [Cortex rules action](https://github.com/grafana/cortex-rules-action) introduced Loki as a backend which can be handy for managing rules in a CI/CD pipeline. It can be used to lint, diff, and sync rules... | https://github.com/grafana/loki/blob/main//docs/sources/alert/_index.md | main | loki | [
-0.08963841944932938,
-0.03837965428829193,
-0.04194571450352669,
0.016921773552894592,
-0.03232314810156822,
-0.11376689374446869,
-0.03671039640903473,
0.0470949187874794,
0.015962913632392883,
0.06968393176794052,
0.02181536704301834,
-0.06555895507335663,
0.01700420305132866,
0.0136623... | 0.17826 |
load past evaluations when rescheduling or resharding Rulers. | https://github.com/grafana/loki/blob/main//docs/sources/alert/_index.md | main | loki | [
-0.04053270071744919,
0.07718931138515472,
-0.00903286226093769,
0.05553201958537102,
-0.06356965750455856,
-0.036908313632011414,
-0.08701355755329132,
-0.012643739581108093,
0.009487209841609001,
0.007570336572825909,
-0.03485475853085518,
0.034698981791734695,
0.009008346125483513,
-0.0... | 0.063859 |
# Upgrade Loki Every attempt is made to keep Grafana Loki backwards compatible, such that upgrades should be low risk and low friction. Unfortunately Loki is software and software is hard and sometimes we are forced to make decisions between ease of use and ease of maintenance. If we have any expectation of difficulty ... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.01826466992497444,
-0.0016958273481577635,
0.02792835794389248,
-0.07881557941436768,
0.03615349158644676,
-0.08514486998319626,
-0.09985344111919403,
-0.03572617098689079,
-0.02969939261674881,
0.03471723571419716,
-0.006852444261312485,
-0.06864035129547119,
-0.06621450930833817,
0.04... | 0.003619 |
- \*\*No data loss\*\* - PersistentVolumeClaims and data are preserved - New StatefulSets will be created with correct service references ## 3.6.0 ### Loki 3.6.0 #### Upgraded AWS SDK to v2 Loki uses the official AWS SDK for configuring and communication with S3 object storage. Version 1 of the SDK reached its end of l... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.0118247764185071,
-0.0007643891731277108,
-0.032181303948163986,
0.012831790372729301,
0.038491737097501755,
0.0038401184137910604,
-0.06751636415719986,
0.009899022057652473,
0.0867975726723671,
0.04891282692551613,
0.03183075785636902,
-0.0073993331752717495,
0.03739884868264198,
-0.0... | 0.036439 |
### Loki 3.2.0 ### HTTP API The API endpoint for instant queries `/api/v1/query` now returns a HTTP status 400 (Bad Request) when the provided `query` parameter contains a log selector query instead of returning inconsistent results. Please use the range query endpoint `/api/v1/query\_range` (`Range` type in Grafana Ex... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.039689745754003525,
0.07539255172014236,
-0.010168232955038548,
0.08356846123933792,
0.015026886947453022,
-0.10628386586904526,
-0.011323000304400921,
-0.04091048240661621,
0.029707113280892372,
0.01827060617506504,
-0.0004033769073430449,
-0.06085936352610588,
-0.0044052633456885815,
... | 0.096911 |
additional validation errors. {{< /admonition >}} {{< admonition type="tip" >}} If you configure `path\_prefix` in the `common` config section this can help save a lot of configuration. Refer to the [Common Config Docs](https://grafana.com/docs/loki//configure/#common). {{< /admonition >}} The \*\*Helm chart\*\* has go... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.0648019090294838,
0.01066556852310896,
-0.043306052684783936,
-0.059433091431856155,
-0.0017941792029887438,
-0.07550830394029617,
-0.09539391100406647,
-0.009848070330917835,
-0.012567522004246712,
0.03420866280794144,
0.03725412115454674,
-0.06233982741832733,
-0.05832253396511078,
-0... | 0.08393 |
all the periods that use `boltdb-shipper` as index type, no additional changes are required besides removing the usage of the deleted configuration option. - If there is a mismatch, you lose access to the index for periods where `-boltdb.shipper.shared-store` does not match `object\_store`. - To make these indexes quer... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.022434866055846214,
-0.034325793385505676,
0.015783311799168587,
0.12631498277187347,
-0.03239928558468819,
0.026243535801768303,
0.0021838124375790358,
-0.05904991552233696,
-0.001839077565819025,
0.005204359069466591,
-0.024472322314977646,
0.03877789154648781,
-0.009092643857002258,
... | 0.04994 |
to new ingesters when the old ingester was shutting down during a rolling restart. Alternatives to this setting are: - \*\*A. (Preferred)\*\* Enable the WAL and rely on the new ingester to replay the WAL. - Optionally, you can enable `flush\_on\_shutdown` (`-ingester.flush-on-shutdown`) to flush to long-term storage on... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.08208155632019043,
0.0034482493065297604,
-0.06933963298797607,
0.05275575444102287,
-0.042187970131635666,
-0.01787729375064373,
-0.029160151258111,
0.01595144532620907,
-0.027530500665307045,
0.05737517774105072,
-0.02965163066983223,
0.06876059621572495,
-0.08105400949716568,
-0.0268... | 0.132113 |
in the replication set. Helps with deduplicating chunks. | | `ingester.sync-min-utilization` | 0.1 | 0 | - | | `frontend.max-querier-bytes-read` | 150GB | 0 | - | | `frontend.max-cache-freshness` | 10m | 1m | - | | `frontend.max-stats-cache-freshness` | 10m | 0 | - | | `frontend.embedded-cache.max-size-mb` | 100MB | 1G... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.03374519199132919,
-0.009478661231696606,
-0.08918739855289459,
-0.003496405202895403,
-0.06532604992389679,
-0.11486224830150604,
-0.037942808121442795,
0.04454836621880531,
-0.06891363859176636,
0.053237855434417725,
0.012942302972078323,
0.07907481491565704,
0.05431956797838211,
-0.1... | 0.041964 |
`cortex\_ring\_member\_heartbeats\_total` - `cortex\_ring\_member\_tokens\_owned` - `cortex\_ring\_member\_tokens\_to\_own` - `cortex\_ring\_members` - `cortex\_ring\_oldest\_member\_timestamp` - `cortex\_ring\_tokens\_total` - `cortex\_ruler\_client\_request\_duration\_seconds\_bucket` - `cortex\_ruler\_client\_reques... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
0.007223606109619141,
-0.020319556817412376,
-0.04103396460413933,
-0.007907208986580372,
-0.040676143020391464,
-0.048316262662410736,
0.08299557119607925,
0.04329053685069084,
0.02143915556371212,
0.028421420603990555,
0.07571592926979065,
-0.09593769162893295,
0.09230189770460129,
-0.09... | 0.128928 |
a tsdb or boltdb-shipper index is used for storing delete requests to ensure pending requests are processed. #### logfmt parser non-strict parsing logfmt parser now performs non-strict parsing which helps scan semi-structured log lines. It skips invalid tokens and tries to extract as many key/value pairs as possible fr... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.0023769750259816647,
-0.035785965621471405,
0.02187718264758587,
0.018235979601740837,
0.011715546250343323,
-0.03592323511838913,
0.04001975804567337,
-0.006460166536271572,
0.07142487913370132,
0.047895338386297226,
-0.007648917380720377,
0.01772131957113743,
0.023556962609291077,
0.0... | 0.107131 |
to run go build with tag `promtail\_journal\_enabled`: ```shell go build --tags=promtail\_journal\_enabled ./clients/cmd/promtail ``` Introducing this tag aims to relieve Linux/CentOS users with CGO enabled from installing libsystemd-dev/systemd-devel libraries if they don't need Journal support. ### Ruler #### CLI fla... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
0.010642461478710175,
0.05515419691801071,
-0.0033557871356606483,
-0.0636344701051712,
-0.013162236660718918,
-0.011869069188833237,
-0.04537522792816162,
0.017823847010731697,
-0.03738268092274666,
0.031357068568468094,
0.025948084890842438,
0.0010446779197081923,
-0.041278813034296036,
... | 0.001104 |
implementation (currently a simple FIFO data structure) with something else in the future without causing confusion #### Evenly spread Memcached pods for chunks across kubernetes nodes We now evenly spread memcached\_chunks pods across the available kubernetes nodes, but allowing more than one pod to be scheduled into ... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
0.017617780715227127,
-0.0030388222075998783,
0.042383041232824326,
-0.0011464923154562712,
-0.04110690578818321,
-0.07270648330450058,
-0.020556971430778503,
0.01946711726486683,
0.02900850959122181,
0.06136882305145264,
-0.06736085563898087,
-0.021411284804344177,
-0.012592842802405357,
... | 0.170208 |
configuration for anonymous usage statistics reporting to Grafana has changed from `usage\_report` to `analytics`. #### TLS `cipher\_suites` and `tls\_min\_version` have moved These were previously configurable under `server.http\_tls\_config` and `server.grpc\_tls\_config` separately. They are now under `server.tls\_c... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.1114669069647789,
0.05322851613163948,
-0.12661096453666687,
0.021222388371825218,
-0.09288952499628067,
-0.0791340321302414,
-0.03187956288456917,
-0.03041325882077217,
0.03627844154834747,
0.04780541732907295,
0.05367742478847504,
0.000945860578212887,
0.017519228160381317,
0.02840249... | 0.003461 |
`2h` previously it was `1h`. \* `query\_ingesters\_within` under the `querier` config now defaults to `3h`, previously it was `0s`. Any query (or subquery) that has an end time more than `3h` ago will not be sent to the ingesters, this saves work on the ingesters for data they normally don't contain. If you regularly w... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.03578777238726616,
-0.03854058310389519,
-0.05910627171397209,
0.020697088912129402,
-0.08200293779373169,
-0.06944380700588226,
0.007211859337985516,
-0.000859456486068666,
-0.006510676350444555,
0.03982963785529137,
0.05567750334739685,
-0.012535804882645607,
0.005337981041520834,
-0.... | 0.145113 |
to use deletes via the compactor: ```yaml compactor: retention\_enabled: true limits\_config: retention\_period: [30d] ``` See the [retention docs](https://grafana.com/docs/loki//operations/storage/retention/) for more info. #### Log messages on startup: proto: duplicate proto type registered PR [#3842](https://github.... | https://github.com/grafana/loki/blob/main//docs/sources/setup/upgrade/_index.md | main | loki | [
-0.092692531645298,
-0.006676187738776207,
-0.030137095600366592,
-0.03540235012769699,
0.005424622446298599,
-0.10815645754337311,
0.012467331252992153,
-0.019316058605909348,
0.09158019721508026,
0.03737707436084747,
0.06684137880802155,
-0.0290206428617239,
-0.028767438605427742,
0.0350... | 0.147839 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.