Hello Albert, welcome to our community!
Thanks for sharing! The thing about including the actor system name is
true, but just from 0.4.0.. TS is using 0.3.5 and by then it wasn't
necessary, regards!
On Thu, May 14, 2015 at 11:15 PM Albert Gorski albgor...@gmail.com wrote:
Hi,
I'm also new in
/kamon-io/Kamon?at=55677f68f4f7d3367e67b125
On Fri, May 29, 2015 at 12:22 PM Ivan Topolnjak ivant...@gmail.com wrote:
Hello Albert, welcome to our community!
Thanks for sharing! The thing about including the actor system name is
true, but just from 0.4.0.. TS is using 0.3.5 and by then it wasn't
max-packet-size = 1024 bytes
includes {
actor = [ user/myActor* ]
trace = [ * ]
dispatcher = [ * ]
}
report-system-metrics = true
}
On Tuesday, May 12, 2015 at 5:31:09 AM UTC-7, Ivan Topolnjak wrote:
Hello TS!
May I ask what
Hello guys!
As Yann said, the only Kamon thing that officially can be put in your log
patterns is the trace token via the provided converter, but, Kamon has
something called TraceLocal Storage which is basically a map where you
can put info and retrieve later on wherever you have access to the
not see any actor metrics
on my logs. Should I enable something on application.conf?
On Friday, May 8, 2015 at 4:40:14 PM UTC-7, Ivan Topolnjak wrote:
Oh, that can be a problem! We have not tested Kamon with 2.4 yet and
probably the issue you are facing is due to Kamon's bytecode being liked
on this. Thanks in advance.
On Wednesday, May 6, 2015 at 11:05:54 AM UTC-7, TS wrote:
Ivan, Sorry about the cross post. I was not sure where I should post. I
am using Kamon 0.3.5
On Wednesday, May 6, 2015 at 5:51:27 AM UTC-7, Ivan Topolnjak wrote:
Hello TS!
I just replied to you other email, please
on this. Thanks in advance.
On Wednesday, May 6, 2015 at 11:05:54 AM UTC-7, TS wrote:
Ivan, Sorry about the cross post. I was not sure where I should post.
I am using Kamon 0.3.5
On Wednesday, May 6, 2015 at 5:51:27 AM UTC-7, Ivan Topolnjak wrote:
Hello TS!
I just replied to you other email
Hello TS!
I just replied to you other email, please disregard that thread and post
your answer here.. what Kamon version are you using?
On Wed, May 6, 2015 at 3:07 AM TS test.tester1...@gmail.com wrote:
I just started using Kamon. I am getting an error while weaving (This
happens when my
Hello there!
It's really exciting to see where the Akka Streams HTTP projects are
heading, congrats to the team and to all contributors for such a great gift
to the community. Now, I know you get asked for WebSockets support a lot,
but this announcement made me wonder: Is the first release of
Vlad,
First, at the time this posting, we (the Kamon team) do not offer any kind
of payed support to our users, we do as much as we can to reply to all user
enquiries/concerns and address the bugs and enhancements reported by the
community in a open and free manner and we hope to continue
** This post was forwarded to kamon-user
(https://groups.google.com/forum/#!topic/kamon-user/fyeHDR7G0AU), here is a
copy of what I replied over there, just for the record.
Hello guys!
The reason for not seeing the actor metrics in New Relic is that we are not
reporting them at all :s... the
Congratulations guys! I'm super excited to see this out and to start
playing with it :), keep rocking!
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Prakhyat,
for the record: Kamon does provide metrics on number of HTTP requests,
average, min, max, counts per response status code and more, we don't have
metrics for bytes transferred.. are you using Spray or Play for HTTP? we do
support them! When we talk about Trace Metrics we talk about the
Congratulations guys!
I had the chance to look trough the code a few days ago and was really
surprised with how simple and concise it is, akka-http is (as Spray is
also) a very interesting piece of engineering, keep up with the awesome
work!
--
Read the docs: http://akka.io/docs/
Lee,
can you please elaborate a bit more on what timing do you want to measure?,
if I literally read your post, it seems like you want to measure the time
taken from the moment in which you start the call to tell on a ActorRef
until the moment the message has been successfully added to that
Heiko,
Hope you can help me with this little doubt.. if using the non deprecated
version of Props.apply, shouldn't we create actors by doing
`actorOf(Props[SomeActor](new SomeActor))`?, it is a bit odd to mention the
type twice, but it seems to be the way to go to ensure compatibility with
future
Roland,
I certainly feel like moving towards bounded queues as the rule rather than
the exception is the way to go. Setting reasonable bounds is a task
requiring deep knowledge of the application domain, actor/dispatcher
dynamics and running platforms (just to name a few), and it is difficult to
Chris,
sorry, I didn't express myself correctly, what I wanted to say is that not
having constant time .size() implementations by default doesn't mean that
we shouldn't monitor mailbox sizes, but instead find a alternative,
efficient way to get those numbers, which in my opinion are very
Charlie,
doing DB calls in Spray has nothing special or different from what you
would do with plain Akka, Play or any other toolkit. Certainly, there is a
preference for using async and non-blocking drivers, but that is not a
requisite. What really matters in case you are doing blocking calls to
19 matches
Mail list logo
