The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.

prometheushacktoberfestmetricsmonitoringalertinggrafanagoinfluxdbmysqlpostgresanalyticsdata-visualizationdashboardbusiness-intelligenceelasticsearch

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Piotr Jamróz 9fb8339f87 Elastic: Allow using long/int as date field for alerts (#44027) ... * Use integers for time range filter Previously it was passed as a string which is automatically converted by Elastic to a number only if the field type is "date". For other types (e.g. "long") such conversion doesn't work. In theory "date" could be passed as a formatted string but we don't use it this way and always pass it as a number so it is safe to always pass numbers, not strings. * Fix time_series_query_test * Retrigger build		3 years ago
..
client	Elastic: Allow using long/int as date field for alerts (#44027)	3 years ago
elasticsearch.go	add core plugins thru store (#43085)	4 years ago
elasticsearch_test.go	Plugins: Migrate Elasticsearch to backend plugin SDK (#36132)	4 years ago
models.go	IntervalV2: Use maxDataPoints to calculate correct interval (#39036)	4 years ago
response_parser.go	Chore: Refactor usage of legacy data contracts (#41218)	4 years ago
response_parser_test.go	Elasticsearch: Fix metric names for alert queries (#38546)	4 years ago
time_series_query.go	Elastic: Allow using long/int as date field for alerts (#44027)	3 years ago
time_series_query_test.go	Elastic: Allow using long/int as date field for alerts (#44027)	3 years ago