The doc I am referring to: https://docs.wavefront.com/opentelemetry_tracing.html

The current support docs:

• Traces
• Metrics

OpenTelemetry also does support logs: https://opentelemetry.io/docs/reference/specification/logs. Though it is not GA in all SDK yet, worth the effort imo.

Just wondering whether WF team is considering the support of otel log and wavefront log in the near future (let's say in the next 2~4Q)

Hi,

I noticed that the Wavefront query language is now publicly documented here:

https://docs.wavefront.com/query_language_reference.html

I am a contributor to an open source project (github.com/ArpNetworking) and we are considering some features that would require parsing and delegating/augmenting parts of the wavefront query language first through internal components while proxying the rest to wavefront or other sources.

Obviously the language implementation is proprietary; however, I was wondering what usage rights were conveyed through the public documentation?

It seems it should be possible for us to engineer the parser we need from the docs while ensuring any delegation/augmentation remains compatible with the stated interface of those language elements.

Can you offer any guidance on the copyright that Wavefront/VMWare places on the language documentation and specification and ideally whether what I’ve described would be considered fair use?

Thank you,
Ville Koskela

I'm a bit confused by this bit about histogram data:

It makes the most sense if I interpret "Wavefront data format histogram data" to mean multiple samples in the "metrics" data format, i.e. this:

my.metric 10 <t1> <source>
my.metric 20 <t2> <source>
my.metric 20 <t3> <source>

And if I interpret "histogram distribution data format histogram data" to mean data like this:

{!M | !H | !D} [<timestamp>] #<points> <metricValue> [... #<points> <metricValue>]
 <metricName> source=<source> [<pointTagKey1>=<value1> ... <pointTagKeyn>=<valuen>]

With those two assumptions, I think I grok the lines linked above.

I am hesitant about those assumptions because the explanation of "Wavefront data format histogram data" is a link to the page that explains the syntax of both the regular metrics format and the histogram format. The term "Wavefront data format" in the table above those lines also seems intended to identify a specific data format, but again, it links to the same page which describes the syntax for multiple data formats.

Are my assumptions correct? And if so, could I suggest altering the terminology to reduce confusion? I think we should use shorter, more distinct names to distinguish these two concepts. The first type above could be referred to as the "metrics format", correct? That's what it is, albeit expecting many samples within short time ranges. The second type mentioned above could be referred to simply as the "histogram format". In either case, "Wavefront data format" is far too vague and could reasonably be interpreted to mean the superset of all data formats supported by Wavefront, rather than one the format of one specific type of data.

In order to get the server working locally on my M1 apple silicon laptop, I had to run bundle config build.nokogiri --use-system-libraries before running bundle config in step 2 of the readme.

This documentation will describe how to Install WaveFront on IBM Cloud.

Requirements/Prerequisites

You will need an IBM Cloud Pay-As-You-Go or Subscription Account type which can be found here.

Introduction

This docs will describe how to install Wavefront on IBM Cloud. These four steps will be needed as follows:

• Step 1: Provision Kubernetes Cluster
• Step 2: Deploy IBM Cloud Block Storage plug-in
• Step 3: Deploy Wavefront
• Step 4: Verify Installation

So let's get started.

Step 1: Provision Kubernetes Cluster

• Search for Kubernetes and select Kubernetes Service from the list.

You will be redirected to the Kubernetes cluster creation page.

Option A: Create free Kubernetes Engine:

• Price Plan: Free

Enter the cluster name of your choice then click Create to provision the free Kubernetes Cluster.
Please wait for few moments to provision the cluster.

Option B: Create Standard Kubernetes Engine with the following attributes:

• Price Plan: Standard

• Infrastructure: Classic
• Availability: Multi Zone
• Metro: Dallas
• 4 VCPU
• 16 GB RAM
• Worker nodes per zone: 3

Enter the cluster name of your choice then click Create to provision.

Please wait for a few moments to provision the cluster.

Step 2: Deploy IBM Cloud Block Storage plug-in

• Just like in step 1, search for "Block Storage" and Click on it.

• On the Block Storage page click on Create

• Now input the storage details

N.B. Select location as the cluster location.

• Location > Europe > London > LON02

• Billing Method > Monthly > 20 GB

• OS type > Linux

• IOPS > 2 IOPS/GB
  

• Click on “I have agreed to the terms and conditions listed below”.

Now a storage plugin will be available in the dashboard.

Step 3: Deploy Wavefront

• Again Search for Wavefront and Click on it.

You will be taken to the Wavefront deployment page.

In the Wavefront creation page add the details below:

• Target: IBM Kubernetes Service
• Method: Helm chart
• Kubernetes cluster: mycluster-free
• Target namespace: wavefront
• Workspace: wavefront
• Resource group: Default

• Check on “I have agreed to the terms and conditions listed below”.

Click Install to deploy Wavefront.
Please wait for all the process to complete.

Step 4: Verify Installation

• Go to Left Navigation Menu.
• Click on Kubernetes

• Click on your Cluster "mycluster-free".

You will be taken to your clusters overview page where you will see the details of your cluster as well.

• To verify the installation find the Actions..
• Click on it and select Web terminal from the dropdown menu.

Click install, then wait for a couple of minutes to finish the process.

• After completing the installation click on Actions > Web terminal again.

A command line terminal will appear. Type the command below:

Get the list of pods:

kubectl get ns

See if it is running:

kubectl get pod -n wavefront -o wide

The Installation is now done! Enjoy !