Comments (6)
Hey @zarbis, sorry for the inconvenience and thanks for reporting the issue.
It seems there is some issue with applying the otlp_config
set in the global limits_config
, i.e. in the overall Loki config file.
It is working fine as expected when set as per tenant config. While I get this fixed, can you please give it a try with the per-tenant config and use that to avoid getting blocked? I will update here when the fix gets merged.
from loki.
@zarbis, updating your configuration is only one part of the implementation, how are you Attaching the structured metatdata to your log lines?
from loki.
@JStickler I expected it to be ingested by OTLP endpoint naturally due to how it's documented:
Structured Metadata: Anything which can’t be stored in Index labels and LogLine would be stored as Structured Metadata.
from loki.
So you're using the OpenTelemetry Collector, which means you must use the otlphttp exporter, which does not support structured metadata.
The docs need to be updated, as we have two OLTP solutions.
from loki.
Indeed I do. The entire Ingesting logs to Loki using OpenTelemetry Collector doc reads like:
- run
otlphttp
exporter in your OTEL Collector - customize
otlp_config
in Loki (optional)
If otlphttp
indeed is incompatible with structured metadata, why does the entire doc is literally the opposite story? Sounds really confusing...
Just in case, this is relevant part of my Collector config (I run entire LGTM stack through it so showing only logs part of it):
config:
receivers:
otlp:
protocols:
http: ...
exporters:
otlphttp/loki:
endpoint: http://loki-gateway/otlp
auth: ...
sending_queue: ...
loki:
endpoint: http://loki-gateway/loki/api/v1/push
auth: ...
sending_queue: ...
service:
pipelines:
logs:
receivers:
- otlp
processors:
- memory_limiter
- attributes/loki
- resource/loki
- batch
exporters:
- debug/normal
# - otlphttp/loki
- loki
I've tried running otlphttp/loki
while also disabling attributes/loki
and resource/loki
since I supposed they won't be needed in native OTLP mode.
from loki.
@sandeepsukhani I've moved otlp_config
under runtimeConfig.overrides.<org>
and it kinda works, but not really:
otlp_config:
resource_attributes:
attributes_config:
- action: drop
attributes:
- k8s.pod.name
- k8s.deployment.name
log_attributes:
- action: drop
regex: .*
scope_attributes:
- action: drop
regex: .*
log_attributes
are dropped, scope_attributes
I've had none to begin with, but resource_attributes
are still present.
I'm not sure whether the difference in different treatment of resource_attributes
and other ones, or regex
vs attributes
list, but labels I've tried to drop are still there:
logcli --org-id <org> series --from="$(date --utc --iso-8601=seconds --date='5 minutes ago')" --analyze-labels '{}'
2024/04/30 21:08:26 http://localhost:3100/loki/api/v1/series?end=1714500506642625448&match=%7B%7D&start=1714500206000000000
Total Streams: 1653
Unique Labels: 8
Label Name Unique Values Found In Streams
k8s_pod_name 1608 1626
k8s_deployment_name 268 745
k8s_namespace_name 40 1626
__stream_shard__ 5 23
exporter 1 21
service_name 1 1653
from loki.
Related Issues (20)
- [Helm] Loki 3.0 helm chart distributed mode doesn't work for ingress without gateway HOT 1
- Helm chart is using wrong image tag and proxy config for GEL in SSD mode
- logcli warning - "CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned" HOT 2
- Method to pretty-print duration from seconds or milliseconds
- lambda-promtail dlq - which one to use Asynchronous invocation or Destinations ? HOT 3
- Storage resizing doesn't work with SingleBinary deployment. HOT 1
- Add time() function for querying timestamp HOT 2
- Switch enable_alertmanager_v2 default to true HOT 1
- Helm Chart Enterprise Gateway Fails to Start in SSD
- `replace: '{{ .Value | urldecode }}'` doesn't decode a value (it doesn't work) HOT 2
- 88888888888888
- Promtail 2.2.1 - oom issue
- Unable to disable stream sharding via CLI HOT 1
- Ingress traffic rejected by NetworkPolicy in Loki chart 6.5.0 (3.0.0)
- Loki chart fails to render proper YAML when add more than one extra manifest
- Loki helm chart version upgrade from 5.44.4 to 6.5.0 issues in Single Binary deployment mode. HOT 10
- Mismatch in count of OTel attributes to index and default label limit HOT 2
- Parse sent data with raw http request error HOT 2
- Add more functions to LogQL HOT 1
- GCS service_account cannot authenticate HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from loki.