@wdolek@SumoLogic Hey, I will have to check internally on this with the engineering team who may have worked as a contributor to this repo. Will keep you posted.
@SumoLogic Hey can you please open a formal support ticket using [email protected] and provide your org id there and ask all your questions and we will be glad to clarify everything tere.
@PramodD33220811 I see could be an intermittent issue. Next time if such a situation arrives request you to file an official support ticket with the session id of the query that you are running along with issue as Twitter has a word limit and it becomes difficult to respond
@PramodD33220811 hey, Are you facing issues with search query performance or overall ingest? We don't have any such known issues. I would recommend opening a support ticket with us and give us a brief description of the ex
act issue.
@sa_cmdr you can reach out at [email protected] directly with the description of the issue that you have and it will open a support ticket with Sumo Logic support for you to provide the required help
@SumoLogic Hi @clarkee Can you please open a ticket by emailing [email protected] or by going to Help -> Support -> Submit a ticket from the Sumo Logic UI. We can help you further from there
@TransportEurope Thanks for sharing this on your twitter. As you mentioned sumologic_help, so it created a case in our ticketing system. Let us know if you have any issues or questions for this new feature.
@nathan_k As far as I know, there is no undocumented limit of one dyno for Sumo Logic Add-on for Heroku. If you can file a Zendesk case with your Org ID, we can investigate it further. Thanks.
@Christo48866392 Regex depends on the type of logs you have. In twitter we have restriction on number of characters. If you can open a case by sending email at [email protected] and provide the sample log message. I can help you writing the query.
@Christo48866392 Yes it can be possible. You need to write a regex, that captures the start_time and End_time from same log line. Then you can simply do "end_time - start_time as Time_duration". Hope that helps..