![]() It would still work, albeit it with degraded performance - there would not be overage charges Local Agent Revisit But IF one did really run out, Sumo Logic would perform much like the free trial when I exceeded all my limits and i got some 429s and some slow ingest. First, he pointed out that for annual plans, that should not happen as sales would get in contact if it were the case that one was likely to run out. Update: I spoke with a rep about really what happens when credits are used up. You can also read more on credits in licensing overview and Flex Credits. If I was front line Ops Manager, I might very well AMEX the whole year upfront and put in place budget limits (see Budgets section later). This just means, at present, Sumo Credits “retail” for US$0.195/mo and US$0.15/year. Showing to do what I’ve been doing would be about US$141 a month. Playing with the cost calculator, I found a query that roughly matched that Then I would guess I’m in the 720 ‘credits’ a month range. Let us assume this is it, what I have monitored is what I want. One can start to build a picture of what their organization is going to need. When you pair that with what one sees in the account details ![]() In a week I could start to get a trend on usage Given a day, we can see some pretty interesting spikes and data including a Data Volume Prediction panel (presently warning me it needs more data points to train the model)Īnd a few days later we can see some trends We can bring up the Overview to see what collectors are consuming how much ingest data It will start to collage usage data from that point forward.Īfter a half a day, I was able to see details from the Apps Then adding the Data Volume App from the Sumo Logic category in Apps You can get better details on usage by enabling Data Volume in your settings. Now that I have an Organization monitored, we can see results in the Security Dashboard We can now see “AnotherRepo” I created in the Organization level show up in my Github Overview dashboard We can add a webhook at the Organization Level just as we did at the Repo level Some of the Github Dashboards really only make sense in the context of monitoring an Organization such as the Security dashboard: Including accurate Issue reporting metricsĪn Overview includes Commits, PRs and Issues over time This, as the Sumo Logic person and I figured out, was from my massive S3 ingestion which consumed all the ingest GBs I had for the period.Īfter it calmed down, I started to get regular webhook pushes and 200 receipts.ĭespite following the guide, The times and events do not quite line up.Īfter a few days I could see results such as PRs in my repos I looked up the webhook responses in Github only to see I hit some sort of rate limit The Github dashboard in Sumo Logic stayed blank. I am concerned that after saving it, the webhook gave a 429 (Too Many Requests) response Paste in the webhook URL from the Sumo Wizard and change the other fields accordingly However, for this test, we’ll just add to one repo The next steps in the wizard speak to adding it for an Organization. We can now start the collector wizard up for the Github app We need to add a Field (x-github-event) first to properly parse events. We will follow this guide for the most part (albeit focus on a Repo first). ![]() Let’s try monitoring our Github Pull Requests. Circling back to monitors, we will dig into more integration connectors including Microsoft Teams, Integration with Rundeck and Datadog (events), and lastly look at Users and Roles before moving into a breakdown on Pricing and Budgets (with a commentary on optimizing S3 Logs). We will revisit our Linux collector and look at a Windows Collector as well including Performance Monitors. Today we will look at more integrations including monitoring Pipelines in Github, the “Usage” integration for Data Volume usage (which can help on price estimations). We then moved onto monitoring Kubernetes, AWS S3 and Cloudfront, Azure Event Hub and lastly touched on Monitors. In our last post we covered the History, Setup and usage with a Linux collector.
0 Comments
Leave a Reply. |