Sync with Inventory
by Austin Kuo
Hi all,
I’m currently investigating how to sync with inventory server.
Here’s the example scenario:
Consider the following problem. A user creates version 1 of the app with
two http servers, one listening on port 8080, the other on port 8181. In
version 2, the http server listening on port 8181 is no longer needed.
When the old version is stopped and the new version started, there will be
just one http server listening. The application is not aware of the
previous state. What should we do so that the second http server is removed
from Inventory?
Thanks in advance.
8 years, 6 months
Hawkular Metrics 0.17.0 - Release
by Stefan Negrea
Hello Everybody,
I am happy to announce release 0.17.0 of Hawkular Metrics. This release is
anchored by performance enhancements and new Grafana Datasource Plugin.
Here is a list of major changes:
1.
*Grafana Datasource Plugin - Experimental*
- A new Grafana 3 datasource plugin is now available for Hawkular
Metrics. This plugin integrates natively via the REST API.
- For downloads and installation instructions please visit Hawkular
Datasource for Grafana
<https://github.com/hawkular/hawkular-grafana-datasource>
- The plugin is developed as an independent project and contributions
are welcomed.
2.
*InfluxDB API - DEPRECATED*
- The InfluxDB API has been deprecated and will be removed in the
upcoming release.
- This was an addition to make project integrations easier. As the
REST interface matured, the role of the InfluxDB compatibility interface
was reduced only serve as the Grafana interface. With the release of the
native Grafana plugin, this is no longer needed.
- For more details: HWKMETRICS-411
<https://issues.jboss.org/browse/HWKMETRICS-411>
3.
*Fetching Raw Data - Multiple Metrics - Experimental*
- Prior to this release, it was possible to only fetch raw data points
for a single metric. This release added POST */query endpoint that
allows querying for raw data points for multiple metrics.
- The endpoints are:
- POST /hawkular/metrics/gauges/raw/query
- POST /hawkular/metrics/counters/raw/query
- POST /hawkular/metrics/counters/rates/query
- POST /hawkular/metrics/strings/raw/query
- POST /hawkular/metrics/availability/raw/query
- POST /hawkular/metrics/metrics/raw/query
- The endpoint accepts a list of metrics ids and allows filtering by
providing start time, end time, sort order and limit.
- For more details: HWKMETRICS-393
<https://issues.jboss.org/browse/HWKMETRICS-393>
4.
*Performance Enhancements*
- Two Cassandra driver settings (maxConnectionsPerHost and
maxRequestsPerConnection) are now user configurable. Part of the update,
the default values have been increased from the driver defaults. The new
defaults had a significant performance boost for a simple test
deployment.
The settings are configurable to allow users to optimize driver behavior
for larger Hawkular Metrics deployments. (HWKMETRICS-430
<https://issues.jboss.org/browse/HWKMETRICS-430>)
- On Linux deployments, the Cassandra driver uses Netty native epoll (
HWKMETRICS-418 <https://issues.jboss.org/browse/HWKMETRICS-418>)
5.
*Cassandra*
- Fixed an issue with schema upgrades present in Hawkular Metrics 0.15.0
and 0.16.0. We recommend upgrading from previous versions directly to
0.17.0. For more details: HWKMETRICS-425
<https://issues.jboss.org/browse/HWKMETRICS-425>
- Cassandra 3.7 is now the supported version of Cassandra. Support
has been deprecated for Cassandra 3.5.
*Hawkular Metrics Clients*
- Python: https://github.com/hawkular/hawkular-client-python
- Go: https://github.com/hawkular/hawkular-client-go
- Ruby: https://github.com/hawkular/hawkular-client-ruby
- Java: https://github.com/hawkular/hawkular-client-java
Release Links
Github Release:
https://github.com/hawkular/hawkular-metrics/releases/tag/0.17.0
JBoss Nexus Maven artifacts:
http://origin-repository.jboss.org/nexus/content/repositories/public/org/...
Jira release tracker:
https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12330692
A big "Thank you!" goes to John Sanda, Thomas Segismont, Mike Thompson,
Matt Wringe, Michael Burman, and Heiko Rupp for their project
contributions.
Thank you,
Stefan Negrea
8 years, 6 months
Metrics and use of metrics_idx
by Michael Burman
Hi,
This sparked my interest after the discussions in PR #523 (adding cache to avoid metrics_idx writes). Stefan commented that he still wants to write to this table to keep metrics available instantly, jsanda wants to write them asynchronously. Maybe we should instead just stop writing there?
Why? We do the same thing in tenants also at this time, we don't write there if someone writes a metric to a new tenant. We fetch the partition keys from metrics_idx table. Now, the same ideology could be applied to the metrics_idx writing, read the partition keys from data. There's a small performance penalty, but the main thing is that we don't really need that information often - in most use cases never.
If we want to search something with for example tags, we search it with tags - that metricId has been manually added to the metrics_idx table. No need to know if there's metrics which were not initialized. This should be the preferred way of doing things in any case - use tags instead of pushing metadata to the metricId.
If we need to find out if id exists, fetching that from the PK (PartitionKey) index is fast. The only place where we could slow down is if there's lots of tenants with lots of metricIds each and we want to fetch all the metricIds of a single tenant. In that case the fetching of definitions could slow down. How often do users fetch all the tenant metricIds without any filtering? And how performance critical is this sort of behavior? And what use case does list of ids serve (without any information associated to them) ?
If you need to fetch datapoints from a known metricId, there's no need for metrics_idx table writing or reading. So this index writing only applies to listing metrics.
- Micke
8 years, 6 months
