-
Notifications
You must be signed in to change notification settings - Fork 2
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
Undefined field handling #44
Comments
We'll take a look @vrelk-net and get back. |
I have the same problem. It seems that the data pulled from Parseable is incorrectly mapped for use in Grafana. This makes this plugin quite unusable if not every log has the same data fields. |
I have the same problem |
Hey @dennisvanderweide @erwinschaap - thank you for the feedback. We'll get back with a proposal to address this. |
We're working on a fix here #45 Should be available in the next release very soon |
I'm unsure if this is the datasource plugin, or grafana causing this issue.
If you have some records that are missing a field, the key->value associations get shifted.
In my example, I am parsing NGINX web logs, and added the
city
field to the geoip data, so older logs don't contain it.The query I'm using is
SELECT COUNT(*) as 'count', city, isocode, latitude, longitude FROM nginx WHERE "__log.tag" IN ($log_type) AND "__log.hostname" = '$log_src' AND site_name = '$site_name' GROUP BY city, isocode, latitude, longitude;
Query inspector data for both: https://gist.github.com/vrelk-net/3b7bc41045a6e8673cf1fcb8b647b300
When the timespan includes mostly data without the
city
field, it disappears from the table columns, but for the records that do have it, it shifts the data over 1 column, and leaves you with a new numbered column at the end.Last 12 hours:
Last 1 hour:
Grafana version: Grafana v11.0.0-169084
Parseable plugin version: 1.2.0
The text was updated successfully, but these errors were encountered: