Skip to content

Releases: oracle/oci-grafana-metrics

List metrics api call fix

04 Jun 20:47
Compare
Choose a tag to compare
  • Now, the number of list metrics call has been set to a maximum of 20 pages
  • The limit is configurable

Support added for variables and auto in window & resolution

06 Apr 23:44
Compare
Choose a tag to compare

New Features

  • Support added for variables and auto in window & resolution
Minor bug fixes
  • Fixed variable duplication in dropdowns
Documentation
  • Instructions added for using variables and auto-config in window and resolution of drop down

Added a region option to getCompartment method

12 Mar 21:45
Compare
Choose a tag to compare

When OCI tenancy is provision with a single region, say 'us-phoenix-1' (home tenancy) and the datasource setting with local has the default regions as 'us-ausburn-1' (in the ~/.oci/config file), the getCompartment does not return the compartment list. The reason being the OCI tenancy has only one tenancy as home and that is not the 'us-phoenix-1' tenancy.

The fix is to set region to the home regions of the OCI tenancy, while making the getCompartment call.

Thanks Jayesh Patel

Support Resource Group

10 Mar 20:31
Compare
Choose a tag to compare

User will be able to use Resource Group.
By Default: No Resource Group

V1.0.7

21 Feb 01:08
Compare
Choose a tag to compare

Fix populated Metric Fields based on the selected region.

Support hard coded values in template variables

23 Jan 19:14
Compare
Choose a tag to compare
  1. Support hard coded values in template variables
  2. Fix bug with filtering compartments by regex in template variable editor

Manual query support. New template variables for dimensions.

25 Nov 20:39
6608581
Compare
Choose a tag to compare
  1. New template variables were added:
  • dimensions() which show all possible dimension keys for selected region, compartment, namespace and metric
  • dimensionOptions() which show all possible dimension values for selected region, compartment, namespace, metric and dimension key.
  1. Dimension value variable can be used as multi-value. Separate queries are generated for each dimension value out of multi-select (but no more than 20 queries)

  2. Custom query is supported. User can type MQL expression manually which will be passed to telemetry instead of selected on the UI metric and dimensions.

  3. Custom template variables were added to the list of dimension value options. Duplicate options are removed.

  4. Options for regions and compartments are cached while query editor is open. Dimension options are cached for the selected region - compartment - namespace - metric.

Fix $namespace and $metric variables

03 Oct 00:39
Compare
Choose a tag to compare

$namespace
In the previous version, the list of namespaces was hardcoded for the $namespace variable.
Today the list of namespaces depends on region and compartment.

$metric
In the previous version, the $metric variable depends on the home region, $compartment and hardcoded $namespace.
Today $metric depends on $region, $compartment and $namespace.

V1.0.3

25 Sep 01:42
Compare
Choose a tag to compare

Fix issue:
Metric name rule creation updated

v1.0.2

27 Mar 01:14
Compare
Choose a tag to compare
  • Shows subcompartments and removes inactive compartments from that list
  • Changes Metric names when rendering on the screen, uses a human readable name for the resource if one is present
  • Shortens ocids to first three and last six characters to save screen real estate