Flink Metrics Web UI don't show double value - scala

How can I see double value in flink web ui on dashboard? Maybe, it's possible with something configuration?
When I tried see metrics, like Meter, on dashboard view only the integer part of number. In log I can see double value:
image with dasboard
image with log
Function with metrics: https://github.com/dedkot01/busting-grain/blob/master/grain-generator/src/main/scala/org/dedkot/CounterProcessFunction.scala
File with Flink config: https://github.com/dedkot01/busting-grain/blob/master/local.conf
Full Cloudflow Sbt Project: https://github.com/dedkot01/busting-grain
If u want run project, just use command in project directory sbt pipeline/runLocal
If it's not possible in Flink Web UI, where it's possible? (maybe in Grafana?)

I'm not found answer how this fix in Flink Web UI.
It's good works in Prometheus and Grafana.
Screenshot from Grafana, value 0.2 is displayed correctly.

Related

How to validate Grafana's json file against 3.1 version

I'd like to share my dashboard to Grafana community, but at the upload page the json isn't validated as "Old dashboard JSON format". it isn't clear which part is wrong or missing. How I can upgrade it and what particular part can be missed there?
I have added __inputs part according to https://grafana.com/docs/grafana/v7.5/dashboards/export-import/ , but it is still impossible to upload the file.
P.S. Upload page is specific to my account and is: https://grafana.com/orgs/eljah/dashboards?pg=dashboards&plcmt=usr-upload
Grafana version according to helm chart is:
- name: grafana
repository: https://grafana.github.io/helm-charts
version: 6.1.17
UPD2.
Can't figure out SHare option on the Grafana ui:
It is not clear how did you export dashboard. Please follow doc https://grafana.com/docs/grafana/latest/dashboards/export-import/#exporting-a-dashboard and check "Export for sharing externally". Then you can publish your dashboard on grafana.com portal without any modification of exported json file.
#JanGaraj has explained the right answer.
But I had some problems with finding a control to do a dashboard share. Finally it was fount there:

Skaffold and mutiple Sub Charts

lately I was experimenting with Skaffold with our Helm Charts and I am in little bit in a dilemma that our Helm Chart \ Sub Charts are compatible with Skaffold or not.
Our helm Charts are looking like the following
my-helm-charts
+-charts
+-project1
+-project2
+-project3
+-project4
+-infrastructure_kafka
+-charts
+-kafka
+-zookeeper
+-infrastructure_cassandra
+-infrastructure_elasticsearch
+-Charts.yaml
+-Values.yaml
The reason we choosed to structure the Helm Charts this way, is that if necessary to spin up extra stages for our project.
Now when I want to develop project2 with Google Cloud Code / Skaffold (which I configured correctly and I can start without problem in IntelliJ) I have to start whole my-helm-charts.
That is actually Ok but the problem is, if I use Debug in Kubernetes, I have a feeling Google Cloud Code/Skaffold can really locate the project2 and no debugging occurs.
My feeling is Google Cloud/Skaffold is more oriented to work with following contruct...
project2-helm
+-templates
+-Charts.yaml
+-Values.yaml
My Subcharts contructs starts in Google Cloud Code/Skaffold without any exception but I can't debug, is it possible to achieve want I want with my structure and if yes, how?
Or is it not possible at all...
Thx for answers...
We recently added a feature called config dependencies which might help here. It allows you to create more specific skaffold.yamls and then map them together with a "requires" field:
https://skaffold.dev/docs/design/config/#configuration-dependencies
Once you have the skaffold.yamls created and the right dependency mapping you can run skaffold with the -m flag to choose once slice of your services:
skaffold dev -m project3
Cloud Code support for modules is incoming.
Cloud Code IntelliJ and Cloud Code VS Code recently added preview level support for deploying and debugging modules of a larger application which uses Skaffold. See more here https://cloud.google.com/code/docs/intellij/skaffold-modules

Writing a custom panel plugin for grafana

So I need to write a custom grafana plugin, that works like a funnel. I decided to try and integrate this funnel. Note that it is supposed to get the data from a mysql Server and use it just as a table and not as time series.
So far I read the grafana documentation and then watched this video. In the video a dataFormat is declared in the plugin.json file, however when I checked other working Plugins I didn't see that part written in the plugin.json. The GitHub repos in the video are also gone. I stumbled upon this one though, so then I copied it in the data/plugin directory. I restarted the Server and it was detected but when I tried making a new Panel I got an error saying that it could not be found. I was planning on starting with this example and then working my way towards integrating the funnel part but I can't seem to get it working. Any ideas where to start?
I have reproduced your problem with the same actions and got same error:
Panel plugin not found: myorgid-simple-panel
Just a guess: there is a dependency section in plugin.json file
"dependencies": {
"grafanaVersion": "6.3.x",
"plugins": []
}
My Grafana version is v6.2.5. Isn't this plugin template for future Grafana release (master or developement version)?
I had the same problem with simple-react-panel. To solve it, I ran in the simple-react-panel-master directory :
npm i #grafana/toolkit
npm i #grafana/ui
yarn build
and after I restart grafana service

Kubernetes dashboard exec issue

seeing an odd behaviour with kubernetes-dashboard where the exec option is not taking me into a shell. Instead it shows me a snippet of the dashboard UI in it? Has anyone noticed this? I cannot see any errors in the logs for the same.
I am using the following dashboard yaml:
https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml
It is a problem with the library hterm and Firefox that has been fixed in version 2 of the Dashboard (as it now uses xterm).
You can read more in the github issue 3541.
If you are stick to a Dashboard with the problem, you can work around it using another browser like Chrome.

Error occurred while starting the build in Openshift 3

I have been trying to deploy a war file as an OpenShift project. The server used is jboss-webserver30-tomcat8. I have followed the below steps -
Put ROOT.war file under 'deployments' directory in local system.
Upload the changes in github.
Create a new JAVA project in OpenShift 3 and provide the github repository details.
No automatic build or deployment starts. On manually clicking on Start Build button, the below error is displayed:
An error occurred while starting the build. Reason: Error resolving
ImageStreamTag jboss-webserver30-tomcat8-openshift:1.2 in namespace
openshift: unable to find latest tagged image
Please suggest how can I resolve the error.
This is an issue with how the jboss-webserver30-tomcat8-openshift imagestream is defined in the cluster. We are working to correct this, it is not currently importing the correct set of tags and as a result the 1.2 tag was stopped being a valid tag, when it should be.
However the short term solution is change your buildconfig to reference one of the tags that has a valid image reference associated (e.g. 1.3) instead of the 1.2 tag it is currently referencing. Your build should then be able to run.
A (temporarily) unavailable builder image may be related to this platform upgrade that correlates with the time of posting your question.
Generally, the best place to check for any incident reports or scheduled maintenance is the Status Page (Starter | Pro clusters; it's linked in the web console too, in the upper right corner of the interface).
If this does not seem to be related (e.g. you're not on the starter-us-west-2 cluster where the platform upgrade is taking place) or persists after the maintenance is over, I would encourage you to check the open issues, and log a new bug report, if it's not in the list.
Thank you.