Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging to SQL Server #269

Closed
carlowahlstedt opened this issue May 4, 2018 · 1 comment
Closed

Logging to SQL Server #269

carlowahlstedt opened this issue May 4, 2018 · 1 comment

Comments

@carlowahlstedt
Copy link

@carlowahlstedt carlowahlstedt commented May 4, 2018

I'm new to AppMetrics and trying to understand it's function. It seems it's the gathering layer (my interest is ASP.Net Core) to send the data to some repository. I see support for several backend repositories, but none of which are "standard" in my environment, but SQL Server is. Would it make sense to log these metrics to SQL so that Grafana could use that as it's repo? Or is the better architectural decision to use some other type of repository?

Help appreciated. Thanks.

@alhardy
Copy link
Collaborator

@alhardy alhardy commented May 5, 2018

There's an brief introduction on what App Metrics is in the docs, hopeful this helps answer some of your questions.

Which repository to use is opinionated just like everything else.

SQL Server wasn't built for timeseries specifically which is where TSDBs come in. However it's definetly possible to use SQL Server as a TSDB, in fact Grafana recently released support for MS SQL as a datasource and also has support for MySQL and PostgreSQL.

Or is the better architectural decision to use some other type of repository?

That would depend on the use case, I would suggest weighing up the pros and cons of each.

App Metrics doesn't yet have a MS SQL reporter, that could be a good contribution.

If your concerns with using a more timeseries specific repository are around hosting, you can find several managed hosting options in the space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants