You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Pelias logger can only log text. If a user of Pelias wants to log metrics somehow, they have to aggregate those log files and define metrics based on patterns within those log files.
This isn't ideal because the pattern matching is often very tough to get right and debug, it requires more services being run as part of a Pelias setup, and there is no indication in the Pelias code that a seemingly unimportant log line might actually be used to drive a critical metric.
First class support for logging metrics directly, through a configurable backend, should be added. statsd is an obvious backend to support. AWS CloudWatch Metrics might be another one worth supporting.
The text was updated successfully, but these errors were encountered:
I am considering closing this. After #30, we can now send the logs as JSON, which is quite flexible, and doesn't prescribe any particular metrics/observability platform like statsd, prometheus, etc.
If anyone has any ideas of things we could add that would be generally useful, let us know.
One that might be useful is a detailed status page with metrics. This is technically generic but can be used with Prometheus easily, and other systems with some work.
Right now Pelias logger can only log text. If a user of Pelias wants to log metrics somehow, they have to aggregate those log files and define metrics based on patterns within those log files.
This isn't ideal because the pattern matching is often very tough to get right and debug, it requires more services being run as part of a Pelias setup, and there is no indication in the Pelias code that a seemingly unimportant log line might actually be used to drive a critical metric.
First class support for logging metrics directly, through a configurable backend, should be added.
statsd
is an obvious backend to support. AWS CloudWatch Metrics might be another one worth supporting.The text was updated successfully, but these errors were encountered: