Hawkular Metrics Openshift Containers
by Matt Wringe
I have a new subproject in Hawkular Metrics which sets up creating
components for Openshift/Fabric8
(https://github.com/hawkular/hawkular-metrics/pull/200).
There are 3 main parts
Cassandra: creates a custom seed provider to support
ReplicationControllers in Kubernetes, creates a folder/zip archive which
can be used to generate a Docker image. It may make sense to move the
Cassandra parts out to a separate project.
Hawkular Metrics: creates a folder/zip archive which can be used to
generate a Docker image
Kubernetes: pulls everything together into a single kubernetes
application. Can be used to deploy an application zip into fabric8 (via
drag and drop in the web console or via the maven plugin) or deploy all
the components into Openshift via the kubernetes.json configuration file.
The docker images are not created and deployed to a docker registry as
part of the build, it will just create a folder where you can run the
docker build from. None of the maven docker plugins I looked at seemed
to really work properly, so its still a manual process to do the build
(and push to a registry). Its something which needs to be improved.
The Cassandra service currently only supports adding new nodes to a
cluster and not removing them via the ReplicationController. This is due
to the replication factor being set to be 1 by default (which means when
a node is removed, so is the data it contained).
I believe the docker subproject of hawkular metrics is obsolete and can
be removed
(https://github.com/hawkular/hawkular-metrics/tree/master/docker), but
someone please correct me if I am wrong. It's scripts are referring to
the console which no longer exists as part of the project.
- Matt
1 year, 3 months
Tenant Id - Not Part of URL
by Stefan Negrea
Hello Everybody,
I've been working on a PR for the upcoming Hawkular Metrics release that will remove the tenant id from the end-point URLs. The tenant id will be moved to either a header parameter or a query parameter. The query parameter is in place for cases (such as curl) where setting a header is not possible, difficult, or inconvenient.
Here is an example of the change:
Existing URL:
/{tenantId}/gauge/{metricId}/data
New URL:
/gauge/{metricId}/data
Tenant id set via:
1) header - tenantId
2) query parameter - tenantId
There are two exceptions to this rule, /tenants and /db/{tenantid}/series. The /tenants end-point will be changed into something different in the upcoming releases since it is mostly a management type API that does not belong in the same place with the regular metrics endpoint. And /db/{tenantid}/series end-point is needed in this exact format for compatibility with Influxdb compatible services.
Now, to the merits of this change. The tenant id is volatile, can change any time, and changes to it should be expected; but the rest of the URL is fixed. The second issue is that the tenant id is a security concern. So we were limited in design choices since a security concern was leaking as part of the URL.
So removing the tenant id from the URL will give us permanent & consistent addresses for resources (metrics and metric data points). And we will gain a lot of flexibility on the security side. In the future, users could authenticate with a user/pass combo and the backend would transform that into a tenant id to be used on the request. If the same user later decides to use a tenant id to pass along the request, the URL of the resources would not change. Another expectation is that tenant id is not sufficient, it is typically a combo of id + secret; so we would have resorted to a header or query param for the second piece of information (the secret).
This change will give us the flexibility to adjust the security model (the meaning of tenant ids and ways to validate them) without compromising the URL structure. This will help Hawkular Metrics as it gets integrated into more and more projects and products.
Here are the links to the JIRA and the PR for this change:
https://github.com/hawkular/hawkular-metrics/pull/202
https://issues.jboss.org/browse/HWKMETRICS-68
Thank you,
Stefan Negrea
Software Engineer
1 year, 3 months
New and noteworthy in hawkular-parent 25
by Peter Palaga
Hi *,
hawkular-parent 25 brings the following:
* srcdeps-maven-plugin 0.0.5
* meets the promisses falsely done for 0.0.4:
* less console output
* built without tests
* wildfly-maven-plugin 1.1.0.Alpha4
I have sent PRs to all components repos.
Thanks,
Peter
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
1 year, 3 months
Ability to group by datapoint tag in Grafana
by Gareth Healy
The OpenShift Agent when monitoring a prometheus endpoint creates a single
metric with tagged datapoints, i.e.:
https://github.com/coreos/etcd/blob/master/Documentation/v2/metrics.md#
http-requests
I1228 21:02:01.820530 1 metrics_storage.go:155] TRACE: Stored [3]
[counter] datapoints for metric named
[pod/fa32a887-cd08-11e6-ab2e-525400c583ad/custom/etcd_http_received_total]:
[
{2016-12-28 21:02:01.638767339 +0000 UTC 622 map[method:DELETE]}
{2016-12-28 21:02:01.638767339 +0000 UTC 414756 map[method:GET]}
{2016-12-28 21:02:01.638767339 +0000 UTC 33647 map[method:PUT]}
]
But when trying to view this via the grafana datasource, only 1 metric and
the aggregated counts are shown. What i'd like to do is something like the
below:
{
"start": 1482999755690,
"end": 1483000020093,
"order": "ASC",
"tags": "pod_namespace:etcd-testing",
"groupDatapointsByTagKey": "method"
}
Search via tags or name (as-is) and group the datapoints by a tag key,
which would give you 3 lines, instead of 1.
Does that sound possible?
Cheers.
9 years, 1 month
HawkFX on Mac OS X issues?
by Thomas Cunningham
Hi,
I'm trying to use HawkFX on Mac OS X - I have it working great on Fedora
but would like to set it up on my Mac OS X box as well. I've got no
experience with ruby or jruby so I may be doing something wrong here in
installation, because I'm seeing the following :
lilguylaptop:hawkfx cunningt$ jruby -S -G hawkfx.rb
NameError: uninitialized constant G
Did you mean? GC
const_missing at org/jruby/RubyModule.java:3348
<main> at -G:
I installed rvm through homebrew and followed the current instructions in
the README.adoc. Should I be installing from source using a tool other
than homebrew to install rvm? It looks like I'm using rvm 1.28.0 and
jruby 9.1.5.0. Does that seem right?
Other possibly useful info :
Mac OS X 10.12
java 1.8.0_31
9 years, 2 months
OpenShift agent - multiple identity for certs
by Gareth Healy
Currently it seems you can only provide the agent configmap with the
identity field. But what i want to actually do, is provide this based on
the pods config map, i.e.:
data:
hawkular-openshift-agent: |
endpoints:
- type: prometheus
protocol: "https"
port: 9779
path: /metrics
collection_interval_secs: 5
metrics:
- name: my-first-metric
type: counter
identity:
cert_file: /var/run/secrets/client-crt/client.crt
private_key_file: /var/run/secrets/client-key/client.key
The reason being, i might have multiple prometheus endpoints that have
different certs.
Is that possible? or planned for the future?
Cheers.
9 years, 2 months
Hawkular Usage and other stats
by Kavin Kankeshwar
Hi,
I am evaluating Hawkular seems very interesting, I just wanted to know if
you guys have some usage stats and community involvement ?
I see see only few Github Stars etc, but the project is being actively
developed based on commit history.
Just wanted to figure out about hawkular if its production ready and I can
start using it if needed at my workplace. Obviously once we start using if
there are any changes I need i am willing to submit patches etc. But just
wanted to check on stats before i dive in . :)
Thanks!
Regards,
--
Kavin.Kankeshwar
9 years, 2 months
srcdeps is apparently broken or at least not working on travis
by John Mazzitelli
I can build this locally fine. However, srcdep plugin when running on travis is failing to compile h-inventory.
See the tons of compile errors here:
https://travis-ci.org/hawkular/hawkular-agent#L391
We need to either:
a) fix what is wrong with srcdep and travis
b) release inventory (and other dependencies in order to build things further downstream) so we don't use srcdeps
At this point, my okhttp upgrade is dead in the water since I can't get the h-agent or h-services repos to go green.
9 years, 2 months
