Multiple database tables

[rhurling]

Would it be possible to extend the record function so that one could save to different tables (maybe a new core attribute "table")?
That way I could use this library for a specialised api counter table with multiple (non-nullable) custom attributes and use the default table for easier / normal metrics.

If this already exists it seems to not be documented.

[IsraelPinheiro]

You can do that using a custom model.

• On your model, extend DirectoryTree\Metrics\Metric
• On that model define any needed aditional data and define the database connection to be used (On my project I define the connection and set uuid as my id type)
• Add DatabaseMetricManager::useModel("Your custom model"); to your AppServiceProvider boot()

I use this exact implementation on my project

[rhurling]

But your solution using a custom model restricts you to only 1 metric model?
I basically want to use 2 different Models (1 for app-related metrics (internal) and 1 for api metrics (customer-visible))

[stevebauman]

Hey @rhurling, I think this is a good suggestion and I agree that it should be possible. Let me see what I can do! 👍