Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:25
    ejsmith synchronize #452
  • 06:25

    ejsmith on elastic7

    Minor (compare)

  • 06:00
    ejsmith synchronize #452
  • 06:00

    ejsmith on elastic7

    Add missing task id (compare)

  • Dec 13 22:43
    ejsmith synchronize #452
  • Dec 13 22:43

    ejsmith on elastic7

    More reindex job changes (compare)

  • Dec 13 15:46
    ejsmith synchronize #452
  • Dec 13 15:46

    ejsmith on elastic7

    Just retry 3 times (compare)

  • Dec 13 15:44
    ejsmith synchronize #452
  • Dec 13 15:44

    ejsmith on elastic7

    More log message changes (compare)

  • Dec 13 14:25
    niemyjski synchronize #452
  • Dec 13 14:25

    niemyjski on elastic7

    Added retry reindex for disconn… (compare)

  • Dec 13 14:09
    niemyjski synchronize #452
  • Dec 13 14:09

    niemyjski on elastic7

    Updated migration to retry sock… (compare)

  • Dec 13 04:51
  • Dec 13 03:28
    ejsmith synchronize #452
  • Dec 13 03:28

    ejsmith on elastic7

    Oops progress (compare)

  • Dec 13 03:04
    ejsmith synchronize #452
  • Dec 13 03:04

    ejsmith on elastic7

    More log formatting (compare)

  • Dec 13 02:02
    ejsmith synchronize #452
Lukas Wöhrl
@woehrl01
I suppose there are different serialiser settings in the 1.x branch. ;)
Blake Niemyjski
@niemyjski
might be
not 100% sure
might have to just rip out the 1.x serializer settings and then have two different serializers that you use
shouldn't be to hard
Lukas Wöhrl
@woehrl01
I'll test this in the next days ;) thank you very much for your help!
Blake Niemyjski
@niemyjski
no problem
Lukas Wöhrl
@woehrl01
have a nice day!
Blake Niemyjski
@niemyjski
you too
Blake Niemyjski
@niemyjski
@woehrl01 were you able to figure this out?
@/all whose ready to help test :D
Lukas Wöhrl
@woehrl01
didn't have time to test this out yet. but today we updated some of our services to send our messages from log4net via exceptionless. works awesome, as expected :)
Blake Niemyjski
@niemyjski
:)
Lukas Wöhrl
@woehrl01
no more email flooding :+1:
Blake Niemyjski
@niemyjski
we've made some more changes around that recently to ensure you get less emails in some scenarios
we were getitng bombarded with tons of emails when there wasn't a stack trace on an error
Lukas Wöhrl
@woehrl01
sounds good
is there something planed to allow custom "grouping" into the left menu?
for example to store complex searches for later usage (instead of keeping them in a text file)
Blake Niemyjski
@niemyjski
Yeah
We want that as well and more dashboards
Sander Rijken
@srijken
@niemyjski you mentioned me, but I couldn't find the message
Blake Niemyjski
@niemyjski
It's up in the list
Sander Rijken
@srijken
Any questions that I should answer? I found some mentions, that's it
Blake Niemyjski
@niemyjski
Nope
was just about testing :)
Sander Rijken
@srijken
right
Lukas Wöhrl
@woehrl01

@niemyjski I got it working, but not as you proposed. ;) Becauses it would introduce another DI container in our system (to allow injecting my dao into the IEventQueue nicely). It also would require me to add a fake api-key and url to make .Submit() work. (IsValid would fail otherwise)

I use now:
EventBuilder builder = e.ToExceptionless();
EventPluginContext context = new EventPluginContext(builder.Client, builder.Target, builder.PluginContextData);
EventPluginManager.Run(context);
IJsonSerializer serializer = builder.Client.Configuration.Resolver.GetJsonSerializer();
string errorAsString = serializer.Serialize(error.Target);

I even got the old one working :). The key was to upgrade the agent to 2.x and deserialize my json to the "InnerError" type. And submit as "@error" in the Event.Data. I can detect the different versions based on an existing "ExceptionlessClientInfo" property in the json file.

I have still one problem, and don't know if it's my mistake. I want to add additional EnvironmentInfos. So I add entries to the .Data field like: info.Data.Add("system up time", val) but these values do not show up in the UI. Things like: info.Architecutre = "x64" are working fine.

Blake Niemyjski
@niemyjski
@woehrl01 , you could reuse our lightweight di system. You just had to register your type with it :).
hmm
well, it would add all of that to the event.data property. are they listed there
environmental info has it's own key
@woehrl01 as long as you got it working, that's all that matters :)
but if you want to meet up.. I could help take a look into why that's not working
Lukas Wöhrl
@woehrl01

yeah, I know that I could use the DI from exceptionless, but I would need to do that at the "global" space. If I add those informations to the event.data property they are shown up. but it would be nice to have some of them under the "environment" tab. there is the "@environment" together with the EnvironmentInfo class. which works as expected. But the EnvironmentInfo class also has a Data property. Thats the one I tried to use. But I think this is the wrong place, isn't it?

I'm already in the weekend. Let's have a look for it on monday ;)

Lukas Wöhrl
@woehrl01
according to https://github.com/exceptionless/Exceptionless.UI/blob/master/src/app/event/tabs/environment.tpl.html the .data property of "@environment" is not displayed/unrolled.
that would be a nice addon. :+1: and this is the answer to my question, I currently use the wrong .data ;)
Blake Niemyjski
@niemyjski
@woehrl01 it has a data property but we currently are not showing anything in the data fields. I think we have a github issue for showing this content
hehe
maybe not. It would be an issue there (can you log one :D)
please
Lukas Wöhrl
@woehrl01
Shure :)
Blake Niemyjski
@niemyjski
It should show extended data for request info, environmental info
and probably something else :)
Blake Niemyjski
@niemyjski
well
so we can't really remove them
we don't have that data
unless we ran a query per organization
to get the last event date.
Blake Niemyjski
@niemyjski
@srijken you around