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 |
|---|---|---|---|---|---|
in the Grafana database. When connecting to the database, the certificates are saved as files, on the local filesystem, in the Grafana data path. | \*\*TLS/SSL Auth Details:\*\* If you select the TLS/SSL Mode options \*\*require\*\*, \*\*verify-ca\*\* or \*\*verify-full\*\* and \*\*file system path\*\* the following ar... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/configure/_index.md | main | grafana | [
-0.08101431280374527,
0.02722027339041233,
-0.1347365528345108,
0.014463619329035282,
-0.10276811569929123,
-0.046737171709537506,
-0.1051122173666954,
-0.05175440013408661,
0.03658495470881462,
0.010328358970582485,
0.0056086075492203236,
-0.06706875562667847,
0.05718762055039406,
0.01788... | -0.02842 |
added your PostgreSQL connection settings, click \*\*Save & test\*\* to test and save the data source connection. ### Min time interval The \*\*Min time interval\*\* setting defines a lower limit for the [`$\_\_interval`](https://grafana.com/docs/grafana//dashboards/variables/add-template-variables/#\_\_interval) and [... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/configure/_index.md | main | grafana | [
-0.07083985954523087,
0.005877608899027109,
-0.10631460696458817,
0.040439993143081665,
-0.14250990748405457,
-0.016537480056285858,
-0.09560270607471466,
-0.03191631659865379,
0.000996464747004211,
0.012417273595929146,
-0.027624577283859253,
-0.05994550883769989,
0.01215708814561367,
-0.... | -0.001652 |
# PostgreSQL template variables Instead of hard-coding details such as server, application, and sensor names in metric queries, you can use variables. Grafana displays these variables in drop-down select boxes at the top of the dashboard to help you change the data displayed in your dashboard. Grafana refers to such va... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/template-variables/index.md | main | grafana | [
-0.05494480952620506,
0.04770033061504364,
-0.10618431866168976,
0.03530323877930641,
-0.12080324441194534,
-0.034893617033958435,
0.0121608292683959,
-0.030189011245965958,
-0.020867690443992615,
0.01593445986509323,
-0.039843976497650146,
-0.09881983697414398,
0.009347408078610897,
-0.04... | 0.04839 |
identifiers in different contexts (for example, an environment called `dev` in one system and `development` in another). Instead of maintaining several variables in sync, you can map all of those values to one variable and reference the property you need in each panel or query. {{< figure alt="PostgreSQL multi-property... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/template-variables/index.md | main | grafana | [
-0.025907309725880623,
-0.015582646243274212,
-0.0436413437128067,
0.0428471565246582,
-0.06400205194950104,
0.053555093705654144,
0.04445336014032364,
0.04402788728475571,
-0.009216705337166786,
-0.0027286612894386053,
0.005065593868494034,
-0.05464385449886322,
0.04248892888426781,
0.014... | -0.069809 |
# Troubleshoot PostgreSQL data source issues This document provides troubleshooting information for common errors you may encounter when using the PostgreSQL data source in Grafana. ## Connection errors The following errors occur when Grafana cannot establish or maintain a connection to PostgreSQL. ### Failed to connec... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/troubleshooting/index.md | main | grafana | [
-0.056334372609853745,
0.019346358254551888,
-0.08847732096910477,
-0.03823365643620491,
-0.1495368629693985,
-0.06916330009698868,
-0.0938359722495079,
-0.0783415138721466,
-0.0026004977989941835,
0.06461258232593536,
-0.011645644903182983,
-0.026505865156650543,
-0.036372099071741104,
-0... | -0.030532 |
connections from the Grafana server: ```text host database\_name username grafana\_ip/32 md5 ``` 1. Reload PostgreSQL configuration: `SELECT pg\_reload\_conf();` 1. If using SSL, ensure the correct authentication method is specified (for example, `hostssl` instead of `host`). ## TLS and certificate errors The following... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/troubleshooting/index.md | main | grafana | [
-0.062131114304065704,
0.05149044096469879,
-0.061749063432216644,
-0.02257359027862549,
-0.1340678334236145,
-0.10314317792654037,
-0.03889678046107292,
-0.10014451295137405,
0.0370459146797657,
0.039289265871047974,
-0.019401023164391518,
-0.04336857050657272,
0.0005868641310371459,
0.03... | -0.085255 |
a PostgreSQL client (psql, pgAdmin). ### Column does not exist \*\*Error message:\*\* `ERROR: column "column\_name" does not exist (SQLSTATE 42703)` \*\*Cause:\*\* The specified column name is incorrect or doesn't exist in the table. \*\*Solution:\*\* 1. Verify the column name is spelled correctly. 1. Check that column... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/troubleshooting/index.md | main | grafana | [
0.02088984102010727,
-0.03484611585736275,
-0.03564763814210892,
0.03170916810631752,
-0.012107417918741703,
-0.021365270018577576,
0.0025406358763575554,
0.034798987209796906,
0.036230284720659256,
0.0012706106062978506,
0.010496147908270359,
-0.06635689735412598,
0.006924315821379423,
-0... | -0.030826 |
values are properly quoted in the YAML file. 1. Refer to the [provisioning example](https://grafana.com/docs/grafana//datasources/postgres/configure/#provision-the-data-source) for the correct format. Example correct configuration: ```yaml datasources: - name: Postgres type: postgres url: localhost:5432 user: grafana s... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/troubleshooting/index.md | main | grafana | [
-0.05613810941576958,
0.02198042906820774,
-0.05361809581518173,
-0.015403826721012592,
-0.10676129162311554,
-0.05521683394908905,
-0.05534384399652481,
-0.05129773169755936,
-0.00889263954013586,
0.057683065533638,
0.03235992416739464,
-0.07634478807449341,
-0.026364663615822792,
-0.0568... | -0.036455 |
# PostgreSQL query editor The PostgreSQL query editor lets you build and run queries against your data source. For general query editor and data transformation concepts, see [Query and transform data](https://grafana.com/docs/grafana//panels-visualizations/query-transform-data/). You can open the PostgreSQL query edito... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/query-editor/_index.md | main | grafana | [
-0.06794925034046173,
0.005327614489942789,
-0.07011637836694717,
0.101803258061409,
-0.11563925445079803,
0.006035061553120613,
-0.012745783664286137,
-0.05167428404092789,
0.017692700028419495,
0.044314492493867874,
-0.017098000273108482,
-0.011284466832876205,
-0.024747880175709724,
-0.... | 0.032586 |
SQL keywords, standard SQL functions, Grafana template variables, and Grafana macros. Columns cannot be completed before a table has been specified. {{< admonition type="note" >}} If a table or column name is a reserved word or contains mixed case or special characters, use double quotes in SQL. For example, `"user"` o... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/query-editor/_index.md | main | grafana | [
-0.02975841797888279,
0.025466345250606537,
-0.03513585031032562,
0.11320082098245621,
-0.05819716304540634,
0.035639774054288864,
0.03491983190178871,
0.04868278652429581,
-0.05295323580503464,
0.0870155543088913,
0.027818672358989716,
-0.09454105794429779,
0.07291453331708908,
-0.0712026... | -0.005117 |
start of the currently active time selection as a nanosecond timestamp. Example: `1494410783152415214`. | | `$\_\_unixEpochNanoTo()` | Replaces the value with the end of the currently active time selection as a nanosecond timestamp. Example: `1494497183142514872`. | | `$\_\_unixEpochGroup(dateColumn,'5m', [fillmode])` ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/query-editor/_index.md | main | grafana | [
-0.009110595099627972,
-0.014048485085368156,
-0.08205971121788025,
0.06294088065624237,
0.021651247516274452,
-0.05419405177235603,
0.020995352417230606,
0.03840683028101921,
0.05748017132282257,
0.025249311700463295,
0.01739886775612831,
-0.08526607602834702,
-0.038182154297828674,
-0.03... | 0.069346 |
BY time ``` \*\*Example using the fill parameter in the $\\_\\_timeGroupAlias macro to convert null values to zero:\*\* ```sql SELECT $\_\_timeGroupAlias("CreatedAt",'5m',0), sum(value) as value, hostname FROM test\_data WHERE $\_\_timeFilter("CreatedAt") GROUP BY time, hostname ORDER BY time ``` Based on the data fram... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/query-editor/_index.md | main | grafana | [
-0.05511699989438057,
0.019378509372472763,
-0.07153988629579544,
0.03748811408877373,
-0.11626345664262772,
-0.011733503080904484,
0.05425209552049637,
-0.050597183406353,
0.03397228196263313,
-0.0012737322831526399,
0.03027845174074173,
-0.1296754628419876,
-0.022982157766819,
-0.0099037... | -0.059075 |
# PostgreSQL annotations Annotations overlay event data on your dashboard graphs, helping you correlate events with metrics. You can use PostgreSQL as a data source for annotations to display events such as deployments, alerts, or other significant occurrences on your visualizations. For general information about annot... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/annotations/index.md | main | grafana | [
-0.0016259949188679457,
0.0036479774862527847,
-0.035603441298007965,
0.010015975683927536,
-0.03388206288218498,
0.0002091432543238625,
0.008415790274739265,
-0.007665568962693214,
0.0643744096159935,
0.005192965734750032,
-0.05358259752392769,
-0.08928007632493973,
-0.04395943880081177,
... | 0.056637 |
- \*\*Organize with tags:\*\* Use consistent tag values to categorize annotations and enable filtering. - \*\*Test queries first:\*\* Verify your query returns expected results in Explore before adding it as an annotation. | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/postgres/annotations/index.md | main | grafana | [
-0.0015476917615160346,
0.037064846605062485,
-0.012765318155288696,
0.07181701809167862,
0.02036382630467415,
0.031573571264743805,
0.11306645721197128,
-0.0815642923116684,
-0.016732819378376007,
-0.01303288247436285,
-0.02542102336883545,
-0.10278307646512985,
0.04743153601884842,
0.056... | 0.096158 |
# Zipkin data source Grafana ships with built-in support for Zipkin, an open source, distributed tracing system. This topic explains configuration and queries specific to the Zipkin data source. For instructions on how to add a data source to Grafana, refer to the [administration documentation](https://grafana.com/docs... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/zipkin/_index.md | main | grafana | [
-0.09453228861093521,
-0.004466464277356863,
-0.11635512858629227,
0.06123866140842438,
-0.06635474413633347,
-0.09954546391963959,
-0.031326282769441605,
-0.017719488590955734,
-0.030190277844667435,
0.07096919417381287,
-0.025425145402550697,
-0.03865332156419754,
0.06440764665603638,
-0... | 0.04053 |
data source from the drop-down list. You can also click \*\*Open advanced data source picker\*\* to see more options, including adding a data source. 1. Set start and end time shift. Since the logs timestamps may not exactly match the timestamps of the spans in the trace, you may need to widen or shift the time range t... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/zipkin/_index.md | main | grafana | [
-0.05264723300933838,
0.047869231551885605,
0.02336609736084938,
0.054918721318244934,
0.114261694252491,
-0.09426110237836838,
0.07934950292110443,
-0.03810678794980049,
-0.01016913540661335,
0.020049728453159332,
0.026864131912589073,
-0.03672632575035095,
-0.0045889331959187984,
-0.0578... | -0.035199 |
for the logs query, based on the span's end time. You can use time units. Default: `0`. | | \*\*Tags\*\* | Defines the tags to use in the logs query. Default: `cluster`, `hostname`, `namespace`, `pod`, `service.name`, `service.namespace`. You can change the tag name for example to remove dots from the name if they are ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/zipkin/_index.md | main | grafana | [
0.014525322243571281,
-0.005385836120694876,
-0.009945329278707504,
0.09788179397583008,
-0.015331066213548183,
-0.05651358887553215,
0.049416691064834595,
-0.03687432408332825,
-0.019521180540323257,
0.04109679162502289,
0.005148234777152538,
-0.05527123808860779,
0.046910639852285385,
-0... | 0.126656 |
spanEndTimeShift: '-1h' tags: [{ key: 'service.name', value: 'service' }, { key: 'job' }] queries: - name: 'Sample query' query: 'sum(rate(traces\_spanmetrics\_latency\_bucket{$$\_\_tags}[5m]))' nodeGraph: enabled: true traceQuery: timeShiftEnabled: true spanStartTimeShift: '1h' spanEndTimeShift: '-1h' spanBar: type: '... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/zipkin/_index.md | main | grafana | [
-0.0777699425816536,
0.0217138659209013,
-0.07659287005662918,
0.08577003329992294,
-0.05064503476023674,
-0.08128751814365387,
-0.010065400041639805,
-0.03746456652879715,
0.001083298004232347,
0.0024292776361107826,
-0.024491362273693085,
-0.055263452231884,
0.026770900934934616,
-0.0272... | 0.030757 |
# Span filters When working with traces, especially those comprising a vast number of spans, pinpointing specific spans of interest can be a daunting task. This is where span filtering comes in. Located above the trace timeline viewer, the \*\*Filters\*\* bar lets you refine the spans displayed based on specific criter... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/span-filters.md | main | grafana | [
-0.09395191073417664,
-0.005887993611395359,
0.042325764894485474,
0.05093669518828392,
0.03454543650150299,
-0.0488227941095829,
0.05303126201033592,
-0.07562826573848724,
-0.05733497068285942,
-0.04653637111186981,
-0.04140752553939819,
-0.04684879258275032,
0.03205891326069832,
-0.00782... | 0.033328 |
timeline. The match count displays the current position and total matches (for example, \_2/5 matches\_). ### Remove a filter To remove a filter, click the \*\*×\*\* on the filter chip below the \*\*Filters\*\* text box. ## Common use cases To find all errors from a specific service, select `service.name` = `checkout`,... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/span-filters.md | main | grafana | [
-0.03353341668844223,
-0.012670776806771755,
-0.0838027074933052,
0.017861250787973404,
-0.024966061115264893,
-0.03324703499674797,
0.06317990273237228,
0.00009315156057709828,
0.04099932312965393,
-0.020564721897244453,
0.017967859283089638,
-0.01196027547121048,
0.0632864460349083,
-0.0... | 0.078465 |
# Service Graph and Service Graph view The Service Graph is a visual representation of the relationships between services in a distributed system. Each node represents a service such as an API or database, and each edge represents requests between services. Use the Service Graph to detect performance issues, track erro... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/service-graph.md | main | grafana | [
-0.1127612367272377,
-0.046632133424282074,
-0.08431025594472885,
0.02327265962958336,
-0.03945249691605568,
-0.08108481764793396,
-0.009719766676425934,
-0.024122847244143486,
0.01459556631743908,
-0.012762315571308136,
-0.03771264851093292,
-0.05537984147667885,
0.028104783967137337,
0.0... | 0.248066 |
error rate, use TraceQL: ```traceql { resource.service.name = "" && status = error } ``` Replace \_``\_ with the name shown in the Service Graph node. Refer to [TraceQL query examples](https://grafana.com/docs/grafana//datasources/tempo/query-editor/traceql-query-examples/) for more queries you can run from Service Gra... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/service-graph.md | main | grafana | [
-0.09176138043403625,
0.0056154546327888966,
-0.055946093052625656,
0.054819218814373016,
-0.0851101353764534,
-0.10639704763889313,
-0.016635777428746223,
-0.012617926113307476,
-0.01744098588824272,
0.025944767519831657,
-0.025800423696637154,
-0.10636013001203537,
0.057804614305496216,
... | 0.123151 |
# Tempo data source Grafana ships with built-in support for [Grafana Tempo](https://grafana.com/docs/tempo//), a high-volume, minimal-dependency distributed tracing backend from Grafana Labs. Use the Tempo data source to search and visualize traces, correlate traces with logs, metrics, and profiles, and monitor service... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/_index.md | main | grafana | [
-0.10643331706523895,
-0.028119022026658058,
-0.03576561436057091,
0.020526055246591568,
-0.030597606673836708,
-0.07927899062633514,
-0.0022103306837379932,
-0.06208813935518265,
0.0014664315385743976,
0.03383839130401611,
0.03251977264881134,
-0.0728837102651596,
-0.046450305730104446,
-... | 0.158755 |
to tracing](https://grafana.com/docs/tempo//introduction/) - [Best practices for traces](https://grafana.com/docs/tempo//set-up-for-tracing/instrument-send/best-practices/): Guidance on planning spans, attributes, and trace structure for effective tracing data. - [TraceQL query examples](query-editor/traceql-query-exam... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/_index.md | main | grafana | [
-0.09177868813276291,
0.012557612732052803,
-0.017828598618507385,
0.09342846274375916,
-0.05505025014281273,
-0.04354245215654373,
-0.032791588455438614,
-0.07282599806785583,
-0.00952227134257555,
-0.017947647720575333,
-0.01655563898384571,
-0.05193647742271423,
-0.037367913872003555,
-... | 0.077241 |
# Troubleshoot Tempo data source issues This document provides solutions to common issues you may encounter when configuring or using the Tempo data source in Grafana. ## Scope of this guide This guide covers issues related to connecting Grafana to Tempo and using the data source features. It applies to the following s... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.08442667871713638,
-0.050091881304979324,
-0.037957269698381424,
0.04068008437752724,
-0.029993096366524696,
-0.033426422625780106,
-0.0718901976943016,
-0.09260082244873047,
-0.0011150762438774109,
0.023440349847078323,
0.029536986723542213,
-0.13953225314617157,
-0.026162896305322647,
... | 0.099768 |
terminates the connection before Tempo responds. \*\*Solution:\*\* 1. Check the network latency between Grafana and Tempo. 1. Verify that Tempo isn't overloaded or experiencing performance issues. If you have [Tempo mixin dashboards](https://grafana.com/docs/tempo//operations/monitor/) installed, check them for resourc... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.07496900856494904,
0.04695727676153183,
-0.064145028591156,
0.023899586871266365,
-0.07790931314229965,
-0.08834360539913177,
-0.06626904755830765,
-0.11607452481985092,
0.02053259313106537,
-0.013196430169045925,
0.00792853906750679,
-0.09507376700639725,
-0.007394310552626848,
-0.0138... | 0.070964 |
field is the instance ID (not your Grafana login), and the \*\*Password\*\* is a Cloud Access Policy token. ### Multi-tenant authentication issues \*\*Error message:\*\* `Unauthorized` when using multi-tenant Tempo \*\*Cause:\*\* The tenant ID (`X-Scope-OrgID` header) is missing or incorrect. This header must be set on... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.06857601553201675,
0.027685418725013733,
-0.07111499458551407,
0.009953650645911694,
-0.09802962094545364,
-0.06025705114006996,
-0.0177654679864645,
-0.09267747402191162,
-0.01442178338766098,
0.03410089388489723,
0.03067176789045334,
-0.10309913754463196,
0.0691368579864502,
-0.021232... | 0.016722 |
`=~`, `!~`, `>`, `<`, `>=`, `<=`. ### Query returns no results \*\*Cause:\*\* The query is valid but doesn't match any traces. \*\*Solution:\*\* 1. Expand the time range to search a broader period. 1. Verify the attribute names and values exist in your traces. 1. Check that the attribute names match exactly, as they're... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.05083728954195976,
-0.0005197813152335584,
0.027913914993405342,
0.09080211073160172,
-0.02680307999253273,
-0.014143326319754124,
0.05025496706366539,
-0.04621998593211174,
-0.03767171502113342,
-0.051328498870134354,
-0.008182586170732975,
-0.09945938736200333,
0.054831717163324356,
-... | 0.030852 |
`overrides.defaults.metrics\_generator.processors: [local-blocks]` Refer to [Configure TraceQL metrics](https://grafana.com/docs/tempo//metrics-from-traces/metrics-queries/configure-traceql-metrics/) for setup steps and required configuration. 1. For Grafana Cloud, the `local-blocks` processor is enabled by default. If... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.0858859047293663,
-0.0581546276807785,
-0.07791633158922195,
0.04567890241742134,
-0.0576794259250164,
-0.05849745124578476,
-0.05665617436170578,
-0.09242870658636093,
-0.02128603681921959,
0.020988473668694496,
-0.018743745982646942,
-0.11579032242298126,
-0.04525071009993553,
-0.0248... | 0.045175 |
in Prometheus: - `traces\_service\_graph\_request\_total` - `traces\_service\_graph\_request\_failed\_total` - `traces\_service\_graph\_request\_server\_seconds\_sum` 1. Verify that Grafana Alloy or the Tempo metrics generator is configured to produce these metrics. These are distinct from span metrics (`traces\_spanme... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.11281103640794754,
-0.026498928666114807,
-0.013730568811297417,
0.03310508280992508,
-0.04416996240615845,
-0.11370263993740082,
-0.007421922404319048,
-0.05436700955033302,
0.002229470992460847,
0.011848141439259052,
-0.015444965101778507,
-0.10943573713302612,
0.025278061628341675,
0... | 0.10395 |
field extracts the trace ID from log lines and creates a link to Tempo. 1. Check that the derived field regular expression matches the trace ID format in your logs. Use \*\*Show example log message\*\* in the derived field settings to test the regular expression against a sample log line. 1. Confirm the \*\*Internal li... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.03215509280562401,
-0.014331012964248657,
0.01551881805062294,
0.06234566867351532,
0.06485128402709961,
-0.04261312261223793,
0.05408645421266556,
-0.05847994238138199,
0.02450028620660305,
-0.014050226658582687,
-0.01328054815530777,
-0.07320321351289749,
0.020197341218590736,
-0.0108... | 0.081507 |
time ranges. ## Other common issues The following issues don't produce specific error messages but are commonly encountered. ### Node graph not displaying \*\*Cause:\*\* The node graph visualization doesn't appear above the trace view. \*\*Solution:\*\* 1. Verify that \*\*Node graph\*\* is enabled in the Tempo data sou... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.049219172447919846,
-0.0058151655830442905,
0.012573805637657642,
0.07832077890634537,
0.041438985615968704,
0.011916535906493664,
0.009833085350692272,
-0.020886799320578575,
-0.07215970009565353,
-0.0020449485164135695,
0.017789509147405624,
-0.12306711077690125,
0.03852340579032898,
... | 0.045433 |
Prometheus metrics from trace data, then create alert rules against the Prometheus data source that stores those metrics. 1. Configure the Tempo [metrics generator](https://grafana.com/docs/tempo//metrics-generator/) (using the `service-graphs`, `span-metrics`, or `local-blocks` processor) to produce metrics from trace... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.08824122697114944,
0.016621572896838188,
-0.013132543303072453,
0.06043240427970886,
-0.008480440825223923,
-0.11245271563529968,
0.0304486732929945,
-0.03972120210528374,
0.010677717626094818,
-0.010236944071948528,
-0.04948921129107475,
-0.11737189441919327,
0.055171798914670944,
-0.0... | 0.15759 |
between the PDC agent and Tempo are dropping long-running connections. 1. For large queries, consider reducing the time range or adding more specific filters. 1. Check if multiple data sources are sharing the same PDC agent, which may cause resource contention. ### PDC authentication mismatch \*\*Error message:\*\* `Un... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/troubleshooting/index.md | main | grafana | [
-0.056253258138895035,
-0.0281242486089468,
-0.07871811091899872,
0.017780838534235954,
-0.08647859841585159,
-0.07014928013086319,
-0.07584041357040405,
-0.10945462435483932,
0.016037186607718468,
0.04531567916274071,
-0.0003020745643880218,
-0.10011142492294312,
-0.009427321143448353,
-0... | -0.042687 |
# TraceQL query examples Use these TraceQL queries in Grafana \*\*Explore\*\* with a Tempo data source. Adjust service names, routes, and attribute values to match your environment. These examples use [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/general/trace/). If your instrumentati... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/traceql-query-examples.md | main | grafana | [
-0.08935047686100006,
-0.011425208300352097,
-0.03753194957971573,
0.0990196242928505,
-0.061581216752529144,
-0.08280277252197266,
0.011672744527459145,
-0.06154061108827591,
0.02339123748242855,
-0.03984896093606949,
0.020202090963721275,
-0.1552630066871643,
-0.005704459734261036,
-0.08... | 0.114226 |
- Query editor modes and options - [Service Graph and Service Graph view](../service-graph/) - Visualize service dependencies | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/traceql-query-examples.md | main | grafana | [
-0.0712258517742157,
-0.038175906985998154,
-0.02466740645468235,
0.01602933369576931,
-0.00676680076867342,
0.0023424059618264437,
0.030388135462999344,
-0.020664112642407417,
-0.026208283379673958,
0.042148321866989136,
0.0143428985029459,
0.030222952365875244,
0.03275094926357269,
0.051... | 0.073857 |
# Search traces using the query builder The \*\*Search\*\* query builder lets you create TraceQL queries using drop-down lists and text fields instead of writing syntax directly. Each selection you make generates a TraceQL query behind the scenes. You can view the generated query and copy it to the [TraceQL editor](../... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/traceql-search.md | main | grafana | [
-0.04014639928936958,
-0.014335238374769688,
-0.016651522368192673,
0.12098069489002228,
-0.025670349597930908,
-0.021198157221078873,
0.02579202689230442,
-0.05768358334898949,
-0.0033919864799827337,
-0.018766334280371666,
0.02444719336926937,
-0.08921845257282257,
0.03396989777684212,
-... | 0.068885 |
# Write TraceQL queries with the editor Use the \*\*TraceQL\*\* editor when you need structural queries across parent and child spans, aggregations, or other features that the [Search query builder](../traceql-search/) doesn't support. TraceQL queries follow the pattern `{ conditions } | pipeline`. Refer to [Construct ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/traceql-editor.md | main | grafana | [
-0.07926809042692184,
-0.020290851593017578,
-0.023048225790262222,
0.09902586787939072,
-0.08075150847434998,
-0.05203475430607796,
0.000011049912245653104,
-0.02692030742764473,
-0.025127138942480087,
0.0016407333314418793,
-0.02485724911093712,
-0.10160687565803528,
0.06544965505599976,
... | 0.031317 |
# Query tracing data The Tempo data source's query editor helps you query and display traces from Tempo in [Explore](https://grafana.com/docs/grafana//explore/). The queries use [TraceQL](https://grafana.com/docs/tempo/latest/traceql), the query language designed specifically for tracing. For general documentation on q... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/_index.md | main | grafana | [
-0.08414041996002197,
-0.012963000684976578,
-0.05775200203061104,
0.08994679152965546,
-0.06432068347930908,
-0.032091476023197174,
0.04520527645945549,
-0.06010080873966217,
0.004052695818245411,
-0.00722820358350873,
0.0015546375652775168,
-0.09392210841178894,
-0.013026736676692963,
-0... | 0.094603 |
more information, refer to [Service Graph and Service Graph view](https://grafana.com/docs/grafana//datasources/tempo/service-graph/).  ## Understand search behavior Tempo search is non-determini... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/_index.md | main | grafana | [
-0.13421083986759186,
0.009647347033023834,
-0.04078337550163269,
0.07108411192893982,
-0.06225396692752838,
-0.07271534949541092,
-0.04987547919154167,
-0.046639807522296906,
0.02715146541595459,
-0.004103780724108219,
-0.021157626062631607,
-0.021985910832881927,
0.0036472403444349766,
-... | 0.093651 |
the query block. ### Use query history and query inspector \*\*Explore\*\* provides a history of all queries you've used within a data source and an inspector that lets you view stats, inspect queries, view JSON, and general information for your data source queries. For more information, refer to the [Query inspector i... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/query-editor/_index.md | main | grafana | [
-0.142107293009758,
0.0024138952139765024,
-0.12591534852981567,
0.03162628412246704,
-0.07124049961566925,
-0.06275255233049393,
-0.060710661113262177,
-0.021227866411209106,
-0.027925580739974976,
0.003751084441319108,
-0.003458630293607712,
-0.01873728446662426,
-0.006190691143274307,
-... | 0.118033 |
# Trace correlations You can use Grafana [correlations](https://grafana.com/docs/grafana//administration/correlations/) to embed interactive correlation links in your trace view to jump from spans to related logs, metrics, profiles, or external systems. This guide explains how to configure and manage Trace correlations... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/trace-correlations.md | main | grafana | [
-0.0637432187795639,
-0.10285530984401703,
-0.06938538700342178,
0.07377952337265015,
0.004592119250446558,
-0.0030375015921890736,
-0.008256710134446621,
-0.05566538870334625,
-0.005873587913811207,
-0.04626314714550972,
-0.018061257898807526,
-0.07397190481424332,
0.022324394434690475,
0... | 0.067438 |
you started. ### Example 1: Trace to logs by service name and trace identifier In this example, you configure trace to logs by service name and a trace identifier. 1. On step 1, add a new correlation with the label \*\*Logs for this service and trace\*\* and an optional description. {{< figure src="/media/docs/tempo/sc... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/trace-correlations.md | main | grafana | [
-0.08871416002511978,
-0.061042420566082,
-0.03154624253511429,
0.04408896341919899,
0.03474246710538864,
-0.04346270114183426,
0.04693351686000824,
-0.03794781118631363,
0.011639847420156002,
0.02391335926949978,
0.03384365141391754,
-0.055535804480314255,
0.10078614205121994,
0.060479328... | 0.075289 |
# Configure trace to profiles correlation Trace to profiles lets you navigate from a span in a trace directly to profiling data in [Grafana Pyroscope](https://grafana.com/docs/pyroscope//). When configured, a \*\*Profiles for this span\*\* button and an embedded flame graph appear in the span details view. ## Before yo... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-profiles.md | main | grafana | [
-0.07729919999837875,
0.018460750579833984,
-0.09181661158800125,
0.02275371178984642,
-0.004771986044943333,
-0.030538225546479225,
-0.03307562693953514,
-0.006479794159531593,
-0.054007481783628464,
-0.029730187729001045,
-0.0022228711750358343,
-0.09275718778371811,
-0.019235242158174515,... | 0.043354 |
# Provision the Tempo data source You can define and configure the Tempo data source in YAML files as part of the Grafana provisioning system. You can use version control, like Git, to track and manage file changes. Changes can be updated or rolled back as needed. {{< admonition type="note" >}} Provisioning via YAML is... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/provision.md | main | grafana | [
-0.09221701323986053,
0.00890612043440342,
-0.07370653748512268,
0.04248962923884392,
-0.07599103450775146,
-0.03018346056342125,
-0.05507402867078781,
-0.05841914191842079,
-0.04956397786736488,
0.07841962575912476,
0.03064064309000969,
-0.06625194847583771,
-0.025880759581923485,
-0.0451... | 0.070402 |
are trying to clone. 1. [Create a new data source](https://grafana.com/docs/grafana//datasources/tempo/configure-tempo-data-source/#add-a-new-data-source) of the same type you want to clone. 1. Copy all of the settings from the existing provisioned data source into the new data source while replacing the password with ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/provision.md | main | grafana | [
-0.12561462819576263,
-0.007652005180716515,
-0.08415152132511139,
0.016008256003260612,
-0.051017504185438156,
-0.016379281878471375,
-0.03462653607130051,
-0.09914639592170715,
-0.011405127122998238,
0.07821833342313766,
0.01191638596355915,
-0.057446904480457306,
0.07235530763864517,
-0... | -0.057904 |
# Configure trace to metrics correlation Trace to metrics lets you navigate from a span in a trace to metrics in a Prometheus or other metrics data source. When configured, a \*\*Metrics for this span\*\* link appears in the trace view. Trace to metrics works with any Prometheus-compatible data source and doesn't requi... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-metrics.md | main | grafana | [
-0.11270978301763535,
-0.059805989265441895,
-0.0534868985414505,
0.029302317649126053,
-0.060706790536642075,
-0.008372491225600243,
0.002217109315097332,
-0.06041600555181503,
0.02293173409998417,
-0.03979673609137535,
0.013293224386870861,
-0.14076149463653564,
-0.01499340869486332,
0.0... | 0.109542 |
from the \*\*Data source\*\* drop-down. 1. Optional: Choose any tags to use in the query. Click \*\*Add tag\*\* to add a tag mapping. These tags can be used in the custom query with the `${\_\_tags}` variable. This variable interpolates the mapped tags as a list in an appropriate syntax for the data source and only inc... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-metrics.md | main | grafana | [
-0.0821773037314415,
0.0199767854064703,
-0.007988763973116875,
0.07655059546232224,
-0.04400327429175377,
-0.05905269458889961,
0.10363328456878662,
-0.001310919993557036,
-0.007804239634424448,
-0.013941668905317783,
0.0016463882056996226,
-0.07426179945468903,
0.059097833931446075,
-0.0... | 0.007802 |
Link spans to profiling data in Grafana Pyroscope. - [Provision the Tempo data source](https://grafana.com/docs/grafana//datasources/tempo/configure-tempo-data-source/provision/): Configure the Tempo data source using a YAML file. | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-metrics.md | main | grafana | [
-0.07470168173313141,
0.004340049345046282,
-0.0874268040060997,
-0.0014826323604211211,
-0.0432441309094429,
-0.02264200709760189,
-0.05929572507739067,
-0.02726246789097786,
-0.06542695313692093,
-0.0001384942006552592,
0.019633011892437935,
-0.07783225923776627,
-0.042633429169654846,
-... | 0.10895 |
# Additional settings The \*\*Additional settings\*\* section of the Tempo data source settings contains options that most users don't need to change. These settings are collapsed by default. Use the down arrow to expand the \*\*Additional settings\*\* section to view these options. This page covers the following setti... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/additional-settings.md | main | grafana | [
-0.0679226815700531,
0.04332897812128067,
-0.029769202694296837,
0.07969523221254349,
0.0332670584321022,
-0.06342338025569916,
-0.012517723254859447,
-0.050300776958465576,
-0.013910532929003239,
0.007046947255730629,
0.0021982642356306314,
-0.03961997851729393,
-0.009852400980889797,
-0.... | 0.145002 |
to constrain your queries: | Name | Description | | ------------------- | ---------------------------------- | | \*\*Last 30 minutes\*\* | Last 30 minutes of selected range. | | \*\*Last 3 hours\*\* | Last 3 hours of selected range. | | \*\*Last 24 hours\*\* | Last 24 hours of selected range. | | \*\*Last 3 days\*\* | ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/additional-settings.md | main | grafana | [
0.011729605495929718,
0.04128897935152054,
-0.025004692375659943,
0.10659798234701157,
0.03860388696193695,
0.024647830054163933,
0.058508336544036865,
-0.013341841287910938,
-0.020430590957403183,
-0.023466456681489944,
-0.026757320389151573,
-0.1139434278011322,
0.051427774131298065,
-0.... | 0.011937 |
# Configure trace to logs correlation Trace to logs correlation lets you navigate from a span in Tempo directly to the matching logs in Loki, and from a log line in Loki back to its trace in Tempo. When configured, a \*\*Logs for this span\*\* link appears in the trace view and a link to the configured tracing data sou... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs.md | main | grafana | [
-0.09731340408325195,
-0.03952108323574066,
-0.03740856051445007,
0.05220367759466171,
0.0009338475065305829,
-0.014194153249263763,
0.019050732254981995,
-0.06547065079212189,
0.03236977756023407,
-0.01775181107223034,
0.0199831984937191,
-0.08231306821107864,
-0.008207020349800587,
0.005... | 0.105554 |
attribute | Loki label | | ------------------- | ------------------- | | `service.name` | `service\_name` | | `service.namespace` | `service\_namespace` | | `cluster` | `cluster` | | `namespace` | `namespace` | | `pod` | `pod` | | `hostname` | `hostname` | Choose labels with low cardinality. In Loki, every unique combi... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs.md | main | grafana | [
0.01525136735290289,
-0.049068350344896317,
-0.07892812788486481,
0.03337135165929794,
0.007090051658451557,
-0.020549464970827103,
0.08591155707836151,
-0.002628559712320566,
0.08332927525043488,
-0.041995640844106674,
0.04376218467950821,
-0.03958466649055481,
0.05025993660092354,
0.0114... | 0.213104 |
enter a pattern to extract the trace ID from log lines. If you select \*\*Regex in log line\*\*, enter a regular expression with one capture group. The following table shows common patterns: | Log format | Regex | | --------------------------------- | ------------------- | | `traceID=` | `traceID=(\w+)` | | `trace\_id=... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs.md | main | grafana | [
-0.07691673934459686,
0.06219968944787979,
-0.024754026904702187,
0.039169859141111374,
0.06091763824224472,
0.006754858419299126,
0.10081858932971954,
0.011192531324923038,
0.027513012290000916,
-0.06609091907739639,
-0.007225262001156807,
-0.028961172327399254,
-0.005201384890824556,
-0.... | 0.064042 |
Pyroscope. - [Configure the Tempo data source](https://grafana.com/docs/grafana//datasources/tempo/configure-tempo-data-source/): Return to connection, authentication, and streaming settings. | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/configure-trace-to-logs.md | main | grafana | [
-0.10753542929887772,
0.00555521110072732,
-0.15264686942100525,
-0.031108904629945755,
-0.08853870630264282,
-0.015157239511609077,
-0.022925958037376404,
-0.05964008718729019,
-0.039869312196969986,
0.007598872296512127,
0.03248557820916176,
-0.07179873436689377,
-0.05622496455907822,
-0... | 0.127842 |
# Configure the Tempo data source The Tempo data source connects Grafana to your Tempo database and lets you configure features and integrations with other telemetry signals. You can configure the data source using either the data source interface in Grafana or using a configuration file. This page explains how to conn... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/_index.md | main | grafana | [
-0.06397321075201035,
-0.0796450674533844,
-0.11272961646318436,
0.00033279668423347175,
-0.07012351602315903,
-0.02111074887216091,
-0.04550394415855408,
-0.07477881014347076,
-0.02879169024527073,
0.014725672081112862,
0.013141077943146229,
-0.11289134621620178,
-0.0001905999524751678,
-... | 0.099401 |
your environment: | Environment | URL format | Example | | -------------------- | ------------------------------------------ | --------------------------------------------------- | | Self-managed Tempo | `http://:` | `http://tempo:3200` | | Grafana Cloud Traces | `https://tempo-.grafana.net/tempo` | `https://tempo-prod... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/_index.md | main | grafana | [
-0.052371785044670105,
0.017792655155062675,
-0.08185112476348877,
-0.024855466559529305,
0.0028919933829456568,
-0.05395590513944626,
-0.04321667179465294,
-0.05464596673846245,
0.003923329990357161,
-0.0028849132359027863,
0.04536236822605133,
-0.054984599351882935,
-0.06668450683355331,
... | 0.03926 |
they arrive. Enable one or both depending on which query types you use.  When streaming is active, it shows as \*\*Enabled\*\* in \*\*Explore\*\*. To check the status, select Explore in the menu, select your... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/tempo/configure-tempo-data-source/_index.md | main | grafana | [
-0.11400127410888672,
-0.05940283462405205,
-0.07839713245630264,
0.01901465654373169,
-0.03611534833908081,
-0.0069228229112923145,
-0.01515074074268341,
-0.10606852918863297,
0.01639876514673233,
-0.02664952166378498,
0.052001938223838806,
-0.07430776208639145,
-0.013495028018951416,
-0.... | 0.119382 |
# MySQL data source Grafana ships with built-in support for MySQL. You can query and visualize data from MySQL-compatible databases like [MariaDB](https://mariadb.org/) or [Percona Server](https://www.percona.com/). Use this data source to create dashboards, explore SQL data, and monitor MySQL-based workloads in real t... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/_index.md | main | grafana | [
-0.012083252891898155,
-0.08647603541612625,
-0.11409389227628708,
0.0051970393396914005,
-0.08602477610111237,
-0.03472593426704407,
-0.036052048206329346,
-0.010673410259187222,
-0.0116913802921772,
0.1039036437869072,
-0.016888223588466644,
-0.032772891223430634,
0.07031718641519547,
0.... | 0.051752 |
# MySQL alerting You can use Grafana Alerting with MySQL to create alerts based on your MySQL data. This allows you to monitor metrics, detect anomalies, and receive notifications when specific conditions are met. For general information about Grafana Alerting, refer to [Grafana Alerting](https://grafana.com/docs/grafa... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/alerting/index.md | main | grafana | [
-0.005495524499565363,
-0.06220217049121857,
-0.05853843316435814,
0.06002877280116081,
-0.04816680774092674,
-0.050669338554143906,
0.10981304198503494,
0.0047827595844864845,
0.008951123803853989,
0.0057200295850634575,
-0.06256385147571564,
-0.09241152554750443,
0.10677511990070343,
0.0... | 0.070003 |
separate query for alerting with hard coded values. ### Table format not supported Queries using the \*\*Table\*\* format cannot be used for alerting. Set the query format to \*\*Time series\*\* and ensure your query returns a time column. ### Query timeout Complex queries with large datasets may timeout during alert e... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/alerting/index.md | main | grafana | [
0.1030053049325943,
-0.0009976637084037066,
-0.03804199770092964,
0.07463377714157104,
0.04871984198689461,
-0.04344695806503296,
0.11462819576263428,
0.010905306786298752,
0.03230719640851021,
-0.023826729506254196,
0.011669089086353779,
-0.07073939591646194,
0.12322179228067398,
-0.01444... | 0.045006 |
# Configure the MySQL data source This document provides instructions for configuring the MySQL data source and explains available configuration options. For general information on managing data sources refer to [Data source management](https://grafana.com/docs/grafana//administration/data-source-management/). ## Befor... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/configure/_index.md | main | grafana | [
-0.034373462200164795,
-0.05217213183641434,
-0.094391830265522,
-0.0276523157954216,
-0.13721804320812225,
-0.06218203529715538,
-0.06838710606098175,
-0.014606019482016563,
-0.047059908509254456,
0.06637603044509888,
0.012734483927488327,
-0.05818137899041176,
0.06011997535824776,
-0.027... | 0.019582 |
authenticate using a CA certificate. Required for verifying self-signed TLS Certs. Follow the instructions of your CA (Certificate Authority) to download the certificate file. Provide the root certificate under \*\*TLS/SSL Root Certificate\*\* if TLS/SSL mode requires it. - \*\*Skip TLS Verification\*\* - Toggle to ski... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/configure/_index.md | main | grafana | [
-0.004909309092909098,
0.00999050959944725,
-0.04273664951324463,
-0.013872669078409672,
-0.10302732139825821,
-0.024804864078760147,
0.08108041435480118,
0.005738392937928438,
0.0665844976902008,
0.01849217154085636,
0.023059707134962082,
-0.0507790669798851,
0.19835199415683746,
0.089864... | -0.05338 |
can override this setting in a dashboard panel under its data source options. ## Provision the data source You can define and configure the data source in YAML files as part of Grafana's provisioning system. For more information about provisioning, and available configuration options, refer to [Provision Grafana](https... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/configure/_index.md | main | grafana | [
-0.056122440844774246,
-0.020906802266836166,
-0.07565147429704666,
-0.029198763892054558,
-0.12835071980953217,
-0.0759933590888977,
-0.05296552926301956,
-0.03059609793126583,
-0.009211634285748005,
0.09439052641391754,
-0.01551409624516964,
-0.05383962392807007,
0.07273711264133453,
-0.... | -0.02749 |
# MySQL template variables Instead of hard-coding details such as server, application, and sensor names in metric queries, you can use variables. Grafana displays these variables in drop-down select boxes at the top of the dashboard to help you change the data displayed in your dashboard. Grafana refers to such variabl... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/template-variables/index.md | main | grafana | [
-0.059853773564100266,
0.03474144637584686,
-0.1001754030585289,
0.04187178611755371,
-0.1181427612900734,
-0.05784258618950844,
0.02201188914477825,
-0.013226891867816448,
-0.03995271399617195,
0.030606525018811226,
-0.026545781642198563,
-0.11843720823526382,
0.06509240716695786,
-0.0198... | 0.064971 |
$\_\_timeFilter(atimestamp) and hostname in($hostname) ORDER BY atimestamp ASC ``` - \*\*`[[varname]]` syntax\*\* Example with a template variable named `hostname`: ```sql SELECT UNIX\_TIMESTAMP(atimestamp) as time, aint as value, avarchar as metric FROM my\_table WHERE $\_\_timeFilter(atimestamp) and hostname in([[hos... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/template-variables/index.md | main | grafana | [
-0.04218171909451485,
0.04841262102127075,
-0.04834984242916107,
0.058827344328165054,
-0.08839139342308044,
-0.0160488523542881,
0.04189754277467728,
-0.025383176282048225,
0.04442524164915085,
0.05477926507592201,
-0.023336805403232574,
-0.10407204180955887,
-0.0031114749144762754,
-0.02... | 0.00734 |
# Troubleshoot MySQL data source issues This document provides solutions to common issues you may encounter when configuring or using the MySQL data source in Grafana. ## Connection errors These errors occur when Grafana cannot establish or maintain a connection to the MySQL server. ### Unable to connect to the server ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/troubleshooting/index.md | main | grafana | [
-0.04373984411358833,
-0.015106231905519962,
-0.04240758717060089,
-0.043562207370996475,
-0.14170047640800476,
-0.07634742558002472,
-0.08090094476938248,
-0.04260757565498352,
-0.005788174923509359,
0.08941560238599777,
0.009699707850813866,
-0.04908626526594162,
0.06984978914260864,
0.0... | -0.039963 |
access database \*\*Error message:\*\* "Access denied for user 'username'@'host' to database 'dbname'" \*\*Cause:\*\* The authenticated user doesn't have permission to access the specified database. \*\*Solution:\*\* 1. Verify that the database name is correct in the data source configuration. 1. Ensure the user has th... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/troubleshooting/index.md | main | grafana | [
-0.0289144329726696,
-0.03639436513185501,
-0.07023724168539047,
-0.026197116822004318,
-0.08049079775810242,
-0.03023981675505638,
0.013606409542262554,
-0.03534473851323128,
-0.03336096927523613,
0.0789739117026329,
0.03464126214385033,
-0.07030545175075531,
0.0449829027056694,
0.0360727... | -0.02756 |
in backticks: `` `table` ``, `` `select` ``. 1. Verify that template variable syntax is correct: `$variable` or `${variable}`. 1. Test the query directly in a MySQL client to isolate Grafana-specific issues. ### Unknown column in field list \*\*Error message:\*\* "Unknown column 'column\_name' in 'field list'" \*\*Caus... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/troubleshooting/index.md | main | grafana | [
-0.04457984119653702,
0.0030510229989886284,
-0.05522846058011055,
0.017961721867322922,
-0.10420550405979156,
-0.05989236384630203,
-0.006781569216400385,
0.020506206899881363,
-0.018393391743302345,
0.10219480842351913,
0.0334167443215847,
-0.06665032356977463,
0.08634595572948456,
-0.06... | -0.006553 |
but manual queries require backticks. 1. Avoid using reserved words as identifiers when possible. ### An unexpected error happened \*\*Error message:\*\* "An unexpected error happened" \*\*Cause:\*\* A general error occurred that doesn't have a specific error message. \*\*Solution:\*\* 1. Check the Grafana server logs ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/troubleshooting/index.md | main | grafana | [
-0.06840304285287857,
-0.05384839326143265,
-0.03352823853492737,
0.03254460543394089,
-0.147037073969841,
-0.04527483135461807,
-0.03759925439953804,
-0.07065150886774063,
-0.03617141395807266,
0.08147480338811874,
0.00817062333226204,
-0.09930983185768127,
0.10878407955169678,
-0.0350551... | -0.036374 |
# MySQL query editor Grafana’s query editors are unique for each data source. For general information on Grafana query editors, refer to [Query editors](https://grafana.com/docs/grafana//panels-visualizations/query-transform-data/#query-editors). For general information on querying data sources in Grafana, refer to [Qu... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/query-editor/_index.md | main | grafana | [
-0.036378614604473114,
-0.021803254261612892,
-0.07817845791578293,
0.06513338536024094,
-0.09072967618703842,
-0.01899799332022667,
-0.009667611680924892,
-0.026048285886645317,
-0.018460547551512718,
0.04878348857164383,
-0.025467630475759506,
-0.04344384744763374,
0.10777848213911057,
-... | 0.026749 |
order by from the drop-down. Select ascending (`ASC`) or descending (`DESC`) order. - \*\*Limit\*\* - You can add an optional limit on the number of retrieved results. Default is 50. - \*\*Preview\*\* - Toggle for a preview of the SQL query generated by the query builder. Preview is toggled on by default. ## MySQL Code... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/query-editor/_index.md | main | grafana | [
-0.051876094192266464,
-0.0330432690680027,
0.011776570230722427,
0.06590595096349716,
-0.053683310747146606,
0.020462458953261375,
-0.03725437819957733,
0.032588422298431396,
-0.004793700762093067,
0.13607290387153625,
-0.012013896368443966,
0.030018623918294907,
0.05208837613463402,
-0.0... | -0.067541 |
of the currently active time selection as a UNIX timestamp. Example: \_1494410783\_ | | `$\_\_unixEpochTo()` | Replaces the value with the end of the currently active time selection as UNIX timestamp. Example: \_1494497183\_ | | `$\_\_unixEpochNanoFilter(dateColumn)` | Replaces the value with a time range filter using ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/query-editor/_index.md | main | grafana | [
-0.012067546136677265,
0.03247833251953125,
-0.035137712955474854,
0.051225267350673676,
0.07454970479011536,
-0.017258603125810623,
0.04161183908581734,
0.01274014264345169,
0.017239749431610107,
0.015293734148144722,
-0.01599651202559471,
-0.09043905884027481,
-0.015002697706222534,
-0.0... | 0.11101 |
returns the same result as the previous one, but adds support for filtering data using the Grafana time picker. \*\*Example with `$\_\_timeGroup(dateColumn,'5m')` Macro:\*\* ```sql SELECT $\_\_timeGroup(time\_date\_time, '5m') AS time, sum(value\_double) AS sum\_value FROM my\_data WHERE $\_\_timeFilter(time\_date\_tim... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/query-editor/_index.md | main | grafana | [
-0.11904624849557877,
0.01630912907421589,
0.009348906576633453,
0.06520132720470428,
-0.08294487744569778,
-0.009838778525590897,
0.003955906722694635,
-0.021991046145558357,
0.07010151445865631,
-0.002955682808533311,
0.007647546473890543,
-0.11198753863573074,
-0.022137021645903587,
-0.... | -0.034901 |
# MySQL annotations Annotations overlay event data on your dashboard graphs, helping you correlate events with metrics. You can use MySQL as a data source for annotations to display events such as deployments, alerts, or other significant occurrences on your visualizations. For general information about annotations, re... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/annotations/index.md | main | grafana | [
-0.005803575739264488,
0.0042478954419493675,
-0.04039527848362923,
0.011182425543665886,
-0.04958196356892586,
-0.016371237114071846,
0.02097332291305065,
0.014982013031840324,
0.04387369006872177,
0.030186360701918602,
-0.056311722844839096,
-0.12428759038448334,
0.06945900619029999,
0.0... | 0.077688 |
time columns and filter columns to improve query performance. - \*\*Use meaningful text:\*\* Include descriptive information in the `text` column to make annotations useful. - \*\*Organize with tags:\*\* Use consistent tag values to categorize annotations and enable filtering. - \*\*Test queries first:\*\* Verify your ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/mysql/annotations/index.md | main | grafana | [
0.029918670654296875,
0.07617450505495071,
-0.051148176193237305,
0.04059750959277153,
0.01850522682070732,
0.030034959316253662,
0.06955613940954208,
-0.028537021949887276,
0.01632620207965374,
-0.011979395523667336,
-0.008860097266733646,
-0.062104012817144394,
0.002588411560282111,
0.00... | 0.10583 |
# OpenTSDB data source Grafana ships with support for OpenTSDB, an open source time series database built on top of HBase. Use the OpenTSDB data source to visualize metrics, create alerts, and build dashboards from your time series data. ## Supported features The OpenTSDB data source supports the following features: | ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/_index.md | main | grafana | [
-0.06507880985736847,
-0.02035479247570038,
-0.03555246815085411,
0.03835538774728775,
-0.015359281562268734,
-0.029074905440211296,
-0.017213134095072746,
0.031879231333732605,
0.005795650649815798,
-0.010641510598361492,
-0.08112531900405884,
-0.07215751707553864,
0.001809985376894474,
-... | 0.108262 |
# OpenTSDB alerting You can use Grafana Alerting with OpenTSDB to create alerts based on your time series data. This allows you to monitor metrics, detect anomalies, and receive notifications when specific conditions are met. For general information about Grafana Alerting, refer to [Grafana Alerting](https://grafana.co... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/alerting/index.md | main | grafana | [
-0.08716368675231934,
-0.03259279206395149,
-0.05442064255475998,
0.08122207224369049,
-0.03594684228301048,
-0.03505359962582588,
0.05018531531095505,
-0.01691911555826664,
0.04805672913789749,
-0.034406814724206924,
-0.07050314545631409,
-0.08031171560287476,
-0.0196352731436491,
0.00834... | 0.092514 |
When sum is above `100` ## Limitations When using OpenTSDB with Grafana Alerting, be aware of the following limitations. ### Template variables not supported Alert queries can't contain template variables. Grafana evaluates alert rules on the backend without dashboard context, so variables like `$hostname` or `$environ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/alerting/index.md | main | grafana | [
0.016949066892266273,
0.04341146722435951,
-0.02948378212749958,
0.06848272681236267,
0.011204872280359268,
-0.086548812687397,
0.0383191742002964,
-0.002379265846684575,
0.04001660645008087,
-0.0015706339618191123,
-0.08617838472127914,
-0.1038285344839096,
0.0923304557800293,
-0.02388544... | 0.006783 |
# Configure the OpenTSDB data source This document explains how to configure the OpenTSDB data source in Grafana. ## Before you begin Before configuring the OpenTSDB data source, ensure you have: - \*\*Grafana permissions:\*\* Organization administrator role to add data sources. - \*\*OpenTSDB instance:\*\* A running O... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/configure/index.md | main | grafana | [
-0.0749717429280281,
-0.05659555271267891,
-0.08966538310050964,
0.024295099079608917,
-0.09885222464799881,
-0.021090133115649223,
-0.053701434284448624,
-0.03274586424231529,
0.0013416706351563334,
0.03461144492030144,
-0.05990446358919144,
-0.059537701308727264,
0.014174481853842735,
-0... | 0.045654 |
filtering. | | \*\*==2.2\*\* | Adds filter support (literal\_or, wildcard, regexp, and more). Filters replace tags for more flexible queries. | | \*\*==2.3\*\* | Adds explicit tags support for rate calculations and additional filter types. | | \*\*==2.4\*\* | Adds fill policy support for downsampling (none, null, zero,... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/configure/index.md | main | grafana | [
-0.0466814860701561,
0.025486689060926437,
-0.01587020605802536,
0.02744213677942753,
-0.035520657896995544,
-0.09193911403417587,
-0.08290735632181168,
-0.027383549138903618,
-0.00675409147515893,
0.014049282297492027,
-0.06850159913301468,
-0.06213616207242012,
0.03232935816049576,
-0.03... | -0.057919 |
suggest/lookup API calls lookupLimit = 1000 }) } ``` ### Terraform example with basic authentication The following example provisions an OpenTSDB data source with basic authentication: ```hcl resource "grafana\_data\_source" "opentsdb\_auth" { type = "opentsdb" name = "OpenTSDB" url = "http://localhost:4242" basic\_aut... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/configure/index.md | main | grafana | [
-0.13598117232322693,
0.02706705965101719,
-0.035959504544734955,
0.00024359862436540425,
-0.05946885794401169,
-0.08504220843315125,
-0.046789247542619705,
-0.027490368112921715,
0.0036521446891129017,
0.07274719327688217,
-0.043464429676532745,
-0.06567814946174622,
0.039235301315784454,
... | 0.010726 |
# OpenTSDB template variables Instead of hard-coding server, application, and sensor names in your metric queries, you can use template variables. Variables appear as drop-down menus at the top of the dashboard, making it easy to change the data being displayed without editing queries. For an introduction to template v... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/template-variables/index.md | main | grafana | [
-0.029340889304876328,
0.03654932975769043,
-0.06789346039295197,
0.07234879583120346,
-0.09887871891260147,
-0.016107827425003052,
-0.0056310691870749,
0.03839399665594101,
0.026975145563483238,
-0.00478702737018466,
-0.06737761199474335,
-0.08988945186138153,
0.039366383105516434,
-0.042... | 0.030211 |
host, env=$env, datacenter=$dc)` | Returns host values filtered by both `env` and `datacenter`. | | `tag\_values(app.requests, endpoint, service=$service)` | Returns endpoint values for the selected service. | ### Create cascading filters To create a hierarchy of dependent variables: 1. \*\*Create the parent variable:\... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/template-variables/index.md | main | grafana | [
0.026568206027150154,
0.004826479125767946,
-0.06268677115440369,
0.061906710267066956,
0.010056552477180958,
-0.09937969595193863,
0.033208560198545456,
-0.03598079830408096,
-0.017484258860349655,
0.08961453288793564,
-0.022908451035618782,
-0.13183067739009857,
0.02591455541551113,
-0.0... | -0.011148 |
# Troubleshoot OpenTSDB data source issues This document provides solutions to common issues you may encounter when configuring or using the OpenTSDB data source. For configuration instructions, refer to [Configure the OpenTSDB data source](https://grafana.com/docs/grafana//datasources/opentsdb/configure/). ## Connecti... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/troubleshooting/index.md | main | grafana | [
-0.06344049423933029,
0.0197895634919405,
-0.05972724035382271,
0.03552603721618652,
-0.0735853835940361,
-0.07185064256191254,
-0.09987403452396393,
-0.04272736608982086,
0.004939832724630833,
0.048884350806474686,
-0.017546044662594795,
-0.040083546191453934,
0.030471136793494225,
-0.032... | -0.042158 |
don't populate \*\*Symptoms:\*\* - Template variable drop-down menus are empty - \*\*Preview of values\*\* shows no results \*\*Solutions:\*\* 1. Enable real-time metadata tracking in OpenTSDB by setting `tsd.core.meta.enable\_realtime\_ts` to `true` in your OpenTSDB configuration. 1. Sync existing metadata by running ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/troubleshooting/index.md | main | grafana | [
-0.06207575649023056,
0.021383564919233322,
-0.03999800607562065,
0.05565011501312256,
-0.05581818148493767,
-0.07612266391515732,
-0.04089108109474182,
0.005797745194286108,
0.003971634432673454,
0.055107481777668,
-0.04060479253530502,
-0.08192498981952667,
0.02048361301422119,
-0.029045... | -0.009241 |
# OpenTSDB query editor The query editor allows you to build OpenTSDB queries visually. The available options depend on the OpenTSDB version you configured for the data source. ## Access the query editor The OpenTSDB query editor is located on the [Explore](https://grafana.com/docs/grafana//explore/) page. You can also... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/query-editor/index.md | main | grafana | [
-0.03262358903884888,
-0.014241121709346771,
-0.08414559066295624,
0.07303489744663239,
-0.10040507465600967,
-0.013196430169045925,
-0.015781452879309654,
0.023664087057113647,
0.05482541769742966,
0.008412095718085766,
-0.046570662409067154,
-0.07888477295637131,
0.02665424533188343,
-0.... | 0.029192 |
time series are returned for each unique value. | ### Add, edit, and remove filters To manage filters: 1. Click the \*\*+\*\* button next to "Filters" to add a new filter. 1. Configure the filter fields (Key, Type, Filter, Group by). 1. Click \*\*add filter\*\* to apply the filter. 1. To edit an existing filter, click ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/query-editor/index.md | main | grafana | [
-0.04667496308684349,
-0.04579155147075653,
0.03355715796351433,
0.0830223485827446,
-0.08701465278863907,
0.058941200375556946,
0.06121169403195381,
-0.08190831542015076,
0.028769899159669876,
-0.05988328903913498,
-0.048701416701078415,
-0.07336624711751938,
-0.019644474610686302,
-0.039... | -0.019425 |
Counter is enabled) The value the counter resets to after wrapping. Default: `0`. | | \*\*Explicit tags\*\* | (Version 2.3+) Toggle to require all specified tags to exist on matching time series. | ### When to use rate calculation Enable \*\*Rate\*\* when your metric is a continuously increasing counter, such as: - Net... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/query-editor/index.md | main | grafana | [
-0.03132138401269913,
-0.07046867161989212,
-0.08776404708623886,
0.08476731926202774,
-0.1030907928943634,
-0.021544743329286575,
-0.005156461149454117,
0.021422581747174263,
0.08403243124485016,
0.013422096148133278,
-0.026599979028105736,
-0.05249281972646713,
0.022885559126734734,
-0.0... | 0.061378 |
`null` when you want graphs to show breaks at missing data points. - Use `zero` when missing data should be interpreted as zero (for example, no requests during a period). - Use `nan` when you need missing values to propagate through calculations. ## Autocomplete suggestions The query editor provides autocomplete sugge... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/query-editor/index.md | main | grafana | [
-0.07494562119245529,
0.03169594332575798,
-0.018845833837985992,
0.05720068886876106,
-0.029227260500192642,
0.009829147718846798,
0.03740309551358223,
0.05734897777438164,
-0.009918425232172012,
-0.026360660791397095,
0.02843676693737507,
-0.17054954171180725,
0.07020892947912216,
-0.019... | 0.047317 |
with zero values. ### Compare environments with filters | Field | Value | | ------------ | --------------------- | | Metric | `app.errors.count` | | Aggregator | `sum` | | Filter Key | `env` | | Filter Type | `literal\_or` | | Filter Value | `staging\|production` | | Group by | enabled | This query shows error counts f... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/query-editor/index.md | main | grafana | [
0.08384684473276138,
0.005648371297866106,
-0.04204936325550079,
0.10482317209243774,
-0.02429119125008583,
-0.07525824755430222,
0.02769768238067627,
-0.01675393618643284,
-0.02116750180721283,
0.036981288343667984,
0.01945069245994091,
-0.16401070356369019,
0.04121099039912224,
-0.040055... | 0.014364 |
# OpenTSDB annotations Annotations allow you to overlay event information on graphs, providing context for metric changes. The OpenTSDB data source supports both metric-specific annotations and global annotations stored in OpenTSDB. For general information about annotations in Grafana, refer to [Annotate visualizations... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/annotations/index.md | main | grafana | [
-0.02795276790857315,
0.017160048708319664,
-0.06217106059193611,
0.013819608837366104,
-0.0027395435608923435,
-0.004981874488294125,
-0.036036644130945206,
0.028688302263617516,
0.06111542135477066,
-0.004639359191060066,
-0.0654776319861412,
-0.06423328816890717,
-0.019904745742678642,
... | 0.124499 |
"Deployments" annotation query for `deploy.\*` metrics. 1. Add an "Incidents" annotation query for `events.incident`. 1. Add a "Maintenance" annotation query with global annotations enabled. This allows you to see how deployments, incidents, and maintenance windows relate to your metric data. ## How annotations appear ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/annotations/index.md | main | grafana | [
-0.029240809381008148,
0.04252057150006294,
0.0199838075786829,
0.02680416777729988,
0.01648489385843277,
-0.0013668615138158202,
0.04080190882086754,
0.005604364909231663,
0.04968611150979996,
0.0014027144061401486,
-0.07780832797288895,
-0.07571732252836227,
-0.017607543617486954,
-0.006... | 0.112364 |
the `description` field is populated when creating annotations in OpenTSDB. Grafana displays the `description` field as the annotation text. ## Next steps - [Build queries](https://grafana.com/docs/grafana//datasources/opentsdb/query-editor/) to visualize metrics alongside annotations. - [Use template variables](https:... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/opentsdb/annotations/index.md | main | grafana | [
-0.0441293828189373,
0.015950320288538933,
-0.05586154758930206,
0.03438979387283325,
-0.03578004613518715,
-0.042197342962026596,
0.012248046696186066,
0.02470237948000431,
0.06026801839470863,
-0.028458943590521812,
-0.08529127389192581,
-0.13249866664409637,
0.01195447240024805,
0.01689... | 0.094282 |
# Configure the Grafana Pyroscope data source The Pyroscope data source sets how Grafana connects to your Pyroscope database. You can configure the data source using either the data source interface in Grafana or using a configuration file. This page explains how to set up and enable the data source capabilities using ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/configure-pyroscope-data-source.md | main | grafana | [
-0.041376788169145584,
-0.04957445338368416,
-0.1304396241903305,
-0.062464140355587006,
-0.10199330002069473,
-0.0408184640109539,
-0.03945937380194664,
-0.030584469437599182,
-0.06401115655899048,
0.06814582645893097,
-0.0003855530812870711,
-0.044009868055582047,
0.010426835156977177,
-... | -0.009323 |
layer of security when working with Pyroscope. For additional information on setting up TLS encryption with Pyroscope, refer to [Pyroscope configuration](https://grafana.com/docs/pyroscope//configure-server/reference-configuration-parameters/). {{< /admonition >}} [//]: # 'Shared content for authentication section proc... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/configure-pyroscope-data-source.md | main | grafana | [
-0.16005182266235352,
0.07272665202617645,
-0.1277928203344345,
-0.038688089698553085,
-0.11663679778575897,
-0.09903617203235626,
-0.028214136138558388,
-0.056159451603889465,
-0.021144112572073936,
0.056641802191734314,
-0.005138748791068792,
-0.033593762665987015,
-0.019322507083415985,
... | 0.013617 |
# Query profile data You can query your profile data using the open source Grafana Profiles Drilldown app or the built-in Grafana Pyroscope data source query editor. - Profiles Drilldown provides a queryless experience for inspecting your profiling data with opinionated workflows to assist your investigation. - Data so... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/query-profile-data.md | main | grafana | [
-0.03690607473254204,
0.02258462645113468,
-0.09832422435283661,
0.033278755843639374,
-0.026135601103305817,
-0.029799576848745346,
-0.014012623578310013,
0.019705183804035187,
-0.08095067739486694,
-0.028088970109820366,
-0.04222782701253891,
-0.03585049882531166,
0.006815491244196892,
0... | 0.073138 |
set a positive number in the \*\*Limit\*\* input to limit the maximum number of time series returned by the data source. The series returned are always ordered by descending value for the total aggregated data over the time period. ### Profiles query results Profiles can be visualized in a flame graph. Refer to the [Fl... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/query-profile-data.md | main | grafana | [
-0.09790383279323578,
0.028408963233232498,
-0.0637800544500351,
-0.0074854702688753605,
-0.09185643494129181,
-0.029614325612783432,
-0.009186675772070885,
0.014501423574984074,
0.018364345654845238,
-0.005324307829141617,
-0.051817700266838074,
-0.035313911736011505,
0.009251692332327366,
... | 0.058159 |
# Configure Trace to profiles Trace to profiles lets you navigate from a trace span directly to the profiling data for that span. You configure the integration in the Tempo data source, which connects your tracing data in Tempo with your profiling data in Pyroscope. {{< admonition type="note" >}} Your application must ... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/configure-traces-to-profiles.md | main | grafana | [
-0.0889502465724945,
0.017603805288672447,
-0.08802659064531326,
0.013730810023844242,
-0.02465967833995819,
-0.026892760768532753,
0.008349351584911346,
0.012167848646640778,
-0.05753945931792259,
-0.01277310773730278,
0.004231405444443226,
-0.07966609299182892,
-0.02487625554203987,
-0.0... | 0.051948 |
# Grafana Pyroscope data source Grafana Pyroscope is a horizontally scalable, highly available, multi-tenant, OSS, continuous profiling aggregation system. Add a Pyroscope data source to query your profiles in [Explore](https://grafana.com/docs/grafana//explore/). Refer to [Introduction to Pyroscope](https://grafana.co... | https://github.com/grafana/grafana/blob/main//docs/sources/datasources/pyroscope/_index.md | main | grafana | [
-0.07658973336219788,
-0.0289863683283329,
-0.1698550283908844,
-0.0057084145955741405,
-0.058156970888376236,
-0.07238474488258362,
-0.022699318826198578,
0.05894394963979721,
-0.10154937207698822,
0.005166895687580109,
-0.013166140764951706,
-0.05097689852118492,
0.014356154948472977,
0.... | 0.080461 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.