content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
========================================== Reducing OS jitter due to per-cpu kthreads ========================================== This document lists per-CPU kthreads in the Linux kernel and presents options to control their OS jitter. Note that non-per-CPU kthreads are not listed here. To reduce OS jitter from non-per-... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.03993845731019974,
0.004581197164952755,
-0.10449253022670746,
0.06316440552473068,
-0.05950404331088066,
-0.11224061250686646,
0.060712121427059174,
0.01180310733616352,
-0.003997372929006815,
-0.03034420683979988,
0.007407653611153364,
-0.007780849002301693,
-0.03144599497318268,
-0.0... | 0.184198 |
I/O on other CPUs. 3. Once your application has started, prevent CPU-hotplug operations from being initiated from tasks that might run on the CPU to be de-jittered. (It is OK to force this CPU offline and then bring it back online before you start your application.) IRQ\_POLL\_SOFTIRQ ---------------- Do all of the fol... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.059582777321338654,
-0.029057027772068977,
-0.042440466582775116,
0.05370680242776871,
0.0012001552386209369,
-0.09820961207151413,
0.0571339949965477,
0.0436202809214592,
-0.022215772420167923,
0.006336777471005917,
-0.0006715768831782043,
-0.000253343372605741,
-0.046253710985183716,
... | 0.123303 |
the CPU goes idle frequently, allowing other CPUs to detect that it has passed through an RCU quiescent state. If the kernel is built with CONFIG\_NO\_HZ\_FULL=y, userspace execution also allows other CPUs to detect that the CPU in question has passed through a quiescent state. c. To the extent possible, keep the CPU o... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.05053244158625603,
0.04534224420785904,
-0.03210531547665596,
0.05710400640964508,
0.03601113706827164,
-0.09491346031427383,
0.004353432450443506,
0.0023799960035830736,
0.06927461177110672,
-0.021595660597085953,
0.013446218334138393,
-0.057799432426691055,
-0.010367278009653091,
-0.0... | 0.095247 |
from being created in the first place, and also obviates the need for RCU priority boosting. This approach is feasible for workloads that do not require high degrees of responsiveness. 2. Build the kernel with CONFIG\_RCU\_BOOST=n. This prevents these kthreads from being created in the first place. This approach is fea... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/kernel-per-CPU-kthreads.rst | master | linux | [
-0.11524944752454758,
0.04138917475938797,
-0.02593618631362915,
0.03344263508915901,
0.012682924047112465,
-0.010632087476551533,
-0.04497218132019043,
-0.038741711527109146,
0.0013902049977332354,
-0.025317557156085968,
0.02008719928562641,
-0.004474654793739319,
0.010039440356194973,
-0... | 0.077373 |
.. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) .. See the bottom of this file for additional redistribution information. Reporting issues ++++++++++++++++ The short guide (aka TL;DR) =========================== Are you facing a regression with vanilla kernels from the same stable or longterm series? One still supp... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.03498361259698868,
-0.08567182719707489,
-0.0019017213489860296,
0.04086824133992195,
0.08761459589004517,
-0.028711983934044838,
-0.06783454120159149,
-0.004684747196733952,
-0.03875764086842537,
-0.02476668916642666,
-0.022978372871875763,
0.01325589045882225,
-0.021951304748654366,
0... | -0.007953 |
invest in this process won't feel wasted in the end: \* Are you facing an issue with a Linux kernel a hardware or software vendor provided? Then in almost all cases you are better off to stop reading this document and reporting the issue to your vendor instead, unless you are willing to install the latest Linux version... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.028752973303198814,
-0.005523581523448229,
0.010102961212396622,
0.01943461410701275,
0.1146743893623352,
-0.11338485777378082,
-0.05280674248933792,
0.10447447001934052,
-0.06159164011478424,
0.009513122960925102,
0.04908722639083862,
0.0023431621957570314,
-0.04330070689320564,
-0.036... | 0.130249 |
longterm kernels. \* Optimize your notes: try to find and write the most straightforward way to reproduce your issue. Make sure the end result has all the important details, and at the same time is easy to read and understand for others that hear about it for the first time. And if you learned something in this process... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.0076898448169231415,
-0.03627489507198334,
0.02216409705579281,
0.025080835446715355,
0.059571634978055954,
-0.11051807552576065,
-0.09455568343400955,
0.09977322071790695,
-0.05065656080842018,
-0.007090551778674126,
0.03825102746486664,
-0.008619974367320538,
-0.02198931574821472,
-0.0... | 0.099974 |
build of the last version known to work performs fine as well. \* Send a short problem report to the Linux stable mailing list (stable@vger.kernel.org) and CC the Linux regressions mailing list (regressions@lists.linux.dev); if you suspect the cause in a particular subsystem, CC its maintainer and its mailing list. Rou... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.016328858211636543,
-0.08875510096549988,
0.06363441795110703,
0.06420400738716125,
0.11132846027612686,
-0.0687488466501236,
-0.138572558760643,
0.012694668024778366,
-0.04799431934952736,
-0.025032546371221542,
0.05682627111673355,
0.043773356825113297,
-0.06800290197134018,
0.01404444... | -0.028153 |
are completely outside the scope of the Linux kernel, its development community, and this document. That's why you can't demand anything such a contract guarantees in this context, not even if the developer handling the issue works for the vendor in question. If you want to claim your rights, use the vendor's support c... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.06662243604660034,
0.0348496250808239,
-0.0331195704638958,
0.00502148037776351,
0.02391481213271618,
-0.01774112693965435,
-0.032739877700805664,
0.13232025504112244,
-0.07524276524782181,
0.01632028818130493,
0.014545666985213757,
-0.022944269701838493,
-0.009429807774722576,
-0.05475... | 0.044592 |
kernel based on a recent Linux version; that for example often holds true for the mainline kernels shipped by Debian GNU/Linux Sid or Fedora Rawhide. Some developers will also accept reports about issues with kernels from distributions shipping the latest stable kernel, as long as it's only slightly modified; that for ... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.03907281532883644,
-0.09797312319278717,
0.028704455122351646,
0.045812107622623444,
0.10458691418170929,
-0.07582849264144897,
-0.10070762038230896,
0.0822349414229393,
-0.08606970310211182,
-0.02572246827185154,
0.05149422585964203,
0.0030312733724713326,
-0.07274909317493439,
-0.01768... | 0.016755 |
involved. Note, searching `bugzilla.kernel.org `\_ might also be a good idea, as that might provide valuable insights or turn up matching reports. If you find the latter, just keep in mind: most subsystems expect reports in different places, as described below in the section "Check where you need to report your issue".... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.05894682556390762,
-0.046675506979227066,
-0.04588025063276291,
0.044631361961364746,
0.04982512816786766,
-0.07224101573228836,
-0.030145304277539253,
0.05779512971639633,
-0.09813182801008224,
0.012361746281385422,
0.025808600708842278,
0.042928870767354965,
0.001138880499638617,
-0.0... | 0.105399 |
\* When dealing with a regression, make sure it's not something else that changed in parallel to updating the kernel. The problem for example might be caused by other software that was updated at the same time. It can also happen that a hardware component coincidentally just broke when you rebooted into a new kernel fo... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.04433516785502434,
-0.07118601351976395,
0.0723460242152214,
0.05801587924361229,
0.1096569299697876,
-0.10131483525037766,
-0.04215015098452568,
0.05967806652188301,
-0.018013207241892815,
-0.025317242369055748,
0.02097262628376484,
0.036173202097415924,
-0.04636330530047417,
-0.002675... | 0.103814 |
search for a line starting with 'CPU:'. It should end with 'Not tainted' if the kernel was not tainted when it noticed the problem; it was tainted if you see 'Tainted:' followed by a few spaces and some letters. If your kernel is tainted, study Documentation/admin-guide/tainted-kernels.rst to find out why. Try to elimi... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
0.034859757870435715,
-0.054668597877025604,
0.03808533027768135,
0.04205365851521492,
0.14559891819953918,
-0.09794337302446365,
-0.01536782830953598,
0.037563834339380264,
0.054054249078035355,
-0.07766994833946228,
0.003866475075483322,
-0.02089347504079342,
-0.011055279523134232,
0.023... | -0.004915 |
you will have to test if the issue happens with other kernel versions. Therefore, it will make your work easier if you know exactly how to reproduce an issue quickly on a freshly booted system. Note: it's often fruitless to report issues that only happened once, as they might be caused by a bit flip due to cosmic radia... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.013727943412959576,
-0.08313494175672531,
0.07749711722135544,
0.09704497456550598,
0.16495424509048462,
-0.08392436802387238,
-0.1543184369802475,
0.023275908082723618,
-0.02373453602194786,
-0.04326217994093895,
0.06178942322731018,
0.024105237796902657,
-0.018397534266114235,
-0.0148... | -0.002185 |
you for example might want to look at the output of ``lspci -k``, as it lists devices on the PCI/PCIe bus and the kernel module driving it:: [user@something ~]$ lspci -k [...] 3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. Device 1535 Ke... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.009846191853284836,
-0.0018106262432411313,
-0.08222927898168564,
0.03172357752919197,
0.07162589579820633,
-0.0036029554903507233,
-0.028685949742794037,
-0.04500235244631767,
0.01369587704539299,
0.007479379884898663,
0.0967441126704216,
0.016181200742721558,
-0.020382283255457878,
0.... | 0.016447 |
Kernel Mailing List (LKML) to CC. Don't omit either of the mailing lists when sending your issue report by mail later! Maintainers are busy people and might leave some work for other developers on the subsystem specific list; and LKML is important to have one place where all issue reports can be found. Finding the main... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.06208473816514015,
0.0013937753392383456,
-0.055336154997348785,
0.0422641783952713,
0.15604016184806824,
-0.04803026467561722,
0.018736179918050766,
0.07540544122457504,
-0.06860622018575668,
-0.05032553896307945,
0.0565020851790905,
-0.06394047290086746,
-0.016931157559156418,
-0.0636... | 0.049741 |
It's also wise to check the internet, LKML and maybe bugzilla.kernel.org again at this point. If your report needs to be filed in a bug tracker, you may want to check the mailing list archives for the subsystem as well, as someone might have reported it only there. For details how to search and what to do if you find m... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.017442917451262474,
-0.05498875305056572,
-0.0528225302696228,
0.04057281091809273,
0.09772714227437973,
-0.05409525707364082,
-0.14175909757614136,
0.09643857926130295,
-0.08047320693731308,
-0.03292739763855934,
0.055899884551763535,
0.022837145254015923,
-0.047726355493068695,
-0.003... | 0.043514 |
(5.8-rc1) shows up on kernel.org. That's because the Linux development cycle then is in its two-week long 'merge window'. The bulk of the changes and all intrusive ones get merged for the next release during this time. It's a bit more risky to use mainline during this period. Kernel developers are also often quite busy... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.009754616767168045,
-0.05582521855831146,
0.05700007826089859,
0.060061998665332794,
0.10196197032928467,
-0.040738996118307114,
-0.10561614483594894,
0.12007986009120941,
-0.02885768935084343,
-0.029062969610095024,
0.05796852335333824,
0.05350343883037567,
-0.07586901634931564,
0.0034... | -0.002411 |
in this document. Also be aware that pre-compiled kernels might lack debug symbols that are needed to decode messages the kernel prints when a panic, Oops, warning, or BUG occurs; if you plan to decode those, you might be better off compiling a kernel yourself (see the end of this subsection and the section titled 'Dec... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.046906717121601105,
-0.05130131542682648,
0.03882180526852608,
0.024036981165409088,
0.0728849247097969,
-0.05655408278107643,
-0.005661180708557367,
0.06953482329845428,
-0.03872746229171753,
-0.010328643023967743,
0.07957220822572708,
0.03535335883498192,
-0.020943686366081238,
-0.077... | 0.112862 |
those). If you prefer to use one of those or just want to help their users, head over to the section "Details about reporting issues only occurring in older kernel version lines" below. Optimize description to reproduce issue --------------------------------------- \*Optimize your notes: try to find and write the most ... | https://github.com/torvalds/linux/blob/master/Documentation/admin-guide/reporting-issues.rst | master | linux | [
-0.03883688151836395,
0.05632559210062027,
-0.029846487566828728,
0.03860769793391228,
0.05794762820005417,
-0.06648143380880356,
-0.04337180405855179,
0.10700208693742752,
-0.05353284627199173,
0.011340096592903137,
0.056783951818943024,
0.01615498960018158,
-0.013673958368599415,
0.00091... | 0.145653 |
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.0008952902862802148,
-0.027353588491678238,
-0.05608828738331795,
-0.007792891934514046,
-0.009260270744562149,
0.005074712447822094,
0.003946343902498484,
0.06795146316289902,
0.02043541707098484,
-0.005791584495455027,
0.02272329293191433,
-0.09193850308656693,
0.014346460811793804,
0... | 0.15045 |
| | `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.026019910350441933,
0.002906725276261568,
-0.031092055141925812,
-0.04068541154265404,
-0.0483119897544384,
-0.09136170893907547,
-0.08902200311422348,
0.08955240994691849,
-0.008502047508955002,
-0.01688210293650627,
-0.016061905771493912,
-0.03874862194061279,
-0.0610143318772316,
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.0566827729344368,
-0.01756930910050869,
-0.06955809891223907,
0.05637914314866066,
-0.013116009533405304,
-0.04795677587389946,
-0.00924777053296566,
0.035843104124069214,
0.026993803679943085,
0.08101876080036163,
-0.03200800344347954,
0.015496043488383293,
-0.011641566641628742,
0.067... | 0.192538 |
prefix: index\_ period: 24h - from: 2023-07-01 store: tsdb object\_store: filesystem schema: v13 index: prefix: index\_ period: 24h ``` For all data ingested before 2023-07-01, Loki used BoltDB with the v11 schema, and then switched after that point to the more effective TSDB with the v13 schema. This dramatically simp... | https://github.com/grafana/loki/blob/main/docs/sources/configure/storage.md | main | loki | [
-0.059914059937000275,
-0.042793892323970795,
-0.04185732081532478,
0.00524690980091691,
-0.030804753303527832,
-0.026858609169721603,
-0.07952479273080826,
0.0325331874191761,
-0.04688997566699982,
0.03278238698840141,
0.019280383363366127,
0.0235441904515028,
-0.01050439104437828,
0.0261... | 0.11094 |
### AWS deployment (S3 Single Store) ```yaml storage\_config: tsdb\_shipper: active\_index\_directory: /loki/index cache\_location: /loki/index\_cache cache\_ttl: 24h # Can be increased for faster performance over longer query periods, uses more disk space aws: s3: s3://:@ bucketnames: schema\_config: configs: - from: ... | https://github.com/grafana/loki/blob/main/docs/sources/configure/storage.md | main | loki | [
0.015075639821588993,
-0.03063647821545601,
-0.0641135647892952,
0.003889695508405566,
-0.03288379684090614,
-0.0005950222839601338,
-0.03047259896993637,
-0.011640680953860283,
0.04151083901524544,
0.08032356947660446,
0.015856128185987473,
-0.04813604801893234,
0.057260286062955856,
-0.0... | 0.031831 |
schema\_config: configs: - from: 2020-07-01 store: tsdb object\_store: s3 schema: v13 index: prefix: index\_ period: 24h ```~~ | https://github.com/grafana/loki/blob/main/docs/sources/configure/storage.md | main | loki | [
0.0002188551297876984,
-0.01480264775454998,
-0.03148831054568291,
0.006138235330581665,
-0.034506019204854965,
0.037147168070077896,
-0.002825989853590727,
-0.020766563713550568,
0.001880775555036962,
0.03042987547814846,
0.03947122022509575,
-0.012363806366920471,
-0.005269100423902273,
... | 0.073219 |
# 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 |
# Usage statistics Loki sends anonymous usage statistics to Grafana Labs. This reporting is enabled by default and helps the Loki team understand aggregate usage patterns. Reports are sent to `https://stats.grafana.org/loki-usage-report` by default. ## What Loki collects Loki reports aggregate operational metadata, inc... | https://github.com/grafana/loki/blob/main/docs/sources/configure/usage-statistics.md | main | loki | [
-0.01585758663713932,
-0.020381176844239235,
-0.12639933824539185,
0.0721026137471199,
-0.02173599600791931,
-0.03982309252023697,
-0.005515631753951311,
0.02600443921983242,
0.033157192170619965,
0.03115060366690159,
0.00990722980350256,
-0.01952272653579712,
-0.002775191329419613,
0.0332... | 0.191397 |
# 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.