HAWKULAR Jira cleanup
by Heiko W.Rupp
Hey,
I have cleaned up the HAWKULAR jira project and closed some outdated items.
Can you please all have a look at the items you have either opened or are
assigned to and see if they are still relevant and close them if not?
Thanks
Heiko
9 years, 2 months
Move to WF 10.1.0?
by Jay Shaughnessy
I noticed that on Openshift we are running Hawkular Metrics on WildFly
10.1.0. It was upped from 10.0.0 several months ago due to a blocking
issue that had been fixed in EAP but not WF 10.0. I ran into a new
issue when trying to deploy Metrics master on OS Origin. It failed to
deploy on WF 10.1.0. I was able to solve the issue without a major
change but it called out the fact that we are building Hawkular against
WF 10.0.1 bom and running itests against 10.0.0 server.
Because OS is a primary target platform I'm wondering if we should bump
the parent pom deps to the 10.1.0 bom and server (as well as upping a
few related deps as well, like ISPN). As part of my investigation I did
this locally for parent pom, commons, alerting and metrics and did not
see any issues.
Thoughts?
9 years, 2 months
srcdep changes?
by John Mazzitelli
I just found out the problem I'm having with srcdeps in h-services is because this wasn't merged:
https://github.com/hawkular/hawkular-services/pull/104
Once I merged that locally, I am able to put in the SRC-revision-### in the version string and it works.
But this brings up a question: what changed? Can you not use srcdeps anymore by simply adding SRC-revision-### in the version string? Because I see now a complicated .mvn directory with extensions.xml and srcdeps.yaml configuration files... did we have srcdep config files before?
I didn't really look closely at the srcdep and mvn changes that went in, but I guess I should have. Is this now more complicated to use than simply changing a version string to include SRC-revision?? Because that was really nice and easy to use (almost magical :-)
9 years, 2 months
Hawkular-metrics resource requirements questions
by Daniel Miranda
Greetings,
I'm looking for a distributed time-series database, preferably backed by
Cassandra, to help monitor about 30 instances in AWS (with a perspective of
quick growth in the future). Hawkular Metrics seems interesting due to it's
native clustering support and use of compression, since naively using
Cassandra is quite inefficient - KairosDB seems to need about 12B/sample
[1], which is *way* higher than other systems with custom storage backends
(Prometheus can do ~1B/sample [2]).
I would like to know if there are any existing benchmarks for how
Hawkular's ingestion and compression perform, and what kind of resources I
would need to handle something like 100 samples/producer/second, hopefully
with retention for 7 and 30 days (the latter with reduced precision).
My planned setup is Collectd -> Riemann -> Hawkular (?) with Grafana for
visualization.
Thanks in advance,
Daniel
9 years, 2 months
moving okhttp library from 2.x to 3.x
by John Mazzitelli
We have been using version 2.x of the okhttp library and its associated WebSocket library.
Moving to the latest 3.x stream would keep us up-to-date and would be useful because we recently saw some odd behavior where the websocket library was spitting out warnings about resources leaking and that problem I think is fixed in the 3.x versions.
So I wrote this JIRA: https://issues.jboss.org/browse/HAWKULAR-1138
There are four PRs associated with that JIRA for parent-pom, commons, inventory, and agent that I need peer reviewed. We then need to publish these in an organized fashion (parent-pom first, then we move commons pulling in the new parent pom, then inventory and agent pulling in the new commons and parent pom).
Also: Metrics: I noticed hawkular-metrics defines a property for a VERY old okhttp version (2.0.0) but it doesn't seem to even be using it. See https://github.com/hawkular/hawkular-metrics/search?q=squareup - I think metrics should get rid of that obsolete version property definition.
Does anyone know of anywhere else we are using okhttp?
9 years, 2 months
Hawkular APM 0.13.0.Final released
by Gary Brown
Hi
We are pleased to announce the availability of Hawkular APM version 0.13.0.Final. The release can be found here: https://github.com/hawkular/hawkular-apm/releases
This release includes:
* OpenTracing (Java and JavaScript) providers:
- sampling API
- use deployment metadata information from OpenShift environment to automatically name services/versions
* OpenTracing based JVM agent
- ability to define custom ByteMan rules
* OpenShift
- template improvements to separate out management of Elasticsearch cluster
- vertx-opentracing example updated to separate services into individual deployments, with Ansible script for single command install
* UI
- trace instance diagram colour coded to show areas with performance issues
- filter sidebar applied to transaction pages
Regards
Hawkular APM Team
9 years, 2 months
Docker build on a VM
by Jay Shaughnessy
I was stumped for quite a while about why I couldn't get a docker build
to run on my VM. The symptom is that the docker build can not reach the
outside world, and therefore can't pull in what it needs. This happens
even though the VM itself has no connectivity issues. Note, I assume
this is a VM thing because it happened to both mazz and myself, using
Virtual Box fedora vms, but it may not be limited to VMs. I finally
stumbled on a stack overflow entry that solved the issue [1].
Basically, you need to tell docker about your DNS servers, and also
Google's DNS server 8.8.8.8. Your mileage may vary, perhaps you'll only
need a subset of of servers, but hopefully this helps you out, because
it was a pita.
[1]
http://stackoverflow.com/questions/25130536/dockerfile-docker-build-cant-...
9 years, 2 months
