-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Wait, nevermind... What I suggested is exactly what logging is
supposed to do:-) So, I think what I'm suggesting is a new logging
framework/tool, which makes absolutely no sense.
- - Juca.
On 05/08/2015 11:35 AM, Juraci Paixão Kröhling wrote:
On 05/08/2015 11:25 AM, Gary Brown wrote:
> Could you give some examples of what "type" would be? I remember
> hearing "deployment" as one of the possible types, but would be
> interesting to think of some other cases.
>> Type could be anything, so a logical label such as "Log
>> entry", "Alert", "BTMFragment", etc - just so that from
an
>> Elasticsearch perspective we could define a basic schema to
>> identify how it should index the information for that type.
>> Elasticsearch can dynamically create a schema based on the
>> information it receives, but there are cases where you need to
>> control how it processes the data (e.g. UUIDs) where you don't
>> want it to analyse the field further.
Then there could also be a "category" property, similar to the
logging approach. For instance, BTM could send 50 events for a
single BTM transaction, some with the FINEST category, some with
CRITICAL, or even ERROR, and only a small portion of them (say, >
INFO) would be persisted by default. In case of problems, it this
could be changed to log all events.
- Juca. _______________________________________________
hawkular-dev mailing list hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVTIOOAAoJECKM1e+fkPrXEnIIAJly6SWoPvr5IK+R8aeGO3YL
QZU3ckbepRya1zWhlxoSqKi0V9qR0wIesQ5isK7R+iJvBX5xptdndBAfn2Odfc3X
xeuhlUFHpZMpEdjGXtp0ozo7rIeGgWzunAK8oEEKEe+ydcVQNdKUPjvqzvO6TXlU
MBEF3vvhFik0XqlmgXs9ZTg6nXTf46M7mbK1YzajPxOe5FmEtYdbb5WO4AHzRUD7
MGFQTZK4DKyGJVxj3+//FHmNOnhS2x99ae12e+Yw020NhTwFvEj+2HUn7M+Di6kp
BOecMFxPw7klpdB6jKjwztvGFn86qWdh3c8AbDOum2dzBzFPVaag/HIGi+fKn0E=
=J1zm
-----END PGP SIGNATURE-----