Should Keycloak integration be optional?
by Juraci Paixão Kröhling
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As I mentioned on the previous email, one of the questions during the
demo was if it would be possible to have the Keycloak integration as
an optional part.
In the backend part, it's not hard to disable Keycloak as the
authentication mechanism, as it's just JAAS. That would require,
though, a second JAAS implementation to replace it.
In the frontend part, however, it's a bit more complicated. The setup
right now is that the web console is treated as an HTML5 single-page
app. This means that the web console is one application and the
backend is a different one, and they propagate the authentication by
using the tokens: the web console gets a token from the Keycloak
JavaScript adapter once the user logs in and sends it along with each
request to the backend. The backend (Keycloak Wildfly Adapter) reads
this token and retrieves the user data from the Keycloak server,
allowing the request to execute or not.
This means that either:
1) web console and REST API (and possibly other wars) become one, so
that the HTML5 single-page app can be served only after the user logs
in (classic Java EE application)
2) the backend JAAS adapter would need to support also some sort of
token exchange, with the frontend abstracting the Keycloak adapter to
work with one auth mechanism or another, possibly auto identifying
what is the backend's auth mechanism.
3) ??
I don't think that the first option is a real one. Having small wars,
each taking care of one concern, is a goal on the project.
So, would an effort in making Keycloak an optional part be worth it?
Should I pursue it?
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUworiAAoJECKM1e+fkPrX8oMH/jC6DSOzx5gJuQNVHsojO6jB
xHjAbhiF89mnlC9iHBKTmZnJ6O4sOs870tibxhhmNvJs+N5wvQVCWhv+5JdqONfe
ETP4O7iKYLHu317DuNW8gl3FRP9Mgj/FkpgGhanikOLZ7S1B9/86zv8qdQ1/C6Hm
EM1MOIlSqqwPk+QPj/51Uo6rMG42ObG6P+mJOu7IhuJK4LS0uZI3yCIyk42+ngit
+T05kOfYOL24nOcL4iCjb0+Qg9SjNPASklq79Kz1h9tMZkq3CAXwyPJ0ty0kKSwR
mejY48LahgwmGQF53zovQJbb7Lpek+Uu9+G/vbcaJGLgqs5qwQq+3qa3e81Q9I0=
=5KoB
-----END PGP SIGNATURE-----
11 years
define: tenant
by Juraci Paixão Kröhling
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
After the demo, I was looking for ways to improve the "realm selection
modal", but I keep hitting a problem with the definition of a
tenant/realm.
Taking Keycloak out of the context for a while, I'd like to get *our*
definition of tenant to be made. After that, I can check if we can use
Keycloak as part of the authorization for this scenario (KC will
probably still be part of the authentication, though).
One possible solution is to have "users" and "organizations", a la
Github. Users can be part of zero or more organizations and
organizations have one or more members. Data (git repos or resources)
belongs to either an user or an organization.
For this solution, here's how I see it working on different scenarios:
- - standalone/hobby user: isn't a member of any organization, but have
a few resources to manage. A sample curl call:
- -> http://user:password@hawkular/metrics
all metrics for all resources owned by the user's main account
- -> http://user:password@hawkular/resource/{resourceId}/metrics
all metrics for this specific resource, which should belong to the
main account
- - user who creates/manages one or more organizations: can either have
resources on the main account (like standalone) or have resources
belonging to an organization. Sample curl call:
- -> http://user:password@hawkular/metrics
all metrics for all resources owned by the user's main account *or*
owned by organizations where this user is a member of.
- -> http://user:password@hawkular/resource/{resourceId}/metrics
all metrics for this specific resource, if the resource belongs to
the user or to an organization where the user is a member of
For this scenario, I think the UI could be built with a "context
switcher". This way, the user would have access to a dashboard with
resources from his main account and could switch to a dashboard with
resources from an organization. The backend, though, would not have
such a notion of "context". Either the user has access to the resource
or not (via the main account or via an organization).
Putting Keycloak back in context: for this kind of scenario, we would
have only one Keycloak realm, so, all users would be in one big realm.
All of the authorization would be made on our backend(s). Upon
registration (via Keycloak), an user doesn't belongs to any
organization. In the future, we can consume some extra LDAP data from
Keycloak, to auto assign users to some organizations, if desirable.
The main disadvantage of this is that we have to also care about the
authorization, as we cannot rely on permission data coming from Keycloak.
The main advantage is that we get a behavior that is custom tailored
to our use case.
Thoughts?
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUymw8AAoJECKM1e+fkPrX9KQH/A2O1pcV+cO3mu7PPV5aWq/v
9Ke+xlm+2hutMVKned5RGld2JD47pqTqdj6WBsLqu04AcntUrc46Vt8gnHCGrst+
FlYPsvlhb/tkN3Ddg4UMfspn5uar7uaSg2namTtSz3A/DDjQkmxqBBCUqtLgFaAc
NDaV/XkDrPCBbbNOHN11GLBV8WpFM6g5JeiaPfHWROGTifQCJU52ZEgPj0pbtGL9
NqLjOF2ekrnhxVNH/PqP2akN0bzWK6Bo2i2SMgNILZEDVQyMlTA1w1hCEcn/35oG
wHCOsGFb2RUJyqGgWqyqoxqsKBgOErzfGUhwQ4VEpU15Cvoh3HyGrEtHQCqFWzI=
=IfUo
-----END PGP SIGNATURE-----
11 years
checkstyle/enforcer
by John Mazzitelli
I just converted the bus code to use hawkular-parent which in turn brought checkstyle/enforcer into play.
I highly recommend everyone do this for your code as soon as you can - the earlier you integrate parent, and especially checkstyle/enforcer, the easier it will be on yourself. Lots of checkstyle and enforcer errors in my stuff that I had to go about fixing... you don't want to do this after you have lots of code that needs to be cleaned up.
11 years
logging ID ranges
by John Mazzitelli
I would like to make a recommendation for logging range IDs for the different components.
Right now, the default width of IDs are 6 characters (they can be more or less, but that's the default). I'm assuming we all will use HAWK as the prefix (as opposed to HAWK vs. HAWKMETRICS vs. HAWKALERTS, etc).
Through my experience integrating this logging stuff the past few days in the bus modules, I've come to appreciate the fact that we should probably give more range than just 1000 IDs to a major component. I don't know exactly how to do it, but I found it easier to split the ranges up to my subcomponents when using the full 6-characters. This allows you to create multiple MessageLogger classes (one per maven module is what I think would be typical - especially if one module doesn't depend on others) and you can break your main range up into subranges, while still having enough IDs left for actual logs.
For example, suppose metrics has four subcomponents (and I'm just making this up) - metrics-aggregator, metrics-collector, metrics-ui, metrics-purge. Now, suppose metrics was given the range 1000-1999. Each subcomponent would only have 250 IDs each if you assign them their own subrange. If you don't, if you just give them all 1000 then you will probably only have a single MessageLogger for all 4, and that will get ugly (MessageLogger would live in one module, and they all would need to depend on it, and any new log message would require all modules to recompile, even if the other modules don't need that message).
So what I say is we give metrics the ID range (e.g.) HAWK-200000 to HAWK-299999. Each subcomponent could then be given:
metrics-aggregator = 200000-200999
metrics-collector = 201000-201999
metrics-ui = 202000-202999
metrics-purge = 203000-203999
So you can see each still has room for 1,000 message IDs individually with room for 100 subcomponents (that's the first three digits of the ID - 200-299).
Alerts would then be given the range HAWK-300000 to HAWK-399999 and it does the same thing.
Obviously, this can be tweeked; you can say the first two digits are the component (20-29) giving you room for 10 subcomponents, with each subcomponent now able to have 10,000 messages (e.g. 200000-209999).
Or we can give each their own prefix (HAWK vs HAWKMETRICS) giving each the full 6-digit ID range all to themselves.
In any event, if you haven't tried coding up log messages with this Jboss logging message ID stuff, I suggest you do it, and see what kinds of issues you will see crop up (mainly it deals with what ranges of IDs get assigned to what MessageLoggers and how many MessageLoggers do you create and where).
We don't want to do this wrong - it will be headaches later on in the future when we realize we handed out the IDs ranges poorly or we created MessageLoggers in the wrong places.
I'm not advocating any specific approach, but we need to think about this - this isn't one of those things where everyone can go rogue. Unless we give everyone their own id prefix (HAWK vs. HAWKMETRICS, for example) in which case, go crazy :)
11 years
jboss logging PR ready for merge to h-parent
by John Mazzitelli
OK, I've got a PR into the hawkular-parent-pom repo - once someone reviews and merges that for me (*cough cough* *hint hint*), it means we have JBoss Logging processing enabled for Hawkular. Take a look here to see what had to get done (it just involved a maven plugin "org.bsc.maven:maven-processor-plugin")
https://github.com/hawkular/hawkular-parent-pom/pull/6
To use the jboss logging processor, your maven project's pom needs to have hawkular-parent as its root parent. Once you do that, you need two dependencies on your pom - jboss-logging itself (obviously) and the jboss-logging-annotations which gives you the logging annotations like @MessageLogger, @LogMessage, etc. These are the two you need:
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging-annotations</artifactId>
<scope>provided</scope>
</dependency>
Here's what a typical logging interface looks like - if interested. This is how you define the i18n messages with ID numbers:
https://github.com/hawkular/hawkular-bus/blob/master/hawkular-bus-common/...
Notice I'm only assigning IDs to INFO through ERROR levels (not for DEBUG or TRACE).
Once hawkular-parent merges my PR, I'll merge my own PR I have waiting in hawkular-bus so it can just use hawkular-parent's jboss logging process stuff.
11 years
Does index.html page need License header
by mike thompson
Just curious if the actual index.html page needs a License header?
And after the ts/js/gwt app is minified does there need to be any licensing header in the minified code?
11 years
[metrics] schema changes
by John Sanda
I merged changes to master yesterday that include schema changes. You will need to drop your existing keyspaces in order to pick up the changes. You can do this in cqlsh,
DROP KEYSPACE rhqtest;
and if you are using ccm, you can start a cqlsh session with,
ccm node1 cqlsh
I just added a property to the build that will do this for you during metrics-core integration tests.
mvn test -Dresetdb
- John
11 years
Logging ...
by Heiko W.Rupp
Hey,
We should / need to start using logging codes just like Wildfly does.
11:19:27,714 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
11:19:27,716 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
We have two options here
1)
We use "HAWK" as our prefix and the following code ranges initially
0-999 Hawkular (integration)
1000-1999 Hawkular-Metrics
2000-2999 Hawkular-Alerts (notifiers should probably be broken out in separate blocks)
3000-3999 Hawkular-Inventory
4000-4999 Hawkular-Bus
2)
We use a prefix per component (e.g. HAWK, HKMET, HKAL, ...) and each component has its own code range starting
at 0
Personally I prefer option 1
There is already documentation on this available
• https://developer.jboss.org/wiki/HowToLogInJBossProjects
• https://developer.jboss.org/wiki/InternationalizedLoggingAndExceptions
• https://developer.jboss.org/wiki/JBossLoggingTooling
While the documentation and examples look a bit complicated, I think we can "reduce" them for
our purpose for Warnings and Errors and do not need them on debug/trace level.
For info level I guess one should personal judgement (and then if it is not important enough for
its own code, it is probably not really something at info, but rather at debug level).
In practice we would probably end up with something like:
import org.jboss.logging.*;
public interface RestApiLogger {
RestApiLogger LOGGER = Logger.getMessageLogger(RestApiLogger.class,"org.hawkular.inventory.rest");
@LogMessage(level = Logger.Level.WARN)
@Message(id = 3000, value = "Something bad has happened")
void warn(@Cause Throwable t);
< plus much more refined messages here >
}
and then in code
} catch (Exception e) {
RestApiLogger.LOGGER.warn(e);
return Response.serverError().entity(e).build();
}
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey, Charlie Peters
11 years
[hawkular/hawkular-alerts] 88f4f1: HWKALERTS-1 Prepare an initial version
by Jay Shaughnessy
Branch: refs/heads/master
Home: https://github.com/hawkular/hawkular-alerts
Commit: 88f4f1ff84345f380b11455331437b722867ac27
https://github.com/hawkular/hawkular-alerts/commit/88f4f1ff84345f380b1145...
Author: Lucas Ponce <ponce.ballesteros(a)gmail.com>
Date: 2015-01-29 (Thu, 29 Jan 2015)
Changed paths:
M .gitignore
A README.adoc
A examples/example-alerts-ui/pom.xml
A examples/example-alerts-ui/src/main/webapp/WEB-INF/jboss-web.xml
A examples/example-alerts-ui/src/main/webapp/WEB-INF/web.xml
A examples/example-alerts-ui/src/main/webapp/index.jsp
A hawkular-alerts-api/pom.xml
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/Alert.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/AvailabilityCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/AvailabilityConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/CompareCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/CompareConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/Condition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/StringCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/StringConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdRangeCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdRangeConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/dampening/Dampening.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/Availability.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/Data.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/NumericData.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/StringData.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/notification/Notification.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/trigger/Trigger.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/trigger/TriggerTemplate.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/AlertsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/NotificationsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/NotifierListener.java
A hawkular-alerts-bus/pom.xml
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/init/AlertEngineRegister.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/AlertDataListener.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/NotifierTypeListener.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/messages/AlertData.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/messages/AlertDataMessage.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/sender/NotificationSender.java
A hawkular-alerts-ear/pom.xml
A hawkular-alerts-ear/src/main/application/META-INF/jboss-deployment-structure.xml
A hawkular-alerts-engine/pom.xml
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/BasicAlertsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/DroolsRulesEngineImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/MemDefinitionsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/MemNotificationsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/rules/RulesEngine.java
A hawkular-alerts-engine/src/main/resources/META-INF/kmodule.xml
A hawkular-alerts-engine/src/main/resources/META-INF/maven/pom.properties
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/conditions.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/dampening.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/notifiers.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/triggers.data
A hawkular-alerts-engine/src/main/resources/org/hawkular/alerts/engine/rules/ConditionMatch.drl
A hawkular-alerts-engine/src/test/java/org/hawkular/alerts/engine/RulesEngineTest.java
A hawkular-alerts-engine/src/test/resources/simplelogger.properties
A hawkular-alerts-rest/pom.xml
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/AlertsHandler.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/HawkularAlertsApp.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/NotificationHandler.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/TriggersHandler.java
A hawkular-alerts-rest/src/main/webapp/WEB-INF/beans.xml
A hawkular-alerts-rest/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-alerts-rest/src/main/webapp/WEB-INF/web.xml
A hawkular-alerts-rest/src/main/webapp/index.jsp
A hawkular-notifiers-api/pom.xml
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotificationMessage.java
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotifierRegistrationMessage.java
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotifierTypeRegistrationMessage.java
A hawkular-notifiers-email/pom.xml
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/notifications/EmailListener.java
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/registration/RegisterListener.java
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/registration/RegistrationInit.java
A hawkular-notifiers-email/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-email/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-email/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-email/src/main/webapp/index.jsp
A hawkular-notifiers-sms/pom.xml
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/notifications/SmsListener.java
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/registration/RegisterListener.java
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/registration/RegistrationInit.java
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-sms/src/main/webapp/index.jsp
A hawkular-notifiers-snmp/pom.xml
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/notifications/SnmpListener.java
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/registration/RegisterListener.java
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/registration/RegistrationInit.java
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-snmp/src/main/webapp/index.jsp
A pom.xml
Log Message:
-----------
HWKALERTS-1 Prepare an initial version
Commit: a0312d4026d9563ca9886d7107e97b75bc7d0732
https://github.com/hawkular/hawkular-alerts/commit/a0312d4026d9563ca9886d...
Author: Jay Shaughnessy <jshaughn(a)redhat.com>
Date: 2015-01-29 (Thu, 29 Jan 2015)
Changed paths:
M .gitignore
A README.adoc
A examples/example-alerts-ui/pom.xml
A examples/example-alerts-ui/src/main/webapp/WEB-INF/jboss-web.xml
A examples/example-alerts-ui/src/main/webapp/WEB-INF/web.xml
A examples/example-alerts-ui/src/main/webapp/index.jsp
A hawkular-alerts-api/pom.xml
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/Alert.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/AvailabilityCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/AvailabilityConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/CompareCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/CompareConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/Condition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/StringCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/StringConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdRangeCondition.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/condition/ThresholdRangeConditionEval.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/dampening/Dampening.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/Availability.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/Data.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/NumericData.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/data/StringData.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/notification/Notification.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/trigger/Trigger.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/model/trigger/TriggerTemplate.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/AlertsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/DefinitionsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/NotificationsService.java
A hawkular-alerts-api/src/main/java/org/hawkular/alerts/api/services/NotifierListener.java
A hawkular-alerts-bus/pom.xml
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/init/AlertEngineRegister.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/AlertDataListener.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/listener/NotifierTypeListener.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/messages/AlertData.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/messages/AlertDataMessage.java
A hawkular-alerts-bus/src/main/java/org/hawkular/alerts/bus/sender/NotificationSender.java
A hawkular-alerts-ear/pom.xml
A hawkular-alerts-ear/src/main/application/META-INF/jboss-deployment-structure.xml
A hawkular-alerts-engine/pom.xml
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/BasicAlertsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/DroolsRulesEngineImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/MemDefinitionsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/impl/MemNotificationsServiceImpl.java
A hawkular-alerts-engine/src/main/java/org/hawkular/alerts/engine/rules/RulesEngine.java
A hawkular-alerts-engine/src/main/resources/META-INF/kmodule.xml
A hawkular-alerts-engine/src/main/resources/META-INF/maven/pom.properties
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/conditions.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/dampening.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/notifiers.data
A hawkular-alerts-engine/src/main/resources/hawkular-alerts/triggers.data
A hawkular-alerts-engine/src/main/resources/org/hawkular/alerts/engine/rules/ConditionMatch.drl
A hawkular-alerts-engine/src/test/java/org/hawkular/alerts/engine/RulesEngineTest.java
A hawkular-alerts-engine/src/test/resources/simplelogger.properties
A hawkular-alerts-rest/pom.xml
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/AlertsHandler.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/HawkularAlertsApp.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/NotificationHandler.java
A hawkular-alerts-rest/src/main/java/org/hawkular/alerts/rest/TriggersHandler.java
A hawkular-alerts-rest/src/main/webapp/WEB-INF/beans.xml
A hawkular-alerts-rest/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-alerts-rest/src/main/webapp/WEB-INF/web.xml
A hawkular-alerts-rest/src/main/webapp/index.jsp
A hawkular-notifiers-api/pom.xml
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotificationMessage.java
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotifierRegistrationMessage.java
A hawkular-notifiers-api/src/main/java/org/hawkular/notifiers/api/model/NotifierTypeRegistrationMessage.java
A hawkular-notifiers-email/pom.xml
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/notifications/EmailListener.java
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/registration/RegisterListener.java
A hawkular-notifiers-email/src/main/java/org/hawkular/notifiers/email/registration/RegistrationInit.java
A hawkular-notifiers-email/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-email/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-email/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-email/src/main/webapp/index.jsp
A hawkular-notifiers-sms/pom.xml
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/notifications/SmsListener.java
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/registration/RegisterListener.java
A hawkular-notifiers-sms/src/main/java/org/hawkular/notifiers/sms/registration/RegistrationInit.java
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-sms/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-sms/src/main/webapp/index.jsp
A hawkular-notifiers-snmp/pom.xml
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/notifications/SnmpListener.java
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/registration/RegisterListener.java
A hawkular-notifiers-snmp/src/main/java/org/hawkular/notifiers/snmp/registration/RegistrationInit.java
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/jboss-web.xml
A hawkular-notifiers-snmp/src/main/webapp/WEB-INF/web.xml
A hawkular-notifiers-snmp/src/main/webapp/index.jsp
A pom.xml
Log Message:
-----------
Merge pull request #1 from lucasponce/Initial-Import
HWKALERTS-1 Prepare an initial version
Compare: https://github.com/hawkular/hawkular-alerts/compare/3436f14c5fe1...a0312d...
11 years
