-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Loki support to Telegraf interface #4407
Comments
moved to #4407, please open future plugin tickets in this repository |
Thank, I will. Also, there are several ways to authenticate to Loki, many use Nginx and basic auth, but a bearer token can be used as well: Bearer Token
Basic Auth
|
One more comment. It may be enough, in the short run, to provide a custom configuration textbox in the outputs section of the configuration, that writes the appropriate place. |
Although I'm not involved in development of this plugin, free text unvalidated input doesn't meet the bar (https://docs.opnsense.org/development/guidelines/basics.html#safeguard-user-input) |
Its not that hard, do you want to try it on your own? |
Important notices
Is your feature request related to a problem? Please describe.
Getting metrics/logs into Loki is a pain. We can write our own configuration file for Telegraf, but that
is probematic and goes against the OpnSense way.
Describe the solution you like
Add Loki support to the Telegraf plugin, and ensure it has options to include the Loki bearer_token so that
it is secure.
Describe alternatives you considered
Writing a custom Telegraf configuration file and inserting that into the OpnSense directly. Its probably not a stable way to go. Other solution is to create a Fluent-bit package (I created a separate feature request for this).
Additional context
Loki is lightweight and powerful on its own. It provides a general and scalable way to monitor both logs and metrics. Its worthwhile to have Loki support inside of OpnSense.
The text was updated successfully, but these errors were encountered: