Prometheus - the new $__rate_interval variable adds some logic that should make using the rate function in Grafana much easier (PR here).
For 7.0, we announced that we would be deprecating multi-org support. In this release, we removed the deprecation notice as we are going to keep multi-org support (got lots of feedback that it is an essential feature for many).
Other releases:
Azure Data Explorer 3.1: we released a new version with lots of improvements to the visual query builder. Hoping to reuse a lot of the work on the visual quer builder on other data sources.
This is a short release to sync with ObservabilityCon (also called CDD - Conference Driven Development). The release contains features that will be demoed at the conference (hint: tracing and Explore - see Exemplars design doc below).
Beta on October 14th. Full release around 1-2 weeks after that.
Grafana community call on plugins signing
Marcus Olsson organized a community call on a hot topic for the plugins developers - plugins signing. We plan to enforce that all Grafana plugins have to be signed (a security measure to make sure that plugins haven't been tampered with). The session was recorded.
Design docs
As the 7.3 release is a special, short release, there is a lot of work underway that is aimed for the 7.4 release. Here are some of the design docs that have been written or are being written (and more coming soon):
> In this release, we removed the deprecation notice as we are going to keep
> multi-org support (got lots of feedback that it is an essential feature for
> many).
>
> Other releases:
>
> we released a new version with lots of improvements to the visual query
> builder. Hoping to reuse a lot of the work on the visual quer builder on
> other data sources.
> (also
> called CDD - Conference Driven Development). The release contains features
> that will be demoed at the conference (hint: tracing and Explore - see
> Exemplars design doc below).
> - Beta on October 14th. Full release around 1-2 weeks after that.
>
> *Grafana community call on plugins signing*
>
> Marcus Olsson organized a community call on a hot topic for the plugins
> developers - plugins signing. We plan to enforce that all Grafana plugins
> have to be signed
>
> As the 7.3 release is a special, short release, there is a lot of work
> underway that is aimed for the 7.4 release. Here are some of the design
> docs that have been written or are being written (and more coming soon):
>
Do you expect the pull request on the Prometheus side to be merged on
time? I'd like to at least make sure that the API changes in the PR is
accepted before the implementation in grafana and won't change.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Grafana Developers, David Kaltschmidt, Zoltán Bedi, Andrej Ocenas
Hi Julien,
As far as I know, we're not expecting the PR on the Prometheus side to be merged by then and we will hide the exemplar code in Grafana behind a feature flag to make sure we don't expose something that would break for users at a later stage. But David K, Zoltan and Andrej know more about this than me.
/Daniel
Andrej Ocenas
unread,
Sep 28, 2020, 3:08:19 PM9/28/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Grafana Developers
Will just confirm what Daniel said, the hard deadline for the ObservabilityCon is for a demo so the code won't be public at the time and as long as we can demo on a prometheus branch that's ok.